What Actions are

When you're done, you know what Actions can do for your Chirp and where to set them up.

Who can do this: the account owner on any plan, and workspace admins and editors. Only the owner and workspace admins add API keys.

An Action connects your Chirp to another app's API. With it, the Chirp can look things up while it answers (today's forecast, an order's status, stock levels) or do something for the visitor (add them to a list, book a slot). They work like the Actions in a Custom GPT, and the same schemas work.

How they work

• You describe the API. Paste its OpenAPI schema, or for Zapier, Make, n8n and Pabbly paste a webhook address, name it and list the fields it gets. See Add an Action from an OpenAPI schema and Add a webhook Action.
• The Chirp decides when to call it. Each operation the API offers becomes something the AI can use when a question needs it.
• Chirp Builder makes the call. Calls go from Chirp Builder's servers, never from the visitor's browser, and keys are added there: see Add the API key an Action needs.
• Changes ask first, unless you say otherwise. Reading data happens straight away. An operation that changes data shows the visitor what will be sent and waits for them to confirm. It runs without asking only when you switch Visitors confirm first off, or when a GPT schema marks it as harmless: see Choose operations, and when visitors confirm first.

The AI uses what the API sends back to answer. It's told the results are data, not instructions, and never to make up results.

Where to find them

In the Chirp's editor, section 7. Actions. A new Chirp needs saving first.

Actions are part of the Chirp's published version: visitors get a new or changed Action once someone who can publish clicks Publish changes (a draft Chirp gets them when it's first published). The preview in the editor uses your latest changes straight away. The public page shows the published version, also to you.

Actions, MCP and GPT Actions

• GPT Actions: the same idea, and the same OpenAPI 3.0 and 3.1 schemas. Keys don't come over from ChatGPT, so you add them here. How the key is sent is read from the schema when it says. Actions where each visitor signs in to their own account (OAuth) are coming soon. The editor's How Actions differ from GPT Actions list has the details: see What Actions can't do yet.
• MCP: connects your own AI app, like Claude or ChatGPT, to your Chirp Builder account so it can build and change Chirps for you, Actions included: see Add Actions through your AI app. A Chirp itself doesn't call MCP servers; it uses Actions.

Good to know

• The model must be able to use tools. If it can't, the section says "This AI model can't use tools, so the Chirp can't run its Actions." Under 5. Model, pick a model with the Web search badge: those can use tools.
• Some APIs charge for their use. Those charges come from the API's provider, separate from OpenRouter.
• Course tutors in the Academy never run Actions.