4 integrations

Integrations

Connect ABM.dev to the tools your team already uses. Every integration listed here is backed by real platform functionality — no placeholders.

Before you begin

Most integrations need an ABM.dev API key or an OAuth-connected workspace. Generate a key in Settings → API Keys.

Native integrations (HubSpot, LinkedIn) install via OAuth from your Settings panel. Zapier and the Claude connector authenticate with an API key.

AI Assistants

Let Claude call ABM.dev tools directly through MCP.

Claude.ai Connector

Give Claude direct access to your ABM.dev workspace via MCP.

MCP serverOAuth 2.1 + PKCE90+ toolsDynamic client registration

View guide Setup

Data

Enrich profiles with first-party social data.

Session-authenticated LinkedIn enrichment for the contacts and companies you research.

Profile enrichmentCompany dataConnection routingPost history

View guide

Authentication

API-key integrations authenticate with an x-api-key header. OAuth integrations (HubSpot, LinkedIn) install from your Settings panel. The Claude connector uses the MCP OAuth 2.1 flow — no keys to paste.

Test your API key

curl -s https://api.abm.dev/v1/me \
  -H "x-api-key: YOUR_API_KEY" | jq .

Webhook events

Subscribe to these events from any webhook-capable service to react to ABM.dev activity in real time.

enrichment.completedEnrichment job finished processing

enrichment.approvedEnrichment result approved for CRM sync

campaign.createdNew campaign was created

campaign.status_changedCampaign moved to a new stage

contact.createdNew contact added to the platform

person_finder.completedPerson finder job returned results

curl -X POST https://api.abm.dev/v1/webhooks \
  -H "x-api-key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "url": "https://your-app.com/webhooks/abmdev",
    "events": [
      "enrichment.completed",
      "campaign.status_changed"
    ]
  }'

Next steps

API reference

Full endpoint documentation

How enrichment works

Understanding confidence scores