Agent actions
Create an action
Create a built-in action an agent can take: calendar, transfer, SMS, email, WhatsApp or Slack.
POST
This endpoint is for the VIP plan only. Other plans get a
403. See Plan access.201 with the new action.
Path Parameters
Body
Every action hasname (required when you create one), condition (when the agent should use it) and isActive. The fields for each kind are below. The API checks the same rules as the dashboard’s server.
Calendar
cal_com, calendly, leadconnector or google. The provider must be connected in the dashboard.A calendar or event type id from List calendars.
Transfer
Transfer actions work on voice agents only, the same as in the dashboard. A chat or widget agent gets a400.
warm (the agent introduces the caller first) or cold (it hands the call straight over).SMS
contact sends to the person in the conversation, specific sends to recipientValue, and ask lets the agent ask. Leave it out for contact.The connected WhatsApp number to send from. It must be in the agent’s workspace. Required unless you send
phoneNumberId.The older way to pick the sender: a phone number in the agent’s workspace whose WhatsApp number sends the message. Send
whatsappSenderId instead.The message, up to 1,600 characters. It can use
{{variables}} from parameters. Required when messageMode is fixed.whatsappSenderId.
Slack
id, kind, agentId, its fields, createdAt and updatedAt.