Operator
← All integrations
Intercom logo+Supabase logo

Connect Intercom to Supabase

Automate Intercom and Supabase with AI

App behavior in Supabase explains tickets that look mysterious in Intercom alone. Your Operator agent on OpenClaw queries the tables you allow for user id or email, attaches recent events to the Intercom conversation, and can flag Supabase rows when a product bug pattern shows up across chats. Tell it why login failed for a user and it reads Supabase auth logs and drafts the Intercom explanation.

It reaches both apps directly or through connectors like Composio MCP and Pipedream MCP, which handle the sign in and token refresh, so there is no Zap to build and no API keys to paste.

What your agent can do with Intercom and Supabase

What your agent does in Intercom

  • Add subscription to a contact

    You can add a specific subscription to a contact. In Intercom, we have two different subscription types based on user consent - opt-out and opt-in: 1.Attaching a contact to an opt-out subscription type will opt that user out from receivi...

  • Add tag to contact

    Tool to add a tag to a contact in Intercom. Use when you need to attach or add a specific tag to a contact for categorization or tracking purposes.

  • Archive contact

    Tool to archive a single contact in Intercom. Use when you need to archive a contact by their ID.

  • Assign conversation

    Assigns a conversation to a specific admin or team in Intercom. Mutates live conversation state; confirm intent before bulk-assigning multiple conversations.

  • Attach contact to company

    Tool to attach a contact to a company in Intercom. Use when you need to associate a contact with a company.

  • Attach contact to conversation

    Tool to attach a contact participant to a conversation on behalf of admin or contact. Use when you need to add a new participant to an existing conversation.

All 133 Intercom actions →

What your agent does in Supabase

  • Create project api key

    Creates a 'publishable' or 'secret' API key for an existing Supabase project, optionally with a description; 'secret' keys can have customized JWT templates.

  • Delete an API key from the project

    Permanently deletes a specific API key (identified by `id`) from a Supabase project (identified by `ref`), revoking its access.

  • Delete third party auth config

    Removes a third-party authentication provider (e.g., Google, GitHub) from a Supabase project's configuration; this immediately prevents users from logging in via that method.

  • Get a third-party integration

    Retrieves the detailed configuration for a specific third-party authentication (TPA) provider, identified by `tpa_id`, within an existing Supabase project specified by `ref`.

  • List third-party auth integrations for project

    Lists all configured third-party authentication provider integrations for an existing Supabase project (using its `ref`), suitable for read-only auditing or verifying current authentication settings.

  • Update an API key for the project

    Updates an existing Supabase project API key's `description` and/or `secret_jwt_template` (which defines its `role`); does not regenerate the key string.

All 116 Supabase actions →

How it works

Tell the agent what you want to happen between Intercom and Supabase, for example to watch one and act in the other, or to keep the two in step. It reads what it needs from Intercom, works out what to do, and runs the matching action in Supabase without you mapping a single field.

You can have it run once, on a schedule, or whenever something changes. Ask it for a status any time and it reads the latest from both apps back to you in the same chat.

Common questions about Intercom and Supabase

How do I connect Intercom and Supabase to Operator?
You authorize Intercom and Supabase once each from your Operator dashboard. Operator holds both connections and refreshes the access tokens for you, so your agent keeps working across them without you signing in again.
What can my agent do across Intercom and Supabase?
Tell it the job and it moves between Intercom and Supabase as one task, choosing which actions to run on each side. There is nothing to map and no trigger to configure; you give instructions the way you would to a person.
Can my agent keep Intercom and Supabase in sync?
Yes. It can watch Intercom and act in Supabase, or keep both in step, reading from one and running the matching update in the other. This runs on demand when you ask or on a schedule you set.
Do I need to build a workflow or write code?
No. There is no workflow to build, no fields to map, and no API keys to paste. Operator manages both connections, and you give the agent instructions in plain language.

Intercom and Supabase integrations

Put your agent on Intercom and Supabase

Sign in, connect both apps, and hand your agent the work. The same setup reaches every app in the catalog. Your first week is free.

Try for free