Intercom integration

What it does

The Intercom integration lets your agency run customer messaging operations on behalf of your clients without leaving TaskJuice. Connect a client's Intercom workspace once and you can create, fetch, update, and list contacts, start new conversations from a contact, reply to existing conversations as an admin or as the contact, upsert companies, and list the tags defined in the workspace. Three webhook triggers fire when a conversation is created, a contact replies to a conversation, or a new contact is created, so you can chain inbox activity into the rest of your workflow.

Connect an Intercom account

1. Open your workspace in TaskJuice and navigate to Connections.
2. Choose Intercom and click Connect.
3. Sign in to the Intercom workspace that should authorize the connection and approve the scopes configured on the TaskJuice OAuth app in the Intercom Developer Hub.
4. TaskJuice returns you to the workspace with the connection ready to use in any workflow.

Intercom access tokens are long-lived and do not expire on a fixed schedule. To revoke access, open Intercom, navigate to Settings, App settings, Authorized apps, and remove TaskJuice. See the Intercom OAuth setup guide for the full grant flow and scope configuration.

Triggers

• intercom/conversation-created fires when a new conversation is created in the workspace. The activation payload carries the Intercom notification envelope with the conversation under data.item.
• intercom/conversation-user-replied fires when a contact replies to an existing conversation. The activation payload includes the new conversation parts under data.item.conversation_parts.
• intercom/contact-created fires when a new contact is created. The activation payload carries the contact under data.item.

Intercom signs every webhook with an HMAC-SHA256 hex digest of the raw body on the X-Hub-Signature-256 header, formatted as sha256=<hex>. TaskJuice verifies the signature against the OAuth app's client secret before activating the workflow. Subscribe to the relevant topic on the Intercom Developer Hub for the app that issued the connection.

Actions

• intercom/create-contact creates a contact (user or lead) with optional external ID, email, phone, name, owner, and custom attributes.
• intercom/get-contact fetches a single contact by its Intercom ID.
• intercom/update-contact updates an existing contact. Send only the fields you want to change.
• intercom/list-contacts lists contacts with cursor pagination via per_page and starting_after.
• intercom/create-conversation starts a new conversation from a contact. The contact becomes the conversation's first sender.
• intercom/reply-conversation posts a reply, note, or quick reply to an existing conversation as an admin or as the contact.
• intercom/create-company upserts a company keyed on company_id, with optional plan, website, industry, size, monthly spend, and custom attributes.
• intercom/list-tags lists every tag defined in the connected workspace.

Known limitations

• Intercom enforces a per-app rate limit (1,000 requests per minute on most plans). When the budget is exhausted Intercom returns a 429 status, which TaskJuice surfaces as a retryable error so downstream resilience policies can back off.
• Every action sends the Intercom-Version: 2.11 header. If your Intercom app is pinned to a different version, contact support so the bundle can be republished against your target version.
• Pagination uses cursor-style starting_after tokens. Each list action returns one page per call along with the cursor for the next page, so workflows that need every page should drive paging explicitly.
• Webhook subscriptions are configured per topic on the Intercom Developer Hub against the OAuth app that issued the connection. TaskJuice does not create subscriptions automatically.
• Personal access tokens are not supported by this integration. Use the OAuth flow, which issues a workspace scoped access token tied to the authorizing admin.