Preventing automation cycles
Events caused by automations include a signed automation context in the following optional HTTP header. The JSON payload keeps its usual format.
X-Kaiten-Automation: <signed_context>
If your service responds by creating or modifying an individual card through the API, forward this header unchanged on every related API request. It preserves the list of previously executed rules so that the originating automation cannot execute again in the same chain. Keep contexts separate for independent webhook deliveries.
The context is company-specific and expires 24 hours after signing at delivery time. API authorization is still required. An invalid or expired header returns HTTP 400; do not retry the operation without the header. Events without an automation chain omit the header.
