IntegrationMessaging destination
Intercom Integration - Route Product Events into Intercom
Meshes routes product events into Intercom through tag changes. That makes it easier to align support and lifecycle messaging with real user behavior instead of stale CRM notes or delayed backfills.
page.visitedtrial.expiredtutorial.started|Actionsadd_tagremove_tagThe event names shown here are examples. In Meshes, event types are fully customized for each organization.
What you can do
Supported actions with real product context behind them
Create the Intercom connection in Meshes with OAuth. Meshes loads the available tags from the connected Intercom workspace so rules can target live messaging and support context.
Intercom tags become more valuable when they reflect what the user just did in the product. A high-intent page visit, a stalled onboarding flow, or a trial state change can all be the trigger that makes the next support or lifecycle motion obvious.
Meshes lets you keep that logic in the event-routing layer. You connect Intercom once in your Meshes workspace, choose the tag action in the rule builder, and let Meshes deliver and retry the update when the downstream API needs help getting there.
add_tagAdd Intercom tags from product behavior
Apply the tags that should trigger support segmentation, lifecycle messaging, or in-app follow-up when the matching event happens.
remove_tagRemove tags when the behavior changes
Keep Intercom context accurate by removing the tag when the user no longer fits the state the workflow was designed for.
Common use cases
How Meshes teams usually put Intercom to work
These are the workflows where this destination tends to matter first. The point is to keep the product event, the destination action, and the operational retry path in one place.
Tag high-intent users after critical page visits
Use page.visited for high-value pages so Intercom can reflect current purchase or expansion intent.
Drive tutorial or onboarding follow-up from behavior
Use tutorial and onboarding events to apply the tags that determine which Intercom follow-up path should start.
See the tutorial-flow use caseMark lifecycle risk or trial state changes for support
Use trial.expired and related events to keep Intercom context current when customer support or success needs to step in.
Keep messaging context close to the event stream
Let the same Meshes event that updates your other systems also manage the Intercom tags that support and lifecycle teams rely on.
How it works
Connect the destination, define the rule, emit the event
In Meshes, the operating model is simple: create the connection in the workspace, create the rule, then let the event delivery layer handle the last mile.
Connect Intercom
Create the Intercom connection in Meshes with OAuth and confirm the tags you want are available in the connection action data.
Create routing rules in Meshes
Create rules for events like page.visited or trial.expired, choose add_tag or remove_tag, and map the user identity fields Intercom needs.
Emit the event and review delivery
Emit the event from your app or use Send Test Event in Meshes. Meshes delivers the Intercom tag change, retries transient errors, and records the full attempt history.
Event example
Emit the product event once
import MeshesEventsClient from '@mesheshq/events';
const meshes = new MeshesEventsClient(
process.env.WORKSPACE_PUBLISHABLE_KEY!,
);
await meshes.emit({
event: 'page.visited',
resource: 'page',
resource_id: 'pricing-enterprise',
payload: {
email: 'alex@northstar.io',
user_id: 'usr_2048',
path: '/pricing/enterprise',
referrer: '/pricing',
},
});Connection model
OAuth
Create the Intercom connection in Meshes with OAuth. Meshes loads the available tags from the connected Intercom workspace so rules can target live messaging and support context.
Why Meshes
Why teams use Meshes for Intercom
The benefit is not just that the destination is supported. It is that the destination sits inside the same fan-out, retry, replay, and delivery-visibility layer as the rest of your stack.
Behavior-based tagging stays close to the source event
Meshes lets page.visited and other product signals update Intercom directly instead of making support context depend on delayed syncs.
Retries protect messaging triggers
If the downstream Intercom API is temporarily unavailable, Meshes preserves the tag action so the workflow does not disappear silently.
You can coordinate Intercom with the rest of the stack
The same event that changes an Intercom tag can update CRM, email, or Slack in parallel from one Meshes rule set.
Customer-facing workspaces still fit the model
If each customer connects its own Intercom account through Meshes, you still keep one event-emission path inside your product.
Keep exploring
Related guides, use cases, docs, and comparison pages
These links are the next layer down: concrete patterns, supporting documentation, and the build-vs-buy context that usually comes up during evaluation.
Catalog
All integrations
Return to the integrations catalog and compare Intercom with the rest of the Meshes messaging and lifecycle destinations.
Open linkDocs
Intercom integration docs
See the Intercom connection flow, rule setup, and testing steps in the product docs.
Open linkUse Case
Page visit Intercom tutorial flows
See how behavioral events can trigger the support and lifecycle context that helps users reach the next step.
Open linkGuide
Page visit to Intercom high intent
See a concrete Meshes pattern for routing purchase-intent page visits into Intercom tags.
Open linkGuide
Tag Intercom users on trial expiry
See how trial lifecycle events can update Intercom so the right follow-up motion is ready.
Open linkCompare
Meshes vs. DIY
See what it takes to build behavior-based Intercom tagging and retry logic into your own app.
Open link