ABM.dev Zapier integrationAutomate ABM.dev with Zapier.
The ABM.dev Zapier integration gives you 1 trigger, 2 actions and 1 search. Queue a person or a company for enrichment, hear about it the instant the job is done, then pull the finished job by its ID. Here is what every step does, costs and breaks on.
Beta app Zapier still marks this integration as beta.
Verified Trustpilot reviews · AI, automation & growth agency
What the ABM.dev Zapier integration actually does
ABM.dev is an account-based marketing service built for AI agents: you hand it a contact or an account, and it goes looking for the data that fills in the gaps. Zapier wires it to your other tools through Zaps, small automations where one event starts a chain of steps. On this app you get one trigger, two actions and one search, and the app works on the free plan.
Three setups cover most of what people build with it.
A webinar list that enriches itself. A marketer sends each new registrant to Enrich a Person. ABM.dev queues the job and hands back its ID straight away, so nobody copies names into a research tool by hand.
A ping in the sales channel when a job lands. New Enrichment Completed fires as soon as a job finishes. A Find an Enrichment by ID step then fetches that job, and a Slack message tells the rep that the record is ready to work.
Target accounts researched in one pass. An analyst building a list of accounts runs each company through Enrich a Company instead of opening every website in a tab.
What Zapier does not do here: neither action gives you the enriched result. Both return a queued job ID, and the data only exists once the job is finished. There is no operation to edit, cancel or delete a job either, and nothing that pulls jobs from before your Zap was switched on. The app is still flagged as beta by Zapier, so its operations can change.
Comparing platforms before you commit? n8n vs Zapier is a good place to start.
Zapier vocabulary in one minute
Seven words come back on every line of this page. Here they are in plain English.
- Zap
- The automation you build in Zapier: one trigger, followed by one or more actions that run every single time that trigger event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for that event to happen.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something on your behalf in another app.
- Task
- The unit Zapier bills you for: one action your Zap completes successfully. The number on your plan counts those, nothing else.
- Polling vs instant trigger
- A polling trigger is checked on a timer by Zapier. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap carry on only when the incoming data meets a condition you set, and quietly stops it otherwise.
- Search step
- A step that looks up something that already exists in an app, so the steps after it can reuse whatever it found.
What an ABM.dev Zap really costs
ABM.dev is not a premium app, so it runs on the free plan. The catch sits in the size of the Zap, not in the app.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap size2 steps: 1 trigger, 1 action
- Premium appNo, works on the free plan (beta)
- ABM.dev triggerInstant, no polling interval
Zapier only bills completed actions. The trigger costs nothing, and an action that fails is not counted. Each successful action counts on its own, so a Zap with three actions uses three times more than a one-action Zap. The free plan gives you 100 tasks a month, but only Zaps of two steps. Add a filter or a Find an Enrichment by ID search and you have a multi-step Zap, which needs a paid plan. Good news on timing: the ABM.dev trigger is instant, so the polling grid below never slows it down.
Connect ABM.dev to Zapier in 3 steps
- 01
Open your Apps page
In your Zapier account, go to Apps and click + Add connection. A connection is your ABM.dev account linked once, then reused by every step that touches ABM.dev.
- 02
Pick ABM.dev
Type ABM.dev into the search box of the dialog, select it, then click Add connection. You need an ABM.dev account already, plus access to anything you do not own that the Zap should touch.
- 03
Sign in and allow access
A new tab opens on ABM.dev. Sign in, then grant Zapier access to the account. The connection now shows up on your Apps page and in every ABM.dev step you add.
Your first Zap: alert the sales team when a job finishes
GoalEach time ABM.dev finishes an enrichment, fetch that job and post a heads-up in the sales channel.
- 01
Create the Zap
Start a new Zap and choose ABM.dev as the app that kicks things off, with New Enrichment Completed as the event. Pick the connection you just added.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent jobs of the connected account, so you build the rest of the Zap on a real one rather than a blank sample.
- 03
Add the search
Add Find an Enrichment by ID as the next step and map the Enrichment ID that the trigger sent into its only required field.
- 04
Add the message
Add the Slack step, pick the channel, and map what the search returned into the text. Test each step once and read what came back before going on.
- 05
Publish
Click Publish to switch the Zap on. Remember that the search makes this a three-step Zap, so it needs a paid plan to run.
ABM.dev triggers
1 event starts a Zap when something happens in ABM.dev, and one of them is instant: the app calls Zapier straight away, whatever your plan.
New Enrichment Completed
Instant triggerIn Zapier“Triggers when an enrichment job finishes for your workspace. Use this to push enriched contacts into your CRM, send notifications, or score leads. The numeric Enrichment ID it emits feeds straight into the "Find an Enrichment by ID" search.”
This is the moment your data is ready. When an enrichment job wraps up in your workspace, the Zap starts and carries the numeric Enrichment ID of that job, which is exactly what the search below expects.
ABM.dev actions
ABM.dev gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Enrich a Company
ActionIn Zapier“Submit a company to ABM.dev for enrichment. Returns the queued job id immediately — chain with the "New Enrichment Completed" trigger to act on the result.”
Sends one company to ABM.dev and gets the queued job ID back immediately, not the researched account itself.
Enrich a Person
ActionIn Zapier“Submit a person to ABM.dev for enrichment. Returns the queued job id immediately — chain with the "New Enrichment Completed" trigger to act on the result.”
Hands a single contact over to ABM.dev and returns the job ID the second the request is queued.
ABM.dev search
1 search step looks for data that already exists in ABM.dev, so a later step can use it.
A search step looks something up that already exists instead of creating it. In the editor, ABM.dev's search sits at the bottom of the Action event list, under SEARCH. Three settings decide what happens when the lookup does not go as planned.
Find an Enrichment by ID
SearchIn Zapier“Looks up an enrichment job by id. Pair with a Delay step after Enrich-a-Person/Company to build a synchronous "wait then fetch" Zap.”
Fetches one enrichment job from its numeric ID, the one returned by either enrichment action. A dropdown lets you pick a recent job while you set it up.
The three settings every search exposes
- Successful if no search results are found?Left as it is, a search that comes back empty stops the Zap there and skips the steps that needed it. Turn it on and the Zap carries on without the data.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. ABM.dev offers no such variant, so you will not see it on this search.
- If multiple search results are found?Three ways out: keep the first match, which is the default, stop the Zap, or pass every match on to the next steps.
When an ABM.dev Zap breaks
Zapier ties no help article to ABM.dev, so the known failure points are the ones every Zap shares.
Most of them come from the fact that enrichment runs in two stages: queue a job, then catch it when it ends. For stuck runs in general, the Zapier troubleshooting guide walks through the usual checks.
Old jobs are never picked up
A Zap only reacts to what happens after you switch it on. Enrichments finished before that stay out of reach, and moving that backlog is a separate job.The trigger feeds an enrichment action
Put Enrich a Person after New Enrichment Completed and each finished job queues a new one, which finishes and fires the Zap again. Tasks drain fast.A bulk run gets held back
Queue a large batch of enrichments at once and the trigger can return a sudden flood. Zapier's flood protection may hold those runs back for review.The search finds nothing
If Find an Enrichment by ID gets a wrong or empty ID, the Zap stops at that step by default and the steps after it are skipped.
Need help automating ABM.dev with Zapier?
A person reads every message.
