Get an automation rule
A single automation rule by id. Administrator only — an agent token gets a 403.
Authorizations
The id_token from POST /auth/v1/signin, sent as Authorization: Bearer <id_token>. Not the access_token — that one does not carry the identity Cloud Chat authorizes on.
Headers
Your Cloud Chat instance ID — an integer, fixed for your company, told at onboarding. The API overview explains how instances work, how to find yours, and the errors a wrong or missing value produces.
1
Path Parameters
Your Cloud Chat account. It has to be an account your token grants membership on, and it has to live on the instance in the cloudchat-instance header — the two travel together. Account numbers are only unique within an instance, so the same number is a different company on another instance. Usually a mismatched pair fails closed with a 401, because your user does not exist on the other instance — but if your identity happens to exist on both, the call succeeds against the other company's data, silently. Read it and you are looking at the wrong help center; write it and you have stored into the wrong account. Send the two values that were given to you together, and never try a number to see what answers.
1
The id returned when the automation rule was listed.
9
Response
The automation rule.
An automation rule of the account — administrator only on every operation of this group.
9
"Auto-close stale conversations"
"Closes conversations idle for 7 days."
The event that triggers evaluation, e.g. conversation_created, conversation_updated.
"conversation_updated"
true
Execution order among the account's automation rules for the same event, ascending. This is what sort=execution_order (the default) orders by.
1
The rule's condition set, in the same shape the dashboard's automation editor writes.
The rule's action set, in the same shape the dashboard's automation editor writes.
"2026-05-02T11:04:17.000Z"
"2026-08-10T14:32:05.123Z"