Intercom

Intercom is a connector: it links a MeDo app to one Intercom workspace so the app can search conversations and contacts, open a full thread, look up companies, work with tickets and published help-center articles, and send a confirmed reply or ticket. It does not delete contacts, run Fin or calls, or give each visitor their own Intercom login.

#What you can build

• A private support inbox. List open conversations and open the full thread when you pick one.
• A ticket intake. Find or create a contact by email, then create a ticket after you confirm the type and description.
• A contact lookup. Search by email and show the contact plus recent conversations.
• A reply workspace. Show a conversation and send your confirmed reply as a selected admin.

Intercom fits when the app should work with real support conversations, contacts, and tickets the owner already keeps in Intercom. It is not a full Intercom admin console, see Limits.

#Build examples

Copy one of these into the prompt box. The first one is the smallest useful starting point.

Use @Intercom to build a private inbox that lists my open conversations and shows the full thread when I pick one.

Use @Intercom to build a private ticket intake that finds or creates a contact by email, then creates a ticket after I confirm the type and description.

Use @Intercom to build a private contact lookup where I search by email and see the contact plus recent conversations.

Use @Intercom to build a private reply workspace that shows a conversation and sends my confirmed reply as a selected admin.

The wording matters: name the customer, email, or ticket you mean. "Show open conversations for billing" produces a different app from "a page that lists every contact".

#Prepare and connect

You need an Intercom workspace that can already see the conversations, contacts, and tickets the app should use. No API key is involved.

1. Open Skills & Connectors in the sidebar and search for Intercom.
2. Open the Intercom card and click Connect.
3. Sign in to Intercom and approve the access MeDo asks for.
4. The button changes to Connected. That is the success state; you do not need to copy anything back into the app.

If you start building before connecting, MeDo notices and shows an Intercom connection button under its reply. You can connect there instead. If no button appears, use the connector card described above.

#Use it in your app

• The app uses the owner's connected Intercom workspace, not each visitor's Intercom login. Everyone who opens the inbox sees the same conversations. Keep lookups and writes behind your app's own sign-in, and restrict them to the people who should have that access. A page titled "private" is not access control on its own.
• Start from a search or a known ID. Copy conversation, contact, and ticket IDs from results. Empty lists mean there is no matching record in this workspace.
• Replies actually send. A confirmed reply or ticket update goes to the customer as the selected admin. Confirm the name, message text, and ticket type before writing.
• Help-center search covers published articles. Drafts may not appear.
• Reads refresh on demand. There is no live sync with Intercom. Add a refresh control rather than expecting new messages to appear by themselves.
• App-owned data stays in the app. Labels, review status, and notes that are not Intercom fields belong in your app's own tables, keyed to the real conversation or ticket ID.

#Limits and troubleshooting

"Connection required" appears in the app. Ask the app owner to open the connector card and click Connect, then reload.

Conversation list is empty or refused. Check Intercom Inbox directly. If Inbox is off, use contacts or tickets instead.

A reply was refused. Sending a reply or creating a ticket needs an explicit confirmation in the app. Check that the confirm step ran before trying again.

Visitors can see conversations when they should not. The connection is shared. Add sign-in and server-side restrictions to the app; see Managing access & roles.

#Related

• Connector catalog — the other connectors and what they are for.
• HubSpot — CRM contacts, companies, and deals, not support tickets.
• Skills & Connectors — how Skills are called, priced, and limited.
• Managing access & roles — restrict who can read and change connected data.