Skip to content

Explore CallMissed

Tools & automationsA conversation with a next step.

A useful agent needs access to the work, not just an answer box. Choose the tools an agent can use, connect supported apps, and send events to your own systems.

A paper-craft toolbox holding interlocking cut-paper gears

Simulated example

  1. Pick one action

    Find the next available appointment.

  2. Connect the tool

    Calendar tool / Scoped read access, attached to one agent.

  3. Watch it work

    The agent returns the available times for the person to choose.

In the console

An order lookup, built as a tool

Describe your order API as a tool the agent can call, test it against the real endpoint, then connect the apps you already use from the catalogue.

Demo: building and testing an order-lookup API tool, then connecting apps from the integrations catalog

Inside Tools & automations

Connect agents to your business tools, calendars, custom APIs and MCP servers.

  • Custom tools
  • MCP servers
  • Calendar
  • Knowledge and memory
  • Webhooks
  • Console assistant

Custom API tools

Define REST tools for your own business workflows and attach them to the appropriate agent. Use explicit input contracts and scoped access.

Connected apps and MCP

Connect supported integrations or remote MCP servers, inspect available tools, check connections and remove access when it is no longer needed.

Calendar, knowledge and memory

Make connected calendar actions and relevant knowledge tools available to supported agents. Tool availability depends on the agent channel and configuration.

Events beyond the conversation

Subscribe your application to supported webhook events, inspect delivery history and replay eligible deliveries. Use the console assistant for supported workspace actions.

A paper-cut pegboard of tools linked by red string to a central tile

See what a tool adds

Toggle the connected tools in this simulated graph and read what the agent can do with each one.

Your agent

Its configured instructions and channel

Simulated example — available actions vary by channel and connected permissions.

With this setup the agent can

  • Calendar actions: Read availability and schedule inside the limits you set.

Some actions reach real people or change records — review permissions before expanding access.

Simulated example.

Three steps to a working setup

  1. 1

    Start with one business action and the agent that should perform it.

  2. 2

    Connect the supported app, define a custom tool or configure an MCP server.

  3. 3

    Test the action with controlled inputs and review activity before expanding access.

Read this before you start

This is agent tool access and event integration, not a promise of a universal no-code workflow builder. Available actions vary by channel and connected permissions. Some actions reach real people or change records; review permissions carefully.

Create an account, then open Tools & automations in the console.