ActiveCampaign lists 1,000+ apps in its official directory, reaches roughly 9,000 more through Zapier, and leaves the rest to the v3 REST API, the eComm GraphQL API, webhooks and CX Apps. That breadth is the reason teams buy it: it is a marketing-automation and CRM layer built to sit on a stack it did not build. The one thing the catalogue cannot supply is a mail relay — ActiveCampaign has no SMTP service, so transactional mail leaves through a separately billed Postmark account connected as an app.
Read the third number before you plan a build. The limit is scoped to the account, not to the API key, so a Shopify sync, a Zapier zap and an MCP client all draw on the same 5 requests per second. Two chatty integrations are enough to hand the third a 429. Bulk endpoints and webhooks, not polling loops, keep a stack under it.
The 26 connectors below are the ones that matter for a stack decision, grouped by the job they do. Every entry links to its official listing. The full catalogue lives at the ActiveCampaign apps directory; the developer surface behind the custom ones is documented at developers.activecampaign.com.
Adds a “Send a transactional email” action that delivers through your own, separately billed Postmark account on separate sending IPs.
Connects a Twilio account so automations can send SMS and handle replies inside the workflow builder.
Parses received mail so an inbound message can act as an automation trigger rather than a manual inbox task.
Deep Data connector syncing orders, products and abandoned carts into contact records for revenue-attributed automations.
One of the five officially listed Deep Data connectors, pushing WordPress store orders and cart activity in.
Deep Data connector bringing order and product history into contact profiles for purchase-based segmentation.
Deep Data connector syncing Square point-of-sale and online transaction data onto the matching ActiveCampaign contacts.
Deep Data connector for Adobe Commerce and Magento stores, syncing order and catalogue data for ecommerce automations.
Syncs payment, subscription and churn events so billing state, not just email behaviour, drives automations.
Two-way sync for teams running ActiveCampaign as the marketing layer over an existing Salesforce CRM.
Brings ticket activity into contact records so support events can trigger follow-ups or suppress marketing sends.
Pushes booking, reschedule and cancellation events into ActiveCampaign to drive reminder and no-show sequences.
Syncs registrations and attendee data into ActiveCampaign for pre-event reminders and post-event follow-up.
Maps submissions to contacts and custom fields, so answers land as segmentable data rather than notification mail.
Sends entries into ActiveCampaign lists with field mapping and tagging — the default WordPress lead path.
Connects WPForms submissions to ActiveCampaign contacts, lists and automations without custom PHP.
Delivers NativeForms responses straight into ActiveCampaign contact records and lists.
Sends forms.app submissions to ActiveCampaign with automatic contact creation on first response.
Official ActiveCampaign plugin adding site tracking and embedded forms to a WordPress install.
Syncs WordPress user accounts and membership levels with ActiveCampaign tags for gated-content workflows.
Connects Webflow site forms to ActiveCampaign lists and automations with no code on the site side.
Passes Unbounce landing page leads directly into ActiveCampaign lists and automations.
Syncs course enrolments and completion progress for learner nurture and completion nudges.
Official AI connector letting Claude query ActiveCampaign data and run tasks through the first-party Remote MCP server.
Bridges ActiveCampaign to roughly 9,000 other apps through triggers and actions with no code.
Visual scenario builder for multi-step workflows that branch across several third-party services.
Two structural notes. The Deep Data label is not garnish: only five connectors sync full order, product and cart objects rather than flat contact fields, and that decides whether revenue attribution and cart recovery work out of the box. And the AI connector is a data server, not a sending server — its roughly 50 MCP tools cover contacts, deals, campaigns and automations, with no send-email tool, because there is no relay behind it.
For behavioural ecommerce messaging rather than CRM-shaped automation, compare the Deep Data set with Klaviyo; for transactional mail from your own backend, with Postmark or Customer.io. Teams wanting one vendor for marketing and relay both end up at Brevo or Mailchimp, since ActiveCampaign keeps relay traffic off its marketing IP pool by design.
The official directory advertises over 1,000 apps, the Zapier connector reaches roughly 9,000 more, and the API, GraphQL, webhook and CX App surfaces leave the ceiling open-ended. What constrains production is not catalogue size but the shared 5 requests per second per-account limit.
Both are Deep Data connectors: install from the apps directory, then authorise against your store. Once connected they sync orders, products and abandoned-cart activity onto contact records, which is what makes revenue reporting and cart recovery work. Historical backfill runs after connection, so give it time before judging segment counts.
Deep Data means the connector writes structured ecommerce objects — orders, line items, products, carts — not just contact fields, so automations can branch on purchase history and revenue attributes back to campaigns. ActiveCampaign officially lists five: Shopify, WooCommerce, BigCommerce, Square and Magento. Anything else arrives via API, webhook or Zapier with less object detail.
Install and authorise the Postmark app, which adds a “Send a transactional email” action to the automation builder. The prerequisite in ActiveCampaign’s own doc: an ActiveCampaign account and an approved Postmark account. ActiveCampaign acquired Postmark in 2022 but does not provision, bundle or resell it — you sign up and pay Postmark separately, from a free 100 emails per month tier. Mail then leaves on Postmark’s transactional IPs, not the marketing pool.
Salesforce has a native two-way app, the usual pattern when Salesforce stays the system of record and ActiveCampaign runs marketing. HubSpot is not in the verified native set here; the routes are Zapier, a webhook or the v3 REST API. Note that ActiveCampaign ships its own CRM with deals and pipelines, so pairing it with a second CRM means deciding up front which side owns stage changes.
Install the official ActiveCampaign WordPress plugin for site tracking and embedded forms, then add the form-specific connector for whichever plugin you use — Gravity Forms, WPForms and NativeForms all have listed apps that map fields and apply tags on submit, and WP Fusion links user roles and membership levels to tags for gated content. Do not stack two paths for the same form: duplicate submissions burn both your contact count and the 5/sec API budget.
This review follows our email infrastructure testing methodology. We disclose affiliate relationships in our editorial independence policy.