Pipedream Intercom steps in n8n

Intercom workflows in Pipedream are of two kinds: contact sync (upsert a lead when someone signs up, tag them) and conversation handling (a new conversation goes to Slack, an AI step drafts a reply). In n8n the first kind maps to the native Intercom node; the second needs HTTP Request.

The n8n side

Intercom node (n8n-nodes-base.intercom):

Resource	Operations
Company	Create, Get, Get All, Update, List Users
Lead	Create, Delete, Get, Get All, Update
User	Create, Delete, Get, Get All, Update

There are no conversation, note, tag or message operations, and no Intercom trigger node. Intercom's newer API merges users and leads into "contacts"; Pipedream's actions already use contacts, while the n8n node still uses the older user and lead endpoints.

What maps where

Pipedream (app intercom)	In n8n	Status
Upsert Contact	User or Lead → Create / Update, or HTTP Request → contacts	manual
Search Contacts	HTTP Request → POST /contacts/search	manual
Add Tag To Contact	HTTP Request → contact tags	manual
Reply To Conversation, Manage A Conversation	HTTP Request → conversations reply / parts	manual
Send Message To Contact, Create Note	HTTP Request → messages / notes	manual
List Conversations	HTTP Request → conversations	manual
New Conversations, New Reply From User, New Closed Conversation (polling)	Schedule Trigger + HTTP Request, or Intercom webhook → n8n Webhook	manual
New Leads, New Users (polling)	Schedule Trigger + Lead / User → Get All, or webhook	manual

The converter has no Intercom mapping yet. Each step arrives as a placeholder with its props, and code steps that call the Intercom API with this.intercom.$auth.oauth_access_token convert into Code nodes with the token as a variable.

Intercom credentials in n8n

API key only: in the Intercom Developer Hub create an app for your workspace, copy the Access Token, paste it as the API Key in n8n. Set permissions on the app (read/write conversations, contacts) to match the endpoints you call via HTTP Request; reuse the same credential there by choosing the Intercom predefined credential type.

Typical migration: new conversation to Slack

Pipedream: Intercom New Conversations (polling) → Slack Send Message to Channel. n8n, webhook option: in the Developer Hub subscribe the app to the conversation.user.created topic with the n8n Webhook URL → Webhook → Slack → Message → Send. Instant instead of polling, and no duplicates to deduplicate.

Intercom migration pitfalls

• No trigger node. Pick webhooks (instant, needs Developer Hub setup) or polling with a Schedule Trigger and the Remove Duplicates node so a conversation is not posted twice.
• Rate limits. 10,000 calls per minute per app and 25,000 per workspace, spread over 10-second windows; going over returns 429. Bulk contact backfills should batch.
• Legacy endpoints. The n8n node calls the old /users and /contacts endpoints and sends no Intercom-Version header. If your Intercom app defaults to API 2.0 or newer, User operations can fail; use HTTP Request on /contacts (role user or lead) instead.
• API version header. HTTP Request calls should send Intercom-Version; without it the app's default version applies, which may differ from what Pipedream used.

How to move your Intercom workflows

1. Export from Pipedream.
2. Upload on /convert; the free report lists every Intercom step and its props.
3. Get the n8n JSON: 1 workflow is free; full export: $3 per workflow, $19 minimum — coming soon.

Guide for HTTP-heavy steps: HTTP requests in n8n. Related: Zendesk, Freshdesk, HubSpot.