Choose an available topic from the sidebar. More documentation is coming soon.

Tools & Actions

AI Chatbot Tools and Actions

Give the agent actions it can run: search data, capture leads, book meetings, take payments, and move visitors to the right page.

The AI chatbot tools and actions reference explains every action you can attach to an agent. Tools extend what the chatbot can do beyond answering from trained content: search a database, look up a booking, capture a lead, send a transcript, open a payment flow, or navigate a visitor to another page. Each guide covers configuration, required credentials, and how to test the action before it goes live.

How Tools and Actions Work

Set up tools from the Tools and Actions overview. An action is a call the agent can make when a conversation needs live data or a side effect. You define when it can run, which fields it collects, and what it returns to the conversation. Start with one action, test it with a real question, then add the next.

  • Name and describe the action so the model knows when to use it.
  • Map the required inputs and the response it returns.
  • Test with a question that should trigger the action – and one that should not.

Data and Search

Use these actions when the answer lives outside the trained content.

Leads and Conversations

Scheduling

Let the agent check availability and book a meeting without leaving the conversation.

Payments and Commerce

  • Polar – create checkout and subscription actions with a Polar token.
  • Paddle – handle Paddle Classic subscription actions.
  • Shopify – look up orders and products from the conversation.

Agent Features

  • MCP server – connect the agent to a Model Context Protocol client over SSE.
  • Navigate to page – move the visitor to a page or section, optionally filtered by data.

Testing an Action

Open the action, confirm the credentials or connection, then ask a question that should trigger it. A passing test returns the expected value in the conversation and leaves a clear trace you can inspect. If the action does not fire, check the description, the required inputs, and whether the model can see the fields it needs. Disable an action before changing its schema, and re-test after every edit.

Related Documentation

On this page