LinkedIn Ads

The connection the whole product runs on, authorised through OAuth with three scopes: r_ads_reporting, rw_ads and r_organization_social. It syncs campaigns, ad sets, creatives, spend, the companies your ads reached and audience detail like industry, seniority and company size. The first sync backfills 90 days, and after that data pulls weekly, every Monday at 00:00 GMT. The rw_ads scope is what lets ZenABM push exclusions back into your live ad sets.

HubSpot

The deepest integration and the one that unlocks half the product. Inbound it pulls pipelines, deal stages and lifecycle data, which powers influenced revenue, ABM stage rules, and the Deals, Sources and Contacts screens. Deals and lifecycle data refresh daily. Outbound it writes a ZenABM LinkedIn Metrics property group onto the company object, covering ABM stage, active campaigns, intents, lifetime impressions, clicks, engagements, spend and engagement score, and that push runs once a week on Monday. Available on every tier including Starter.

Salesforce

One directional. It pulls opportunities in so advertised accounts can be tied to pipeline and closed revenue, and deal signals become available inside ABM stage rules. There is no write back onto Salesforce accounts, so reps see the engagement data only if they open ZenABM. Company matching runs automatically with a dedicated page for fixing duplicates and misses. Salesforce is excluded from the $59 Starter tier and starts at Growth.

Webhooks

The route to everything ZenABM does not integrate with directly. A filter builder scopes the data, for example companies sitting in the Interested stage, and a payload builder picks the fields. Delivery can be sequential, one company per request, or batched into a single array. Webhooks fire automatically after each Monday sync, and can be triggered by hand in between. Growth tier and above.

Clay, Slack, Outreach and Salesloft

All of these are marketed as destinations for intent signals and all of them are reached over a webhook rather than a native connector. ZenABM's own docs name Clay as the common case and recommend sequential delivery because Clay wants one row per request. That works cleanly, though it inherits the weekly cadence, so a Clay table fed this way refreshes on Mondays instead of continuously.

API and MCP server

A REST API at app.zenabm.com/api/v1 using bearer tokens, limited to 100 requests a minute, with endpoints for companies, ad sets, campaigns, ABM campaigns, deals, job titles, stages, contacts and a LinkedIn ad library. The MCP server at app.zenabm.com/api/mcp exposes 57 tools, of which 4 change live ad delivery and are flagged destructive, plus 15 prebuilt ABM workflows as slash commands. Both start at Growth.

What is missing

No Zapier or n8n app, no Pipedrive or Attio connector, and no second ad platform as a real data source. The homepage promises multi channel attribution across Google Ads, Reddit Ads and organic, but the Sources screen that delivers it is built from your HubSpot contacts' last touch property history and requires HubSpot, so it re-reads what your CRM already recorded rather than identifying companies on those channels. There is also no impression capping, which LinkedIn has not opened to ZenABM.