Your store, your CRM, your support desk, and your analytics, connected so data arrives as events campaigns can act on. No middleware, no per-connector bill.
Every one of these is available on every plan. Connect them from Settings, then Integrations. Shopify uses a custom app in your store admin. WooCommerce uses REST credentials. EngageApp registers the store webhooks after you connect.
E-commerce
Connect your Shopify store so orders, checkouts, and customers arrive as events for campaigns and cart recovery. Autopilot needs a sending channel in Settings — store events are mapped automatically after connect. See Autopilot activation docs.
Learn moreE-commerce
Connect your WooCommerce store so orders and customers arrive as events for campaigns and cart recovery. We register the store’s webhooks for you. Autopilot needs a sending channel in Settings — store events are mapped automatically after connect. See Autopilot activation docs.
Learn moreCRM
Keep contacts in step with your CRM, trigger campaigns when a deal moves, and write engagement back onto the record your salespeople actually read.
Learn moreSupport
Turn support conversations into automation signals. Follow up after a ticket is resolved, win back a low CSAT rating, or hold marketing back while a customer is mid-conversation.
Learn moreAnalytics
Pull each contact’s UTM campaign params from your PostHog project onto their profile (via the “Sync UTM” action) so you can segment and measure ROI by campaign.
Learn moreTelephony
Turn calls into automation signals. A missed call can trigger a follow-up text, and agents see who is calling before they answer.
Learn moreData
Let campaigns append a row to one of your spreadsheets with the “Add row to Google Sheet” action — contact fields plus any custom columns you define.
Learn moreData
Save the areas you care about, then trigger campaigns on a weather condition, branch on it, gate sends by it, and use {{ weather.* }} in your copy.
Learn moreBuilding now. Tell us if one of these is what's holding you back — it moves things up the list.
Attribute UTMs to contacts from GA4. Requires a BigQuery export on your GA4 property and a matching user ID.
Every channel points at a provider you own, so your sender reputation, your rates, and your numbers stay yours. Credentials are encrypted at rest.
Point it at whatever already sends your transactional mail. Credentials are encrypted at rest.
Set-up guideBring your own account, or use a platform-managed sender where one is offered.
Set-up guideOfficial Meta Cloud API with template approvals. Connect with Meta in a few clicks.
Set-up guideFCM v1 with your own service account, reaching Android, iOS, and web.
Set-up guideRender takeovers inside your own product with a published SDK on either platform.
Set-up guideDefine your own channel — we POST the rendered message wherever you point us.
Set-up guidePublic secret keys cover ingest — contacts, events, and enroll. Bots use scoped Action keys to read campaigns and Autopilot. Full workspace operations stay on the signed-in dashboard API, and anything we don't integrate with yet you can reach with a webhook step.
The dashboard talks to a JWT-authenticated REST API. Public secret keys (df_) are ingest-only — contacts, events, and enroll — not campaign or billing access. Bot operators use scoped Action keys.
API referenceSend any behavioural event from your backend and trigger, branch, or wait on it inside a campaign. No fixed schema — your event names, your properties.
Event guideIdentify contacts, update attributes, and enrol people into campaigns from your backend with a workspace-scoped secret key (df_). That key does not grant dashboard or campaign-authoring access.
Integration guidePublished client SDKs that identify the current user and render in-app takeovers inside your web app or Flutter app.
SDK docsCall your own endpoint as a campaign step — with the contact, the campaign, and your own payload — to reach anything not on this page.
Webhook actionsScoped Action keys (act_) so a customer bot can read credits, campaigns, segments, channels, and Autopilot. Catalog: /api/v1/actions/openapi.yaml. Secret df_ keys are rejected here.
Actions catalogIssue and rotate ingest (df_), publishable (pk_), and scoped Action (act_) keys separately, so a key you hand to one system can be revoked without touching another.
Managing keysEvery integration is available on every plan, including the free starting credits. Nothing here needs a sales call to switch on.