How to Build Custom Intercom Integrations With No Native App (2026)

Intercom does support this natively through Custom Actions, but wiring one up means a developer defining request and response schemas, mapping data attributes, and maintaining it. That's the right tool for some teams. For everyone else, there's a lighter path.

If the tool you need has an API, you can connect it to Intercom yourself — without an App Store listing, and without hand-writing a Custom Action. This guide shows how, using AI-agent Custom Tools: you describe the action in plain English, and the same setup works across every help desk you run.

First, the framing. Macha isn't an Intercom replacement — it runs on top of the Intercom you already use. Fin and your Inbox keep working as they do; Macha adds an AI layer that can read conversations, reason, and — through Custom Tools — reach into any other system to answer or act.

What "custom integration" actually means now

Historically, "integrating X with Intercom" meant one of three things: find an App Store integration, build a Custom Action against Intercom's API, or pay a developer for a bespoke build. All three are real, and all three are heavy — an App Store app is someone else's idea of the integration; a Custom Action or bespoke build is a project with a schema to maintain.

A Custom Tool is a lighter path. Instead of building an app or hand-defining a schema, you describe an action — "look up an order," "create a Jira issue," "check a subscription in our billing system" — and point it at the relevant API endpoint. Your Macha AI agent then calls that action while it works a conversation, passes the right parameters, and reasons over what comes back — no code, and the exact same setup works if you also run Zendesk, Freshdesk, Front, or Gorgias.

The difference in practice is control and portability. A Custom Tool does exactly what you describe, scoped to the one job you need, and it isn't locked to a single vendor's action framework.

The model in three steps

Every Custom Tool follows the same shape, whether it's wrapping Salesforce, a Postgres database, or an internal microservice.

1. Point it at the API. You give Macha the endpoint, method, and credentials. If you'd rather not fill in a form, the built-in Sidekick will scaffold the whole thing from a plain-English description — "connect Stripe to look up payments," "hook up our internal orders API."

2. Define the action. Give the tool a label and a description the AI uses to decide when to call it, set the method and URL (with placeholders like {{order_id}} for the parameters the agent will fill), and choose whether it's a Read or a Write. Reads are safe lookups; Writes — refunds, status changes, record updates — require confirmation before they run. Authentication, static headers, and response mapping are all here too, so a real production endpoint drops straight in — without hand-authoring a request/response schema.

3. The agent uses it live. Once the tool exists, your agent calls it mid-conversation. A customer asks "where's my order?" in Intercom Messenger; the agent recognizes the intent, calls Get Order Status with the order ID it pulled from the chat, and answers with the real status and tracking — grounded in your system of record, not a guess.

That's the entire loop: define once, and the AI decides when to use it on every relevant conversation thereafter.

What it looks like once you've built a few

Custom Tools aren't a one-off escape hatch — teams build a small library of them, grouped by the service they wrap. Here's a Macha workspace with tools for Postmark (list templates, send email) and a store's order-lookup endpoint, each tagged Read or Write with its API URL.

Notice the mix of GET/Read and POST/Write. An agent can be allowed to look up anything but only act — send, refund, update — with a confirmation step. That boundary is enforced per tool and per agent.

Read vs Write, auth, and staying safe

Because a Custom Tool can reach into real systems, the guardrails matter as much as the capability:

• Read vs Write. Read tools are free to call. Write tools (anything that changes state) require confirmation, so an agent can't silently issue a refund or delete a record.
• Scoped by design. A tool exposes exactly one action against one endpoint. It does the job you defined and nothing else.
• Permissioned per agent. You decide which agents get which tools — your triage agent might only read; a senior-support agent might be allowed to write.
• Audited. Every call is logged, so you can see exactly what ran, with what inputs, and when.

For authentication, the builder supports the common patterns (API keys, bearer tokens, custom headers), so tools that need credentials — most of them — work without exposing secrets in the conversation.

When to use an App Store integration or Custom Action vs a Custom Tool

Custom Tools don't make Intercom's App Store or Custom Actions obsolete; they cover what's slow or missing.

• Reach for an App Store integration when a well-maintained one already exists and does what you need out of the box. If Macha has a native connector for it, use that (it's deeper and zero-setup).
• Reach for a native Custom Action when your team wants everything inside Intercom's own framework and has the developer time to define and maintain the schema.
• Reach for a Custom Tool when there's no app, you want it live in minutes without hand-writing a schema, the tool is internal or industry-specific, or you run more than one help desk and want the same action everywhere.

The honest rule of thumb: if you've ever said "I wish Fin could just check X for me," and X has an API, that's a Custom Tool.

Examples worth building

The pattern generalizes across every category of tool a support team touches:

• CRM — pull a customer's account, plan, and owner from Salesforce or HubSpot into the conversation.
• Databases & warehouses — query orders, subscriptions, or usage from Postgres, Snowflake, or BigQuery to answer from source of truth.
• Billing & payments — check a subscription or issue a refund in Chargebee, Recurly, or Stripe.
• Engineering — open a Jira, Linear, or GitHub issue from a bug report and read its status back.
• Internal systems — hit your own admin API to look up an account, reset a flag, or trigger a job.

For a browsable list of tools you can connect this way — 200+ across CRM, databases, e-commerce, ITSM, and more — see the Custom Tools integration directory. If it has an API, it belongs on that list.

Running more than one help desk? The same approach works on Zendesk, Freshdesk, Front, and Gorgias — Custom Tools are portable across all of them.

The bottom line

A missing App Store integration used to mean "not supported," and a Custom Action meant "get an engineer." With Custom Tools, it means "not yet — give me ten minutes." You describe the action, point it at the API, and your Intercom AI agents can read and write it live inside a conversation, with Read/Write guardrails, per-agent permissions, and a full audit trail — and the same tool works across every help desk you run.

Ready to try it? See how Custom Tools work, browse the integration directory, or start a free trial and wire up your first tool today.

Frequently asked questions

Do I need an engineer to build a Custom Tool for Intercom? No. You describe the integration in plain English and Macha's Sidekick scaffolds the request, authentication, and parameters — no request/response schema to hand-author. Technical teams can still go deeper with full control over methods, headers, bodies, and response mapping.

How is this different from Intercom's Custom Actions? Custom Actions are Intercom's native, developer-configured way to give Fin an API action inside Intercom. Custom Tools are a no-code alternative that works the same way across every help desk you run — so you're not rebuilding the integration per platform or maintaining schemas by hand.

Is this an Intercom App Store app? No. A Custom Tool doesn't need an App Store listing. It's an action your AI agent calls against any API, so you can connect tools that will never have a native integration, including internal and industry-specific systems.

Can it change data, or only read it? Both. Read tools are safe lookups; Write tools (refunds, updates, status changes) require a confirmation step before they run, and you control which agents can use them.

Is it secure? Yes. Custom Tools are scoped to a single action, permissioned per agent, and every call is audited — so you always know what ran, with what inputs, and when.