5 minIntegration · Beta
Zapier
Trigger ABM.dev enrichments from any of Zapier’s 7,000+ apps and route enriched contacts, campaigns, and webhook events back into the rest of your stack.
Public-beta partner app
The ABM.dev Zapier app is in private beta while we work through Zapier’s partner-program review. If you’d like an invite to the beta zap, drop us a line at partners@abm.dev.
In this guide
- Authenticate Zapier with your ABM.dev API key
- Use ABM.dev triggers (enrichment.completed, campaign.status_changed)
- Use ABM.dev actions (enrich a person, queue a campaign)
Authentication
The ABM.dev Zapier app uses an x-api-key header. Generate a key under Settings → API Keys and paste it into the Zapier auth screen.
Sanity-check your key from the terminal
curl -s https://api.abm.dev/v1/me \
-H "x-api-key: YOUR_API_KEY" | jq .Triggers
ABM.dev triggers are backed by the same webhook events you can subscribe to directly. The Zapier app polls or receives push events for each.
enrichment.completed— fires when an enrichment job finishescampaign.status_changed— fires when a campaign moves stageperson_finder.completed— fires when a person-finder job returns results
Actions
- Enrich a person by email or LinkedIn URL
- Enrich a company by domain
- Queue a contact into a campaign