Skip to main content
Integrations · Intercom
A Guild agent reads, creates, updates, and deletes records across Intercom on behalf of your team. Guild stores the Intercom API key server-side and injects it at request time, so agent code never sees it. Credential policies let you restrict which operations each agent may call, and activity logs capture every action for audit.

Book a demo

See how teams govern agents that use Intercom.

Talk to sales

Get access to Guild, then connect Intercom to your first agent.

What the Intercom integration exposes

The integration provides tools that cover contacts, companies, conversations, tickets, Help Center collections and articles, content snippets, tags, data exports, and more. Tools support both individual and bulk operations, including bulk contact creation, update, and deletion, as well as conversation-to-ticket conversion. Tools for Fin voice calls, office hours schedules, custom object instances, and workspace activity logs are also included. All tools use the intercom_openapi_ prefix and are selectable with pick() so an agent loads only what it needs.

How it works

1

Open Credentials in Guild

Go to Access & setup > Credentials in your Guild account or organization. This page lists connected credentials and shows a gallery of available integrations.
2

Connect the Intercom integration

Click Connect, select intercom-openapi, and paste your Intercom API key into the API Key field. Guild sends the key as a bearer token in the Authorization header on every request.
3

Import tools into your agent

Import IntercomOpenapiTools from the guildai~intercom-openapi package and spread it into your agent’s tools object. Use pick() to include only the specific tools your agent requires.

Why Intercom access needs governing

Intercom holds customer contact records, support conversations, and ticket data. An agent with unrestricted access could delete contacts, purge tickets, or export bulk data without review. Guild credential policies let you write ALLOW and DENY rules that the credential proxy enforces before any request leaves Guild. You can restrict an agent to read-only operations using a methods: GET resource constraint, block destructive operations such as delete_contact or delete_ticket by name or wildcard pattern, and scope rules to a specific agent or workspace so one agent’s permissions do not bleed into another’s. Guild stores the Intercom API key server-side and injects it only after the policy check passes. Agent code, prompts, and containers never receive the key. You can scope a credential to a single workspace, a single member, or a single agent, and the workspace settings page lets you restrict a workspace to its own credentials so shared account credentials cannot be used there. The audit trail in Guild’s activity log records each call, giving you a durable record without any extra instrumentation.

About the Intercom integration

Agents can create, update, and delete contacts, companies, conversations, and tickets in Intercom. They can manage Help Center articles, collections, and content snippets, as well as apply tags and handle data exports. The integration also supports bulk contact operations and conversation-to-ticket conversion. The integration is guildai~intercom-openapi.

Authentication

  • Type: API key
  • Header: Guild sends the key as a bearer token in the Authorization header

Setup

1

Connect Intercom

In Guild, go to Access & setup > Credentials, click Connect, select intercom-openapi, and paste the key into API Key.
See Credentials for workspace, member, and agent-scoped credentials.

Usage

Selecting specific tools

Tools are named with the intercom_openapi_ prefix. Use pick() to include only what your agent needs.

Tools

Tools in the latest published version of guildai~intercom-openapi:

Frequently asked questions

Yes. A credential policy rule with methods: GET in the resources block restricts the agent to GET requests only, blocking creates, updates, and deletes regardless of which tools the agent calls. See the credential policies docs for the full rule syntax.
No. The catalog entry for guildai~intercom-openapi lists no webhook events, so the integration does not receive inbound events from Intercom.
Yes. Connect a workspace-scoped credential in each workspace and point each one at a different Intercom account. Guild resolves credentials in order: a workspace credential takes precedence over the account default, so each workspace uses the account you intend.
Connect a dedicated credential scoped to that agent, or add a DENY rule in the credential policy scoped to that agent’s ID. A dedicated credential serves only the one agent it is attached to and never serves other agents in the workspace.

Put a governed agent on Intercom this week

Book a demo

See how teams govern agents that use Intercom.

Talk to sales

Get access to Guild, then connect Intercom to your first agent.
Also runs on Guild: Front · Pylon · Zendesk Read: Docs: Credential policies · Credentials · Tools in agents
Last modified on November 10, 2026