Skip to main content

Enabling Candu Actions for Fin (Intercom AI Agent)

How to expose read-only Candu Actions to Fin so it can answer live questions (subscription, SDK status, content, segments) instead of guessing , plus how to verify Fin actually called the action.

Written by Jonathan Anderson

Enabling Candu Actions for Fin (Intercom AI Agent)

Candu's Actions aren't just for your own embedded wizards — any read-only action can be exposed directly to Fin, Intercom's AI Agent, so it can answer real customer questions with live data (current subscription plan, SDK install status, segment membership, content status, and more) instead of guessing from its knowledge base.

How it works

Fin access is set per action, not with a single workspace-wide switch. Each action has its own toggle, so you choose exactly which of your read (and, more carefully, write) actions Fin is allowed to call.

Before you start: connect Intercom to Candu

This is a one-time, workspace-level setup. If Intercom is already connected for your workspace, skip ahead to Step 1.

  1. Go to Settings > Integrations, then click the Integrations tab — it sits next to Webhooks and is easy to miss.

  2. Find the Intercom card ("Connect Intercom to provision data connectors for Actions") and click Manage.

On the Intercom connection page you'll see three sections:

  • Connection — shows which Intercom account/workspace is connected, plus an auto-synced MCP authentication token (sent as the Authorization: Bearer header on every Fin request to Candu's MCP gateway). You don't need to touch this unless you're manually configuring a stored authentication token on the Intercom side. Test Auth confirms the connection is healthy; Disconnect removes it.

  • Fin settings — a Sync all to Intercom button that bulk-pushes every action's current Fin settings in one go (plus a "Last synced" timestamp). Use this if things look out of sync instead of opening every action individually.

  • Data Connectors — a Fetch Data Connectors button that pulls the list of connectors already registered in the connected Intercom workspace, so you can see from Candu's side what's actually live in Intercom.

Once this is connected, the per-action Fin toggle below actually has somewhere to sync to. If it isn't connected yet, none of the per-action toggles in Step 2 will do anything.

Step 1: Find the action

  1. Go to Actions > All Actions in your Candu workspace.

  2. Search for the action you want to expose and click into it.

📸 The Actions list (Actions > All Actions), showing the search box and the Enable/Type/AI policy columns.

Step 2: Turn on "Available on Fin"

  1. On the action's detail page, click the Fin tab (next to Overview and Logs).

  2. Toggle "Available on Fin" to On. This is separate from the action's main Enable switch — an action can be fully enabled everywhere else and still be Off for Fin by default.

  3. Under "Make available via", leave it on Direct (Fin can call it any time it's relevant) unless you specifically want it restricted to Procedure only (only callable when a Fin procedure explicitly references it).

  4. Leave the Audience checklist (users / leads / visitors) on its default unless you need to restrict who Fin will use this action for.

📸 An action's Fin tab with "Available on Fin" switched On, showing the Direct radio and Audience checklist.

When you toggle it, you'll briefly see "Pending changes to push" → "Intercom definition synced". That confirms the change synced through to Intercom's own Data Connector Builder (Settings > Integrations > Data connectors) — Candu Actions are registered there as Intercom data connectors under the hood.

Only expose read-only actions (to start)

Stick to actions of Type: Read for a first pass. Write actions (anything that creates, updates, deletes, publishes, clones, archives, toggles, or bulk-modifies something) need a separate, deliberate decision, Fin calling those unsupervised is a different risk profile than Fin looking something up. If an action shows AI policy "Needs Review", don't switch it to "Automatic" just to unblock the Fin toggle, that flag is usually there for a reason. Check why an action is flagged before changing its policy.

Step 3: Test it in a live conversation

  1. Open the Messenger on a page where it's embedded (or use Fin preview from the Data Connector Builder in Intercom).

  2. Ask a question that should require the action you just enabled — e.g. "Is the SDK installed on my site right now?" or "What's my current subscription plan?"

  3. Fin should answer with a specific, real value (a timestamp, a plan name, a count) rather than a generic knowledge-base-style answer.

a live Fin conversation asking about SDK status/subscription, with Fin's answer showing a real timestamp and plan value.

Step 4: Verify Fin actually called the action

A specific-sounding answer isn't proof by itself, confirm it properly:

  1. In Intercom, go to Inbox > Fin for Service > All conversations (this view is scoped to conversations where Fin was involved) and open your test conversation.

  2. Under Fin's answer bubble, look for a "Private sources" section. If the action was actually called, it's listed there as [Candu Action] your_action_name.

Summary checklist

  • Intercom is connected (Settings > Integrations > Integrations > Intercom > Manage)

  • Action is Read type (write actions need a separate decision)

  • "Available on Fin" is On, on the action's Fin tab

  • "Make available via" is Direct (or Procedure only, if intentional)

  • Tested with a real Fin conversation and got a specific, live-data answer

  • Confirmed the call in the conversation's Private sources list, not in Candu's Logs tab

Related Articles
Did this answer your question?