> ## Documentation Index
> Fetch the complete documentation index at: https://docs.cloudhumans.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Confirm an automation rule

> Second half of creating a rule. Send back only the `proposal_token` from `proposeAutomationRuleCreate`; the rule saved is exactly the one that was previewed, created off and placed after the last rule of its event at the moment of the confirm. The token is consumed by this call. If any rule of the same event was created, changed or removed after the proposal, nothing is written and the call answers 409 `stale_proposal`: propose again, so the preview and its warnings reflect the rules as they are now. **Administrator only — an agent token gets a 403.**

> [!NOTE]
>
> Second step of the propose → confirm flow for a new rule. The rule is created off. See
> [Propose an automation rule](https://docs.cloudhumans.com/api-reference/cloudchat/endpoints/propose-an-automation-rule.md)
> for the full walkthrough, the list of warnings, and who turns rules on.


## OpenAPI

````yaml api-reference/specs/cloudchat/v1.json POST /v1/accounts/{accountId}/automation-rules/confirm-create
openapi: 3.0.1
info:
  title: Cloud Chat API
  version: v1
  description: >-
    The curated public surface of Cloud Chat. Every call needs two things: the
    Bearer token from `POST /auth/v1/signin`, and the `cloudchat-instance`
    header that says which Cloud Chat instance your company lives on.


    If you don't know your instance value, the [Find your
    credentials](/api-reference/cloudchat/credentials) page reads it out of your
    own token in the browser.
servers:
  - url: https://api.cloudhumans.com/cloudchat
    description: Production
security:
  - bearerAuth: []
tags:
  - name: Canned Responses
    description: >-
      Canned responses — the shortcuts agents expand while replying. Each one
      belongs to a single account and is identified by its short code.
  - name: Conversations
    description: >-
      The conversations of an account: read them, change their priority and
      status, assign them, leave internal notes, and block or unblock the
      contact of a conversation. Answering the customer, opening a conversation
      and deleting one are not part of this surface. What you can see and change
      follows the same rule as the dashboard: an administrator token reaches
      every inbox, an agent token only the inboxes it is a member of.
  - name: Contacts
    description: >-
      Customer contacts of the account, with their personal data. Administrators
      only.
  - name: Help Center
    description: >-
      Portals, categories and articles of the help center — the public FAQ your
      customers read.
  - name: Uploads
    description: Store the images help center articles embed.
  - name: Labels
    description: >-
      The label definitions of an account: the tags conversations and contacts
      carry. Listing and reading are open to any member; creating and updating a
      label need an administrator or CX engineer token. Renaming a label retags
      the records that carry it. There is no delete: removing a label and
      creating another with the same title would bring the old tags back. The
      same group applies labels to a conversation or a contact and takes them
      off again.
  - name: Inboxes
    description: >-
      The inboxes a token can see — every inbox of the account for an
      administrator, only its memberships for an agent. Administrators can also
      change an inbox's name, greeting, working hours and CSAT toggle. Never
      includes the channel's credentials, and the channel itself is not editable
      here.
  - name: Agents
    description: >-
      Read-only access to the human and AI agents of an account. A hidden admin
      (the platform's own support user) never appears, on the list or by id.
  - name: Teams
    description: >-
      Teams group agents for assignment. Listing and reading are open to any
      member; creating and updating a team, and managing its membership, require
      an administrator token. A system-managed team (provisioned by the
      platform) can be read like any other but never updated.
  - name: Macros
    description: >-
      Macros bundle a sequence of actions an agent runs against a conversation
      from the dashboard. This surface lets you list, read and write macro
      definitions — running one is not part of the v1 contract. A macro is
      either `global` (visible to the whole account) or `personal` (visible only
      to its author); an agent token can only create personal macros.
  - name: Automation Rules
    description: >-
      The account's automation rules — administrator only. An agent token gets a
      403 on every operation in this group.


      Reading is direct. Writing goes through a propose → confirm pair: the
      propose call validates the change, writes nothing, and returns a
      single-use `proposal_token` with a preview and a list of `warnings`; the
      confirm call sends the token back and applies exactly what was previewed.
      Rules created through the API start off, and turning a rule on or off
      stays with a person in the Cloud Chat automations screen.
  - name: Availability Reasons
    description: >-
      The reasons an agent can go `busy` for, configured per account. Listing is
      open to any member; creating, updating and deleting require an
      administrator token. Deleting is a soft delete — the reason disappears
      from listings but agents' past availability history keeps referencing it.
  - name: Native Attribute Requirements
    description: >-
      Which native conversation attributes (priority, assignee, tag, team) the
      account requires agents to fill before resolving a conversation. Listing
      is open to any member; requiring and un-requiring need an administrator
      token. Deleting a requirement is reversible — require the same key again
      to restore it.
  - name: Custom Attributes
    description: >-
      The custom fields an account added to conversations, contacts and
      companies, and their definitions: key, type, model and options. Listing
      and reading are open to any member; creating and editing need an
      administrator token. Deleting a definition, conditional sub-lists and the
      AI fill settings stay in the Cloud Chat screen.
  - name: Campaigns
    description: Check who a campaign would reach, send it, and read the result back.
  - name: Reports
    description: The numbers of the Cloud Chat reporting dashboards, read through the API.
  - name: Companies
    description: >-
      Companies (the businesses your contacts work for) and the links between
      contacts and companies. Companies must be enabled for the account; when
      they are not, every operation in this group answers `403`. Any member of
      the account can read. Updating a company and linking or unlinking contacts
      is open to agents, supervisors, CX engineers and administrators; an
      assistant is read-only.
paths:
  /v1/accounts/{accountId}/automation-rules/confirm-create:
    parameters:
      - $ref: '#/components/parameters/CloudChatInstance'
      - $ref: '#/components/parameters/AccountId'
    post:
      tags:
        - Automation Rules
      summary: Confirm an automation rule
      description: >-
        Second half of creating a rule. Send back only the `proposal_token` from
        `proposeAutomationRuleCreate`; the rule saved is exactly the one that
        was previewed, created off and placed after the last rule of its event
        at the moment of the confirm. The token is consumed by this call. If any
        rule of the same event was created, changed or removed after the
        proposal, nothing is written and the call answers 409 `stale_proposal`:
        propose again, so the preview and its warnings reflect the rules as they
        are now. **Administrator only — an agent token gets a 403.**
      operationId: confirmAutomationRuleCreate
      requestBody:
        required: true
        content:
          application/json:
            schema:
              $ref: '#/components/schemas/AutomationRuleConfirmRequest'
      responses:
        '201':
          description: >-
            Created. The rule is off until a person turns it on in the
            automations screen.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/AutomationRuleCreateResult'
        '400':
          description: >-
            The `proposal_token` is missing, invalid, expired, already used,
            issued to another user or account, or belongs to another kind of
            proposal (`details[0].code` is `invalid_proposal`). Nothing was
            written. Propose the change again.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error:
                  code: bad_request
                  message: The request is malformed.
                  details:
                    - field: base
                      code: invalid_proposal
                      message: >-
                        The proposal token is invalid, expired, already used or
                        belongs to another proposal. Propose the change again.
        '401':
          $ref: '#/components/responses/Unauthorized'
        '403':
          description: >-
            Two situations answer with this code: the account is suspended (the
            reason every endpoint shares), or your token is not an administrator
            — this operation requires one.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error:
                  code: forbidden
                  message: You are not allowed to perform this action.
        '404':
          $ref: '#/components/responses/NotFound'
        '409':
          description: >-
            The event's rules changed after the proposal (`details[0].code` is
            `stale_proposal`). Nothing was written.
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/Error'
              example:
                error:
                  code: conflict
                  message: >-
                    The request conflicts with the current state of the
                    resource.
                  details:
                    - field: base
                      code: stale_proposal
                      message: >-
                        The rules changed after the proposal was made. Read them
                        again and propose the change again.
        '429':
          $ref: '#/components/responses/TooManyRequests'
        '500':
          $ref: '#/components/responses/InternalError'
components:
  parameters:
    CloudChatInstance:
      name: cloudchat-instance
      in: header
      required: true
      description: >-
        Your Cloud Chat instance ID — an integer, fixed for your company, told
        at onboarding. [The API
        overview](/api-reference/cloudchat/overview#two-headers-every-call)
        explains how instances work, how to find yours, and the errors a wrong
        or missing value produces.
      schema:
        type: integer
        example: 1
    AccountId:
      name: accountId
      in: path
      required: true
      description: >-
        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.
      schema:
        type: integer
        example: 1
  schemas:
    AutomationRuleConfirmRequest:
      type: object
      required:
        - proposal_token
      properties:
        proposal_token:
          type: string
          description: >-
            The `proposal_token` from the matching propose call. Nothing else in
            the body is read.
          example: eyJfcmFpbHMiOnsiZGF0YSI6eyJqdGkiOiI0YjEw...
    AutomationRuleCreateResult:
      type: object
      required:
        - automation_rule
      properties:
        automation_rule:
          $ref: '#/components/schemas/AutomationRule'
    Error:
      type: object
      description: The error envelope every Cloud Chat API response uses.
      required:
        - error
      properties:
        error:
          type: object
          required:
            - code
            - message
          properties:
            code:
              type: string
              description: >-
                The stable, machine-readable reason. Branch on this, never on
                `message`.
              enum:
                - unauthorized
                - forbidden
                - not_found
                - validation_failed
                - conflict
                - bad_request
                - internal_error
                - rate_limited
                - service_unavailable
              example: not_found
            message:
              type: string
              description: >-
                The reason in words, localized to your account's language
                (English, Spanish or Brazilian Portuguese; English when the
                account is set to anything else). Wording changes with the
                account and between releases, so never match on it.


                Two cases stay in English whatever the account is set to:
                `unauthorized`, decided before any account is known, and the
                account-level `not_found`, which must not reveal the account's
                language.
              example: Resource could not be found.
            details:
              type: array
              description: >-
                Present on some rejections — a 400 for a refused query parameter
                or upload mode, for example. One entry per offending field,
                localized to the account's language like `message` — match on
                `code` and `field`, never on the text.
              items:
                type: object
                required:
                  - field
                  - code
                  - message
                properties:
                  field:
                    type: string
                    description: Which request field the rule was about.
                  code:
                    type: string
                    description: Stable, machine-readable reason.
                  message:
                    type: string
                    description: The rule in words.
    AutomationRule:
      type: object
      description: >-
        An automation rule of the account — administrator only on every
        operation of this group.
      required:
        - id
        - name
        - description
        - event_name
        - active
        - order_id
        - conditions
        - actions
        - managed_by
        - execution_delay
        - delay_trigger
        - folder_id
        - created_at
        - updated_at
      properties:
        id:
          type: integer
          example: 9
        name:
          type: string
          example: Auto-close stale conversations
        description:
          type: string
          nullable: true
          example: Closes conversations idle for 7 days.
        event_name:
          type: string
          description: >-
            The event that triggers evaluation, e.g. `conversation_created`,
            `conversation_updated`.
          example: conversation_updated
        active:
          type: boolean
          example: true
        order_id:
          type: integer
          description: >-
            Execution order among the account's automation rules for the same
            event, ascending. This is what `sort=execution_order` (the default)
            orders by.
          example: 1
        conditions:
          type: array
          description: >-
            The rule's condition set, in the same shape the dashboard's
            automation editor writes.
          items: {}
        actions:
          type: array
          description: >-
            The rule's action set, in the same shape the dashboard's automation
            editor writes.
          items: {}
        managed_by:
          type: string
          nullable: true
          description: >-
            Who maintains the rule besides the account's administrators. `null`
            for a rule people own. `claudia_integration` marks a rule the
            ClaudIA integration created and keeps in sync: it can be read, but
            the API refuses to edit it or move it in the execution order.
          example: null
        execution_delay:
          type: integer
          nullable: true
          description: >-
            How many minutes the rule waits before it runs, counted from the
            moment `delay_trigger` describes. `null` for a rule that runs as
            soon as its event fires. Always set together with `delay_trigger`.
          example: null
        delay_trigger:
          type: string
          nullable: true
          description: >-
            What the wait in `execution_delay` measures. `customer_unresponsive`
            and `agent_unresponsive` require the `message_created` event, and
            `status_idle` requires `conversation_updated`. `null` when the rule
            does not wait.
          enum:
            - customer_unresponsive
            - agent_unresponsive
            - status_idle
            - null
          example: null
        folder_id:
          type: integer
          nullable: true
          description: >-
            The folder the rule is filed under in the automations screen, or
            `null` when it is not in one. Folders are organized in the screen;
            the API does not set this field.
          example: null
        created_at:
          type: string
          format: date-time
          example: '2026-05-02T11:04:17.000Z'
        updated_at:
          type: string
          format: date-time
          example: '2026-08-10T14:32:05.123Z'
    GatewayError:
      type: object
      description: >-
        Rejected by the gateway before Cloud Chat saw it, so it does not use the
        `error` envelope.
      required:
        - message
      properties:
        message:
          type: string
          example: API rate limit exceeded
        request_id:
          type: string
          description: Gateway request id. Quote it when reporting a problem.
          example: f3f7567638d4b65a8003057d0c77d275
  responses:
    Unauthorized:
      description: >-
        No Bearer token, or one that is expired, malformed, or not a Cognito
        token. Sign in again for a fresh `id_token`.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: unauthorized
              message: >-
                Authentication is required. Send a valid Bearer token in the
                Authorization header.
    NotFound:
      description: >-
        The resource is not there for you. Three situations answer with this
        code, and the first two apply to **every** endpoint — the account is
        resolved before anything else runs, so a list or a create fails this way
        too:


        - the account does not exist on this instance,

        - the account exists but your token has no membership on it,

        - on an endpoint that names one, the resource it names (a canned
        response, a portal, an article) does not exist where the path says it
        does.


        The first two are deliberately indistinguishable — same status, same
        body, and the message stays in English in both, since translating it
        would reveal the account's configured language. So you cannot use this
        endpoint to find out which account ids exist. The third case is
        localized like every other error, which is safe because you only reach
        it once membership is established.


        Either way a 404 is not worth retrying. Check the `accountId`, the
        `cloudchat-instance` value, and that your user is a member of the
        account.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: not_found
              message: Resource could not be found.
    TooManyRequests:
      description: >-
        Rate limited per credential. Note the envelope: this one is `{
        "message": ... }`, because the request never reached the API.


        Don't hardcode the limit — read it from the response. `Retry-After` says
        how many seconds to wait, and every response (not just this one) carries
        `ratelimit-limit`, `ratelimit-remaining` and `ratelimit-reset`, the last
        in seconds.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/GatewayError'
          example:
            message: API rate limit exceeded
    InternalError:
      description: >-
        Something failed on our side. The response never carries the underlying
        error, but it is reported to our monitoring automatically — no need to
        file anything for a one-off.


        Retrying is reasonable, with one caveat on `POST`: a 500 does not prove
        the write did not happen, so a retry can come back `422` with
        `short_code` already taken. That 422 means the first attempt succeeded —
        list the account and confirm before treating it as a failure.
      content:
        application/json:
          schema:
            $ref: '#/components/schemas/Error'
          example:
            error:
              code: internal_error
              message: An unexpected error occurred. Please try again later.
  securitySchemes:
    bearerAuth:
      type: http
      scheme: bearer
      bearerFormat: JWT
      description: >-
        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.

````

This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.