Skip to main content
Custom actions are special instructions that let your agent ask your own software to do something. You name the action, say when to use it, and give Botcadence the web address to call. Botcadence does not provide that outside service for you. Create them under Build → Actions (page title AI Actions). Enable each named action on a workflow Tools tab under Custom actions. You do not need an Integrations connection unless your own API uses credentials you store on the action. Use a custom action when you have a web address for a task such as looking up an order, saving a lead, or creating a booking, and a built-in tool does not cover it. If one outside service already offers many ready-made tools, use MCP instead.

​
Create an action

1

Open Actions

In the project sidebar, under Build, select Actions.
2

Create AI Action

Select Create AI Action. Name the action, describe when the agent should use it, and configure how it calls your API.
3

Save

Save the action. It appears in the Actions list. It does not run on live conversations until you enable it on a node and publish.

​
Enable on a workflow

1

Open Tools

Open the workflow, select an Agent, Supervisor, or Task, then open Tools.
2

Turn the action on

Under Custom actions, enable the action by the name you gave it.
3

Publish

Publish the workflow so channels and campaigns pick up the new tool.
In a test conversation, ask for something that should fire the action. Confirm your API receives the call.
Zapier, HubSpot, and custom webhooks stay on Integrations. Those are not Tools-tab rows. Custom actions are for APIs you describe yourself so the agent can invoke them.