Actions are the tools your agent invokes when a conversation matches their description: an API lookup, a form, a widget, or an escalation. You do not build actions by hand. All actions are created from Skills: when you save a skill that contains a webhook step, Chatropic creates the linked HTTP action and lists it under Actions > Available actions.

The Available actions list under Actions.

​
What is an action?

An action defines:

​
Where actions come from

1

Create a skill

Describe the feature under Agent settings > Skills > New skill, including the API call if one is needed. See the Skills guide.
2

Save the skill

Each webhook step in the skill creates (or updates) a linked HTTP action automatically.
3

Review in Available actions

Open Actions > Available actions to see the linked action, test it with sample parameters, and enable or disable it.
Edit an action’s URL, headers, and body from its skill’s webhook step rather than from the action page, so the skill and its linked action stay in sync.

​
How the agent fills parameters at runtime

  1. The planner selects an action when the user’s message matches the action Description.
  2. It fills the parameters from the message and prior turns, using the property names from the parameter schema.
  3. Chatropic substitutes {{parameter}} placeholders in the URL and body before calling your API.
  4. If a required parameter is missing, the agent asks a follow-up question instead of calling the API with an empty value.
This is why the description matters so much: write it like an instruction to a colleague, for example “Search the catalog by keyword when the user asks about items, prices, or availability.”

​
Go deeper

Skills

Create the playbooks that generate actions.

Manage tokens

Static and customer-login credentials for API auth.

Action chaining

Multi-step workflows with on_success.

Response mapping

Shape API JSON for chat widgets.

Escalate to human

Hand off to a live agent queue.

Suggested prompts

Quick-reply chips and starter prompts.
Do not put secrets in action URLs or headers. Use Manage tokens and reference them with @ in header fields.