Skip to main content
How Decision Required and remembered decisions handle data. Automated checks reduce what leaves the platform but are not a guarantee, so choose a Slack channel whose members you would trust with the run’s context.

​
What goes to Slack

  • The card: the agent’s question, a summary of the run so far and the answer options.
  • The answer as the card shows it afterwards. A free-text reply is shown as typed, up to 120 characters, when it passes the personal-data pattern checks and uses plain Latin letters; otherwise “Free-text reply received”. A name typed into a reply can therefore appear.
  • On a seen-before card, a summary of the earlier question and answer.
  • Notices that a saved answer was applied.
  • With Add Error Code, the suggested code, its description and the step name.

​
What goes to your webhook

Only endpoints subscribed to these events receive them, signed like every webhook:
  • agent.decision_requested: the question, a short context, the fields and options, and, when available, a signed screenshot link that expires per your file URL expiration.
  • agent.decision_answered: how it closed and, when answered, where, by whom (a Slack user id, a CloudCruise user id or an API key id) and the answer.
  • agent.decision_applied: the remembered error’s id, the saved recovery that was followed, and who approved it and when.

​
Screening

Card text is checked by an automated screen before sending, which uses an external model provider and can miss content. A reply reaches the AI model before it is screened. A card that fails is withheld, not redacted. A suggested error code that fails is not offered, and the card shows the plain Add Error Code button.

​
What is stored

Run input values are masked out of error messages before matching, and only the normalized message is stored. Saved instructions and questions that fail the personal-data screen are rejected, not trimmed. Slack retention is set by your Slack workspace. Do not type secrets or personal data into a reply.