Integration

Intercom

Plandalf integrates with Intercom as a crm platform.

crm

Visit Intercom →

What it does

Sends emailEmail GIF promo Notifications
Runs automationsAutomation Purchase automations
Custom HTML blocksTotally custom checkout layouts Buy button
Per-recipient timer imagesEmail GIF promo Deadline campaigns
Open APIAPI SDK

Product surfaces

Where Intercom fits in the buying workflow

Integrations work best when the checkout surface, payment state, invoice record, and post-purchase automation all point at the same commercial object. These product screens show the Plandalf controls that should be configured before Intercom receives checkout, payment, tax, or workflow context.

The Numi offer editor showing layout, product, theme, automation, invoice, and settings controls.

Offer configuration stays visible

Use Offers to decide what Intercom receives: product, price, buyer, checkout mode, invoice, and automation context.

Offers Products Prices Checkout templates

The Numi checkout elements palette showing content, interactive, and selling blocks.

Checkout layout and selling blocks stay editable

Before Intercom enters the stack, operators still need checkout templates, products, prices, coupons, order bumps, upsells, and branded offer content they can inspect.

Checkout templates Order bumps Upsells Coupons

The Numi offer editor automation tab showing sequence controls beside the checkout canvas.

Purchase events can start follow-up

Intercom should fit into the work after checkout: fulfilment, records, CRM updates, support context, webhooks, and sequences.

Purchase automations Automations Sequences Webhooks

Overview

Intercom blends live chat, outbound email, and in-product messaging. For promo enrolment the relevant surface is its Series product — a visual workflow with rule-based entry and optional webhook steps.

What Plandalf does here

Countdown in outbound email — an <img> tag with Intercom’s {{ email }} attribute renders per recipient.
Series-driven enrolment — webhook blocks POST to the promo’s catch URL; on plans without outbound webhooks, Zapier covers the same path.

Setup templates

Drop-in implementations

Copy-paste setups for the most common ways to wire Intercom into Plandalf.

promo · email

Drop the Plandalf countdown image into an Intercom email

In the Intercom email editor, paste this <img> tag into an HTML block. {{ email }} is Intercom's attribute token — it substitutes the recipient's email address at send time.

<img
  src="{{ promo.countdown_url }}?ref={{ email }}"
  alt="Time remaining on this offer"
/>

promo · automation

Enrol Intercom contacts via a Series

In Intercom, go to Proactive Support → Series → New series.
Pick an entry rule — a segment, an event, or a specific user attribute change that marks a new promo participant.
Add a block: Outbound webhook (on plans that include it) or fall back to Zapier on plans that don't.
URL:
```
{{ promo.catch_url }}
```

Method POST, body:

{"email": "{{ email }}", "ref": "{{ email }}"}

Set the series live.

Automation graph

Connecting Intercom

How Intercom participates in Plandalf sequences: what events it exposes upward, and what actions Plandalf can perform on it.

Triggers from Intercom

Events Plandalf can subscribe to through webhooks, API work, checkout state, payment context, and connected integrations.

intercom.subscriber_added: Fires when a new subscriber is added to Intercom.
intercom.automation_step_reached: Fires when a contact reaches a designated step in a Intercom automation.
intercom.webhook: Fires when Intercom POSTs to a Plandalf webhook URL — use for anything not covered by a native trigger.

Actions on Intercom

Things Plandalf sequences can do after checkout, payment, invoice, customer, or deadline events.

intercom.add_subscriber: Add a contact to a list or audience in Intercom.
intercom.tag: Apply a tag or segment to an existing Intercom contact.
intercom.send_email: Send a one-off transactional or broadcast email through Intercom.
intercom.start_automation: Enrol a contact into a Intercom automation.
intercom.upsert_contact: Create or update a contact record in Intercom.
intercom.create_deal: Open a new deal or opportunity in Intercom.
intercom.custom_api_call: Hit any Intercom REST endpoint with a templated payload.

Embeddable surfaces: Plandalf countdown image and buy button HTML · Per-recipient countdown GIF with merge-tag substitution

Example sequence

trigger: stripe.payment_succeeded
actions:
  - intercom.add_subscriber:
      list: paying-customers
      tag: tier-${plan}
  - plandalf.grant_entitlement: ${product_slug}

Pair it with

Connect Intercom with…

Platforms whose roles complement Intercom inside a Plandalf sequence.

Intercom + ActiveCampaign

Compose Intercom and ActiveCampaign programmatically via the Plandalf SDK.

Intercom + beehiiv

Compose Intercom and beehiiv programmatically via the Plandalf SDK.

Intercom + Kit (ConvertKit)

Compose Intercom and Kit (ConvertKit) programmatically via the Plandalf SDK.

Intercom + Customer.io

Compose Intercom and Customer.io programmatically via the Plandalf SDK.

Intercom + Drip

Compose Intercom and Drip programmatically via the Plandalf SDK.

Intercom + Flodesk

Compose Intercom and Flodesk programmatically via the Plandalf SDK.

See all integrations →

Integration methods

How Intercom connects to Plandalf

Each method below is the minimum viable setup. Pick the one closest to how you already use Intercom with checkout, payments, invoices, webhooks, API work, SDK checkout, and integrations.

Method 1
Embed a Plandalf buy button
Drop the Plandalf embed script into a Intercom HTML block and tag any element with `data-plandalf-present` to open the configured flow on click.
```
<script src="https://cdn.plandalf.com/embed.js" async></script>

<button data-plandalf-present="offer_abc123">
  Buy now
</button>
```
Method 2
Drop in a per-recipient countdown image
Add an HTML block to any Intercom email and paste the Plandalf countdown URL. Intercom's merge tag `{{ contact.email }}` substitutes per recipient so each subscriber sees a timer pegged to their own deadline.
```
<img
  src="https://cdn.plandalf.com/timers/{TIMER_ID}.gif?ref={{ contact.email }}"
  alt="Time remaining on this offer"
  width="600"
  height="120"
/>
```
Method 3
Enrol from an automation step
Inside Intercom's automation builder, add a Webhook step that POSTs the contact to a Plandalf sequence catch URL. Use this to mirror Intercom journey logic into Plandalf without re-building the segmentation.
```
{
  "email": "{{ contact.email }}",
  "sequence": "post-signup-onboarding",
  "source": "intercom"
}
```
Method 4
REST API webhook
For anything not covered by a native trigger, configure a Intercom webhook to POST to Plandalf. The payload is forwarded into the sequence as `${event}`.
```
curl -X POST https://api.plandalf.com/v1/webhooks/intercom \
  -H "Authorization: Bearer $PLANDALF_API_KEY" \
  -H "Content-Type: application/json" \
  -d @event.json
```

Official Intercom docs and sign-up: www.intercom.com

FAQ

Common questions about the Intercom integration

Do I need a paid plan to use Intercom with Plandalf?

Plandalf itself is free to connect. Intercom's native webhook step is on its paid tiers — on the free plan, route the trigger through Zapier instead, which still works end-to-end.

How long does setup take?

Under 10 minutes. OAuth (or paste an API key), pick the lists/segments you care about, and you're live. No code unless you want it.

Can I disconnect Intercom later without losing data?

Yes. Disconnecting only revokes the credentials — historical events Plandalf fired stay in your sequence logs, and Intercom's own records are untouched. You can reconnect any time and resume from the last seen event.

Does Plandalf store Intercom data?

Plandalf stores the minimum IDs needed to address a record in Intercom plus a log of events Plandalf fired. Source-of-truth data stays in Intercom.

What if my crm need isn't covered by the actions or triggers listed here?

Use the generic `intercom.custom_api_call` action or the inbound `intercom.webhook` trigger. Anything Intercom's REST API can do, a Plandalf sequence can drive.

Is there a usage limit?

Plandalf respects Intercom's API rate limits and backs off on 429s. For very high-volume use cases, ask about a dedicated worker pool.

Where do I find Intercom's own documentation?

Intercom's homepage at https://www.intercom.com links to their developer docs. For Plandalf-side questions about the Intercom integration, see the Plandalf docs.