type: "intent" when creating them and type=intent when listing them.
Intent rules have a version lifecycle. A rule can have a current published version, draft versions, and archived historical versions. Drafts have no agent assignments and do not run in production until published.
Intent-rule endpoints
Endpoints shared with Business Rules
Intent-only endpoints
Typical draft workflow
1
Generate the draft content
Call Generate intent-rule draft with AI with natural-language instructions. The LLM returns a draft name, description, and rule tree. The response is not persisted yet.
2
Create the draft
Call Create intent rule with
status: "DRAFT" and the generated fields or your own tree. Do not send botIds for a draft.3
Update the draft
Call Update intent rule with
status: "DRAFT". Sending the status explicitly prevents an existing published version from being updated instead.4
Publish and assign
Read the draft’s
versionId, then call Publish rule draft with that draftVersionId and at least one agent ID.Intent-rule response fields
Intent-rule responses use the sharedRule shape and add lifecycle fields such as version, versionId, status, parentVersionId, publishedAt, isStale, and currentPublishedVersionId.
