Skip to content

Turn on capabilities

The Capabilities page is the roster of everything your agent can do beyond talking: one card per capability, each with its status and a link to its configuration. Status is Ready, Needs attention, or Off.

This document covers the console mechanics: connections, secrets, custom integrations, and readiness. For what each capability does, see Capabilities.

Each capability configures on its own page under Capabilities: Scheduling, with a Representatives tab, People fields, and Custom integrations. Two of them have guides of their own, Schedule calls and Manage people. Starting conversations is set up under Outreach rather than here.

Accounts the agent acts through, such as Google Calendar or Slack, are connected once for the whole workspace at Workspace · Connections.

Connect an account

Capabilities that act through an external account, such as Google Calendar for scheduling or Slack for notifications, need a connection. Workspace · Connections lists each connected account with its state.

State What it means
Connected Working.
Expired The provider's token lapsed. Reconnect when you get a chance; the agent recovers on its own in most cases.
Revoked or Error The connection is broken and stays broken until you reconnect. The page shows the provider's last error.
Not connected Never connected.

Connect starts the provider's sign-in flow, and the resulting access belongs to the whole workspace. Each account lists the agents that use it. Disconnect revokes access at the provider and deletes the stored credential. When agents use the account, the confirmation names them: they keep booking calls, but their bookings stop reaching the calendar, and their Scheduling card shows Needs attention until you connect an account and choose it in their Scheduling settings.

For notification-style items you also choose the destination service: where Notify Operator lands, or which calendar meetings are written to. The agent's behavior never changes with the service, so you can swap it later without touching a Playbook.

Secrets are write-only

API keys, webhook URLs, and auth headers are stored encrypted and never shown back. The console displays a saved secret as set, with a Replace action. Secrets never appear in an exported document.

Define a custom integration

A custom integration is an ability backed by your own HTTP endpoint. Define it on Capabilities · Custom integrations.

  1. Name and description. The description teaches the agent when to use the ability, so write it the way you would brief a new teammate: "Looks up an order by ID. Use when a customer asks about order status, shipping, or returns."
  2. Inputs. What the agent should gather from the conversation, as a small schema such as orderId: string.
  3. Endpoint. Method, URL, and an optional write-only authentication header.

When the agent decides the ability applies, Anychat calls your endpoint with the inputs, hands the response back, and the agent continues the turn with the result.

An integration with no endpoint is never offered to the agent.

Read readiness

A capability with incomplete configuration is not offered to the agent, so it fails visibly in setup rather than silently in a conversation. Two surfaces say what is missing.

The Capabilities page shows a status per card, such as "no representatives: calls book with 'someone from our team'".

The readiness card on the agent's Overview flags breaks across the whole agent: a Playbook that needs a capability which is not configured, or a missing Default Playbook. Each finding links to the page that fixes it. A clean agent shows no card.

What's next