Support sees what a customer bought
A SaaS team records an upgrade event on the contact, so an agent opening a conversation sees the purchase date and plan without leaving the inbox.
Native on one side, webhook on the other
A Stripe-paid Plandalf checkout can be recorded in Intercom as an event through Send Webhook, and an Intercom Series can start a Plandalf countdown.
No credit card required. No coding required.
IntercomPlandalf has no Intercom steps and does not sync Stripe customers into Intercom. Intercom has a Stripe app of its own for that. For Plandalf sales, a Send Webhook step can submit a data event to Intercom's API for a contact it can find, and an Intercom Series webhook block can post back to a Plandalf catch URL.
| Event | From and to | Through | What happens |
|---|---|---|---|
| Checkout completed | Plandalf (paid via Stripe) → Intercom | Webhook | A Send Webhook step posts to Intercom's events endpoint with the buyer's email, an event name such as bought-pro-plan and the order details as metadata. If Intercom cannot find the contact it answers 404. |
| Invoice refunded | Stripe → Intercom | Webhook | A refund that succeeds in Stripe starts Invoice Refunded, so a webhook step can record a refund event that support can see on the contact. |
| Series webhook block | Intercom → Plandalf | Webhook | Plandalf's Intercom page describes an outbound webhook block in a Series, on plans that include it, posting to a Plandalf catch URL to enrol the person in a promo. |
| Stripe app inside Intercom | Stripe → Intercom | By hand | Intercom's Stripe app shows subscriptions and recent payments in the inbox and syncs billing attributes, with no Plandalf step involved. |
You need a published Plandalf checkout on Stripe, an Intercom access token that can write events, and buyers who can be found in Intercom by email.
Create an Intercom access token with write permission for events. The events endpoint uses a bearer token and serves regional hosts for the US, EU and Australia.
In Plandalf go to Automation, then My Sequences. Choose Plandalf, Checkout Completed, pick the offer and choose a recent checkout as the sample on the Test tab.
Choose Plandalf, Send Webhook, POST, and the events URL for your workspace region. Add an Authorization header with Bearer and your token.
Send event_name as a past-tense name, email as {{trigger.customer_email}}, created_at as a Unix timestamp counted in whole seconds and metadata with up to 10 flat keys such as offer and total.
Intercom wants a second-granularity Unix time. Check what the Get Current Date & Time step outputs in your chosen format on its Test tab before you map it into created_at.
A step test writes to a real contact, so use your own email, which Intercom must be able to find. Then run a Stripe test purchase with Run on test purchases switched on and read the run in the Events view.
A SaaS team records an upgrade event on the contact, so an agent opening a conversation sees the purchase date and plan without leaving the inbox.
A seller of two courses sends an in-app message only to contacts with the event for the advanced course.
A Series that tags new chat leads posts them to a Plandalf catch URL, so each lead gets a countdown on a launch price.
Checked October 26, 2026 against Plandalf's own setup guides and the vendor documentation: Intercom Help Center: Stripe app, Intercom developer docs: submit a data event.