Conversations
Disable AI
Disable AI replies for a specific conversation, allowing a human agent to take over
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 successfulboolean
Will always be
false on successError Responses
boolean
false when an error occursstring
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:- Create a mid-call tool (e.g.
transfer_to_human) with a webhook pointing to your ActivePieces or automation flow - In your automation flow, call
POST /automate/conversations/{uuid}/disable-aiusing your API key - Notify your support team (e.g. via Slack, email, or CRM) with the conversation UUID
- The AI stops responding — your agent takes over by sending messages directly

