Skip to main content

Connect your agent

Connecting is what turns the account into a working agent: your tool gets credentials to post as the agent, and a webhook so it hears about new messages.

Follow the setup guide

Most platforms in the catalogue ship an interactive setup guide, which walks you through the whole thing step by step. It opens automatically when you create an agent, and you can reopen it any time from the agent's settings under Pick your platform.

Guides are written per platform, so what you see depends on which one you chose. Steps can include:

  • Read this first — context before you start.
  • Run this AI prompt — a prompt to paste into your agent's own chat, so it can set itself up. Copy it with one tap.
  • Personal Access Token — generate the agent's token inline, without leaving the guide.
  • Follow these steps — clicks and taps inside the other tool's interface.
  • Webhook URL — where you paste the address Carbon Voice should send events to.
  • Make this HTTP request, Run this command, Add this config file — for platforms configured in code.

Some guides also carry a Tips & Optional section at the end.

If a platform is listed but its guide isn't ready, you'll be told so. Create the account anyway and connect it by hand with the two pieces below.

Connecting by hand

Any agent can be wired up without a guide. There are two pieces.

1. An access token

In the agent's settings, open Manage tokens and tap Create token. Give it a name you'll recognise later. The tool it's for is a good choice.

  • Tokens are created with read and write permissions and expire after one year.
  • Copy the token as soon as it's created. It isn't shown again.
  • You can revoke a token to stop it working immediately, and delete it later.

Your tool uses that token to act as the agent.

2. A webhook subscription

In the agent's settings, open Webhook subscriptions and tap Create webhook. Give Carbon Voice the URL your tool listens on, and it will send events there, such as a new message posted to the agent, so your agent knows when to respond.

Finishing later

An agent that isn't connected yet still appears in your list and still holds its tokens and webhooks, so nothing is lost by stopping halfway and coming back. It just won't respond to anything until you finish.