Chatwoot capabilities

Use this index to choose the Chatwoot operation family that owns your task and to interpret its AIP contract before invocation. The reviewed surface contains 150 fixed account API operations and three connector-level composites.

The source-derived capability snapshot owns the ordered machine inventory. Focused pages own inputs, results, side effects, and task guidance; the JSON snapshot does not replace runtime discovery or the source that constructs each contract.

Catalogue identity

A matching capability ID does not prove that a tenant may discover it. The admitted connector version, operation allowlist, tenant route, artifact, and provider revision remain part of capability identity.

Choose a family

Retry means the capability contract advertises connector retry support. It does not authorize an application to repeat a call without checking Action identity, terminal state, and provider outcome.

Read a capability ID

A catalogue capability uses its exact operation suffix:

cap:chatwoot:conversation.list
│            │            └─ operation
│            └────────────── resource family
└─────────────────────────── connector namespace

Nested resources retain each stable segment:

cap:chatwoot:team.member.create
cap:chatwoot:contact.note.update
cap:chatwoot:report.inbox_label_matrix

The three composites use colon-separated connector-owned names:

cap:chatwoot:message:create
cap:chatwoot:conversation:status
cap:chatwoot:conversation:handoff

Do not infer a capability from an upstream route. Use the admitted manifest or the source-derived snapshot.

Catalogue binding metadata identifies the connector, operation suffix, provider method, fixed path template, and upstream revision. The configured account is inserted by the host and is not part of the capability ID.

HTTP method and operation class

The 150-operation provider catalogue has this method split:

The reviewed catalogue contains no PUT operation. The connector classifies only GET as a read. The three composites are also mutations.

Capability kind legend

Provider records remain callable Tools because the native AIP resource-read surface has no Action handler. A CRUD name does not change the executable capability kind.

Risk legend

Risk is policy input, not authorization by itself.

The four non-delete high-risk catalogue operations are:

• macro.execute;
• contact.import;
• contact.export;
• inbox.webhook.register.

High risk does not mean the other mutations are reversible. Every catalogue mutation can change external customer-service state.

Approval legend

Approval is required for:

• all 88 catalogue mutations; and
• all three connector-level composites.

The 91 approval policies use the tenant-policy selector and a 900,000 ms validity window. They require:

• a reason;
• an input snapshot;
• a policy decision.

The approved record must bind the authenticated actor, tenant, capability, Action, policy hash, and exact input. Expiry or an input change requires a new decision.

Idempotency and retry legend

An idempotency key identifies one intent; it does not prove that an upstream Chatwoot deployment deduplicates provider requests. Reuse the same key only with the same capability, account, Action identity, and canonical input.

If a mutation response is lost after provider dispatch, preserve the same Action and key and inspect durable state. Do not create a replacement Action or repeat the provider operation automatically.

Execution legend

All 153 capabilities advertise:

Catalogue contracts publish a 120,000 ms timeout hint, a 30,000 ms maximum queue-delay hint, and a 99.9% availability target. Composite hints are narrower. These values are contract metadata, not a measured deployment SLO or qualification result.

Side-effect legend

Catalogue operations declare:

• read plus external_network for GET;
• write plus external_network for every mutation.

The composites add more specific markers:

Side-effect markers are a minimum policy signal. A generic provider mutation may still trigger notifications, automation, assignment changes, exports, or downstream webhooks.

Compensation legend

The 62 reads require no compensation. All 91 mutations declare rollback_not_supported and name no compensating capability.

Approval and idempotency do not make a mutation reversible. Recovery must inspect the actual Chatwoot object and use a separately authorized provider operation only when its consequences are understood.

Use the machine snapshot

assets/capabilities.json contains:

• exact source and upstream revisions;
• aggregate family, method, kind, risk, approval, mutation, and retry counts;
• one ordered record for each of 153 capabilities;
• stable IDs, names, kinds, risks, provider methods and path templates;
• approval, idempotency, execution, side-effect, data, and compensation fields.

Its reviewed SHA-256 is:

460f413f87b12bbc4e38e9943b6ecf9ba9192c25ee903892d4b6886ca4efa0b5

The asset is a source-derived review artifact. It does not prove registry admission, tenant authorization, artifact qualification, or live provider compatibility.

Choose the next page

• Use accounts-agents-teams-and-bots.md for account access and workforce configuration.
• Use inboxes-integrations-and-webhooks.md for channels and provider-side integration registration.
• Use conversations-and-messages.md for the customer-support lifecycle.
• Use contacts-and-companies.md for customer and organization records.
• Use automation-macros-and-canned-responses.md for reusable behavior.
• Use labels-attributes-and-filters.md for metadata and saved views.
• Use reports-audit-and-events.md for read-only operational evidence.
• Use customer-portals.md for help-center content.
• Use aip-composite-operations.md for connector-owned message, status, and handoff behavior.

Related documentation

• Chatwoot connector overview
• Chatwoot connector configuration
• Capabilities and contracts
• Approvals and policy
• Conformance and qualification