Get contact
Retrieve a contact by its Intercom ID.
Connector library
Intercom connector.
Create and retrieve Intercom contacts, retrieve conversations, add internal conversation notes and send administrator replies using API 2.16.
Connector download
Download Intercom
Versioned ZIP for your CXFabric tenant.
Use this connector in a flow
- Register the ZIP in your tenant, or add a new version if the connector is already installed.
- Create or select a credential if the action requires one.
- In a Draft flow, add an available action, choose its version, connect it, and map inputs.
- Test the step and flow; review output and failures before activation.
See readme.md in the ZIP for settings and limitations.
- Version
v0.2.0.1 Choose version
- Release
- 2026-10-03
- Package
- Implemented source
- Schema credentials
- Bearer token
- Connection settings
- API Base URL
- Package size
- 9 KB
- SHA-256
167c4e21a3bc03cfc7edbc6c447ac5d2e4fc3abfce22fdf12db86f9577281aa4
Version history
What's new
- v0.2.0.1Latest · 2026-10-03 · Implemented source
Improves action labels, mapping hints and connection groups while retaining the existing parameter keys, types, defaults, credentials and result contracts.
- v0.2.0.0Earlier · 2026-10-03 · Implemented source
Create and retrieve Intercom contacts, retrieve conversations, add internal conversation notes and send administrator replies using API 2.16.
- v0.1.1.0Earlier · 2026-10-02 · Starter scaffold
Historical generic scaffold archive, retained unchanged for existing version references.
Included in this version
Included actions
Implemented in v0.2.0.1. Use a separate flow trigger; no webhook trigger is included.
Create contact
Create a contact with an email address and optional display name.
Get conversation
Retrieve a conversation with plaintext messages; the vendor returns at most 500 recent parts.
Add conversation note
Append an internal note authored by an authorized administrator.
Reply to conversation
Send an administrator comment; customer notifications depend on channel settings.
Vendor API
API and access
Implementation considerations
- Support APIs often distinguish agent/admin operations from end-user request operations; confirm the right permission model.
- Keep requester identity, organization, assignee, status, and external IDs mapped explicitly.
- Use ticket events for updates, but protect against loops when CXFabric writes back to the same system.
Related connectors
More in CX & Support APIs
Support
Need help with Intercom?
Tell us what you need to connect or change.