Resources · Zapier integration

Atlas Zapier integrationAutomate Atlas with Zapier.

The Atlas Zapier integration gives you 5 triggers, 10 actions and 7 searches. All five triggers are instant, it runs on the free plan, and nearly every step turns on one detail: which ID points at which person. Here is what each operation does and costs.

See the 22 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Atlas Zapier integration actually does

Atlas is a relationship platform that maps your team's network to find the next customer, investor or hire. The integration lets Zapier react when a person, a company, a custom field or a list changes in Atlas, and write people, notes, lists and field values back into it.

Three results worth building first. A record that documents itself: List Member Added starts the Zap, Get User fetches the teammate who will sign it from their email, and Create Note leaves a trace on the person. Lists that sort themselves: Custom Field Value Updated reacts to a change in a field, and Add Person to List files the person where they belong. A clean outbound sync: Person Updated and Company Updated fire the moment Atlas changes, so the next steps start from the latest version of the record.

Now what Zapier does not do for Atlas. No trigger fires when a person, a note or a list is created; only updates and list membership are watched. None of the seven searches can create the missing item for you, since the app exposes no find-or-create. And almost every action needs a Person ID, which can be your own identifier or the internal Atlas one, so you have to know which one you are passing.

The same app also has an Atlas Make integration page, and the Make vs Zapier comparison helps you choose between the two.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet below and in the Zap editor, each explained once and then used as is.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in Atlas that starts the Zap, such as a person being updated. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that creates, updates, adds or deletes something in Atlas for you.
Task
The unit Zapier bills: one action that completes successfully. Your plan is a monthly count of those tasks.
Instant trigger
A trigger the app reports itself, the moment the event happens. All five Atlas triggers work this way.
Filter
A step that lets the Zap continue only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already in Atlas, a person, a list, a note, so the steps that follow can use it.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes it one, and it needs a paid plan.
Cost

What it really costs

Atlas is not a premium app on Zapier, so you can start on the free plan. What you pay is counted in tasks.

  • Free plan100 tasks a month, unlimited Zaps
  • Steps on the free planTwo: one trigger, one action
  • Premium appNo, works from the free plan
  • Instant triggers5 of 5, no waiting whatever the plan

The trigger never costs a task. Every action that succeeds counts on its own, so a Zap that creates a note and then adds the person to a list uses two tasks per run, and an action that fails costs nothing. The free plan is limited to two steps: one trigger, one action. Add a search step, a filter or a second action and the Zap becomes multi-step, which needs a paid plan. With Atlas, that limit bites early: a note needs a creator, a deletion needs a note ID, and both usually come from a search.

Connect

Connect your Atlas account

  1. 01

    Start from Apps

    In Zapier, open the Apps page and click + Add connection. A connection is your Atlas account linked to Zapier once, then reused by every step that talks to Atlas.

  2. 02

    Find Atlas

    Search for Atlas in the dialog, select it, then click Add connection. A new tab opens on the Atlas side so you can sign in with the Atlas account the Zap should act for.

  3. 03

    Sign in and allow access

    Log in to Atlas in that tab and grant Zapier access. You need an Atlas account, plus read or write access to any records you do not own yourself and want the Zap to touch.

First Zap

Your first Zap: log who added a person to a list

GoalEvery time someone joins an Atlas list, a note appears on their record, signed by the teammate you pick.

  1. 01

    Build: pick the trigger

    Create a Zap, choose Atlas as the trigger app and List Member Added as the event, then select your Atlas connection. The trigger is instant, so you will see a lightning bolt.

  2. 02

    Test the trigger

    Run the test: Zapier pulls the three most recent items from the connected account. Pick one, so the next steps are mapped on a real person rather than an empty sample.

  3. 03

    Add the Get User search

    Add a step and pick Get User from the search section. Give it the email a teammate used to register with Atlas: the note needs a creator, and this is where it comes from.

  4. 04

    Add Create Note

    Add the action Create Note. Map the Person ID from the trigger, the creator from Get User, and write the note body. With a search, this is a multi-step Zap on a paid plan.

  5. 05

    Test, then Publish

    Test the search and the action, then check the person in Atlas: the note should be there. Click Publish. From then on, every action that succeeds on a run counts as a task.

Triggers

The 5 Atlas triggers

5 events start a Zap when something happens in Atlas, and 5 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Company Updated

Instant trigger

In Zapier“Triggers when a company is updated.”

Fires whenever a company record changes in Atlas. It is the only trigger of the app that works at company level; the four others follow people and lists.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a partnerships lead wants any change on a target account pushed to the team the minute it happens, with the company looked up through Get Company.
Watch out
most Atlas actions work on people, not companies, so a Zap started here often needs a search before it can act.
2

Custom Field Value Updated

Instant trigger

In Zapier“Triggers when a the custom field value for a person is updated.”

Runs when the value of a custom field changes for a person. Custom fields hold whatever your team chose to track on people, so this is the trigger that follows your own process.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a recruiter flips a candidate's stage field and wants the person filed into the matching shortlist.
Watch out
do not answer it with Upsert Custom Field Value for Person on the same field, or the Zap restarts itself.
3

List Member Added

Instant trigger

In Zapier“Triggers when an person is added to a list.”

Starts the Zap as soon as a person is added to an Atlas list. Lists are how teams group targets, so being added to one is usually a decision someone just made.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a fund adds a founder to its pipeline list and wants a note logged on the person at once.
Watch out
a Zap that answers with Add Person to List can set itself off again.
4

List Member Removed

Instant trigger

In Zapier“Triggers when an person is removed from a list.”

The reverse case: someone is taken off a list. Removal often means a lead went cold, a candidate was declined or a deal closed, and that change usually deserves a trace.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a sales team removes a contact from its active list and wants a note logged on that contact the moment it happens.
Watch out
removals made before the Zap was published are never picked up.
5

Person Updated

Instant trigger

In Zapier“Triggers when a person is updated.”

Reacts whenever a person record changes in Atlas. It is the broadest people trigger of the app, the one to choose when you care about any edit rather than a specific field.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a talent partner wants each edit on a tracked person to start a review routine.
Watch out
pairing it with Update Person on the same people loops, since the update counts as a change and fires the trigger again.
Actions

The 10 Atlas actions

Atlas gives you 10 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Person to List

Action

In Zapier“Add a person to a list”

Puts a person on a list. Both the list and the Person ID are required, and the ID can be yours or the one Atlas exposes.

When to use it
a field change or an outside event should file the person into a shortlist.
Watch out
List Member Added will see each addition this makes.
2

Create List

Action

In Zapier“Creates a list”

Creates a new list in Atlas, and only asks for a name. It is the lightest action of the app to set up.

When to use it
each new campaign or hiring round should get its own list from the start.
Watch out
later steps will need this list's ID, so test once and see where it comes back.
3

Create Note

Action

In Zapier“Creates a note”

Writes a note on a person. Three fields are required: the Person ID, the creator (the Atlas user who signs the note) and the note body.

When to use it
record what happened to a person, such as a list change or an outside event.
Watch out
the creator is a user, so pair it with Get User when you only have an email.
4

Create Person

Action

In Zapier“Creates a person”

Adds a person to Atlas. The only required field is the External Person ID, the identifier your own system uses for that person.

When to use it
a contact appears in another tool and should exist in Atlas too.
Watch out
that external ID is what later steps will look the person up by, so keep it stable.
5

Delete List

Action

In Zapier“Deletes a list”

Deletes a whole list, identified by its List ID. That ID also shows in the address bar when you open the list in Atlas.

When to use it
close the list of a finished campaign once its work is done.
Watch out
test it on a throwaway list first, since the run touches live data.
6

Delete Note

Action

In Zapier“Deletes a note”

Deletes a note, which takes two required values: the Person ID the note belongs to and the note's own ID.

When to use it
clear notes written by an earlier automation that turned out wrong.
Watch out
without the note ID you need Get Note first, so plan a search step.
7

Remove External Identifier From Person

Action

In Zapier“Removes a person”

Works on a person through their External Person ID only, and its name and its description disagree: the label talks about removing the external identifier, while Zapier describes it as removing a person.

When to use it
only after a test on a throwaway person, to see in Atlas which of the two it actually does.
Watch out
the internal Atlas ID is not accepted here, only yours.
8

Remove Person From List

Action

In Zapier“Remove a person from a list”

Takes a person off a list without touching the person record itself. The list and the Person ID are both required.

When to use it
a deal closes elsewhere and the contact should leave the active pipeline list.
Watch out
List Member Removed will fire for every removal it makes.
9

Update Person

Action

In Zapier“Update a person”

Changes an existing person, found by their Person ID: your own identifier or the internal Atlas one that the triggers expose.

When to use it
details change in another tool and Atlas should follow.
Watch out
a Zap started by Person Updated should not run this on the same people, or it loops.
10

Upsert Custom Field Value for Person

Action

In Zapier“Upsert a Custom Field Value”

Sets a custom field value on a person, writing it whether a value is already there or not. It needs the Person ID and the custom field.

When to use it
keep a stage or score field current from another step.
Watch out
Custom Field Value Updated will fire on what this writes.
Searches

The 7 Atlas searches

7 search steps look for data that already exists in Atlas, so a later step can use it.

A search step fetches something that already exists in Atlas and hands it to the next steps. In the editor, the Atlas searches sit at the bottom of the Action event list, under SEARCH, and some fields offer + Add search step to insert one right where you need it. Whether a search wants an exact value or a close one is decided by Atlas, not by Zapier.

1

Get Company

Search

In Zapier“Triggers a company request.”

Fetches a company by its Company ID, which has to be the internal Atlas ID the triggers expose.

When to use it
right after Company Updated, to read the full company before acting on it.
Watch out
your own company identifiers are not accepted here.
2

Get Custom Field

Search

In Zapier“Triggers a custom field request.”

Fetches one custom field you pick: the field itself, not the value it holds on a person.

When to use it
a later step needs details of the field itself, not of a person.
Watch out
for the value held by a given person, use Get Custom Field Value for Person.
3

Get Custom Field Value for Person

Search

In Zapier“Triggers a custom field value request.”

Reads what one custom field holds for one person. It requires the Person ID and the field.

When to use it
before a filter, to let the Zap continue only for people at a given stage.
Watch out
a filter on top of it adds one more step, which a paid plan covers.
4

Get List

Search

In Zapier“Triggers a list request.”

Looks up a list by its List ID: the internal Atlas ID from the triggers, also visible in the list's address in Atlas.

When to use it
check a list's details before adding people to it.
Watch out
it searches by ID, not by list name.
5

Get Note

Search

In Zapier“Triggers a note request.”

Fetches a single note, using the Person ID and the note's own ID, both required.

When to use it
read a note before deciding whether to delete or answer it in a later step.
Watch out
you need both IDs; the person alone is not enough to pick a note.
6

Get Person

Search

In Zapier“Triggers a person request.”

Finds a person from an ID, which can be the one your own system uses or the internal Atlas one.

When to use it
a list trigger hands you a person and the next step needs their full record.
Watch out
the ID that triggers hand over is the internal Atlas one; yours is the External Person ID set when the person was created.
7

Get User

Search

In Zapier“Triggers a user request.”

Finds an Atlas user, a member of your team, from the email they registered with.

When to use it
fill the creator of Create Note from a teammate's email.
Watch out
it only finds people with an Atlas account, not contacts stored in Atlas.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there, and the steps that depended on it are skipped. Switched on, the Zap carries on without the result.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create. None of the seven Atlas searches offers it, so creating a missing person or list takes a separate action.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one, which is the default, stop the Zap, or pass all of them on at once.
When it breaks

When it breaks

Zapier ties no help article to Atlas and records no limit of its own. The failures that show up come from how Zaps work in general, and from the IDs Atlas relies on.

Four cases to know before you publish. When a Zap still misbehaves, the Zapier troubleshooting page is the next step.

  • The Zap triggers itself

    A Zap that writes into what its own trigger watches fires again: Update Person after Person Updated, Add Person to List after List Member Added. It loops and burns tasks fast.

  • The wrong kind of ID

    Some fields take your own ID or the Atlas one, Get Company and Get List want the Atlas one, and Remove External Identifier From Person only accepts yours. Check that field first when a step fails.

  • Nothing from before

    A Zap only reacts to what happens after you publish it. People updated or lists changed earlier are never picked up, and moving that backlog is a separate job.

  • A bulk import gets held back

    Import or update many people at once and the triggers can send a huge batch. Zapier's flood protection may then hold those runs back.
Need help

Need help automating Atlas with Zapier?

A person reads every message.

FAQ

Atlas Zapier integration: FAQ

01Is the Atlas Zapier integration free?
Yes, you can use it on the free Zapier plan, because Atlas is not a premium app. That plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. With Atlas, that limit comes quickly: as soon as you add a search to find a person or a user, or a filter, or a second action, the Zap becomes multi-step and needs a paid plan. Many useful Atlas Zaps need a search, so plan for that.
02How many Zapier tasks does an Atlas Zap use?
One task per action that succeeds, each time the Zap runs. The trigger costs nothing. A Zap that writes one note per new list member uses one task per member; one that writes the note and then updates a custom field uses two. An action that fails is not counted. Volume is the thing to watch: Person Updated fires on every edit, so a team that edits records all day can run a Zap far more often than expected, and every run spends tasks on each completed action.
03Do Atlas triggers fire in real time?
Yes, all five of them. They are instant triggers: Atlas tells Zapier the moment the event happens, and the plan you are on makes no difference, the free one included. The polling intervals of Zapier's plans, 15 minutes on Free down to 1 minute on Team and Enterprise, do not apply to any Atlas trigger. In the editor, a Zap that starts from an instant trigger shows a lightning bolt, which is a quick way to confirm it.
04What does it take to connect Atlas to Zapier?
An Atlas account, plus access to the records you do not own and want the Zap to read or change. You connect from the Apps page of Zapier: add a connection, choose Atlas, sign in on the tab that opens and grant access. The connection is reused by every Zap afterwards. The part that needs thought comes after: most actions require a Person ID, and you have to decide whether you map your own identifiers or the internal Atlas ones.
05Which ID does Atlas expect in a Zap?
It depends on the step, and that is the main trap of this app. Most people fields accept either the ID your own system uses or the internal Atlas ID that the triggers expose. Get Company and Get List want the Atlas ID. Remove External Identifier From Person only takes your external ID and refuses the Atlas one. Create Person sets that external ID in the first place, so keeping it stable across tools saves a lot of failed steps.
06What if the Atlas operation you need is not in the list?
Check first whether two operations can do it together. There is no trigger for a new person, note or list, but Person Updated and the list triggers cover many cases, and a search plus a filter can narrow them down, at the cost of a multi-step Zap. On the action side, the ten actions and seven searches listed here are all there is, and none offers find-or-create. If the gap remains, the answer is usually another tool, since Zapier cannot add what the app does not expose.
07Zapier, Make or n8n for Atlas?
It depends on criteria, not on a ranking. Coverage first: check that the 5 triggers, 10 actions and 7 searches listed here do what you need, because nothing else exists on Zapier. Steps next: Atlas Zaps often need a search before an action, and every extra step pushes you to a paid plan. Then volume, since every successful action costs a task. Atlas also has a dedicated Make page on this site.
Same platform

Other docs you might need on this stack.

Browse all integrations