Skip to content
PUThttps://app.evoriqa.com/api/v1/chatbots/{chatbotId}/actions

Configure an agent action

Creates or updates the chatbot configuration for one action type. An unknown `type` is a **404**. Only `book_appointment` has a validated `config`, discriminated on `config.provider` — every other action type stores its `config` unvalidated. Within a booking provider each setting is OPTIONAL: a partial config saves cleanly, so an action can be configured before its credential exists. What is validated is the SHAPE of whatever you do send (422 with per-field errors). A config whose `provider` is absent or unrecognised skips validation entirely and is treated as the loose `webhook` default. When `enabled: true` on an API-mode provider (`cal_com`, `calendly`) and a credential is stored, the event type is additionally checked against the live provider: a definitive rejection — token refused, event type not found — is a **422**; an inconclusive check (provider unreachable, or a stored credential that will not decrypt) still saves and returns a `warning` string. The embed providers carry no credential, so no live check runs for them. Connected-mode bookings pass through this same schema, with `connected`, `credentialName`, `eventTypeUri`/`eventTypeId` and `showChip` riding along.

Requires scope chatbots:write

Warning:

Access is gated — enable it before your first call

The API is off by default. A request succeeds only when all three switches are on: the platform master switch (off by default), your organisation’s API toggle, and your plan or client entitlement. Any one off returns 403 API access is not enabled for this workspace.

Parameters

Request body

Content type: application/json

Request

Response

200 OK