Skip to main content
POST
Disables AI responses for a conversation. Once disabled, the assistant will stop generating replies — any new messages in the conversation will be stored but not answered by the AI. This is useful for human takeover flows: configure a mid-call tool or automation that calls this endpoint when a customer requests to speak with a human agent.

Authentication

This endpoint requires your Automate API key as a Bearer token.

Path Parameters

string
required
The unique UUID identifier of the conversation

Response Fields

boolean
true when the operation was successful
boolean
Will always be false on success

Error Responses

boolean
false when an error occurs
string
Error message. Possible values:
  • Conversation not found — the UUID does not exist or belongs to a different account

Human Takeover Flow

A common pattern is to configure a mid-call tool that triggers this endpoint when the customer asks to speak with a human:
  1. Create a mid-call tool (e.g. transfer_to_human) with a webhook pointing to your ActivePieces or automation flow
  2. In your automation flow, call POST /automate/conversations/{uuid}/disable-ai using your API key
  3. Notify your support team (e.g. via Slack, email, or CRM) with the conversation UUID
  4. The AI stops responding — your agent takes over by sending messages directly
To re-enable AI later, use the Enable AI endpoint.