Alerts and notifications
Use workflows to turn conversation problems and trends into actions such as Slack messages, support tickets or emails. Alert collection is managed by LogicDialog. You do not need to configure monitoring services, thresholds or webhook URLs.
Choose what to respond to
Add a LogicDialog event trigger to a workflow and choose an event:
Conversation error relates to one conversation. Monitoring alerts relate to activity across an assistant, rather than one conversation. An unsuccessful business outcome alone does not count as a technical conversation error. A failed action can produce a conversation error even if the conversation recovered and continued.
Send an alert to Slack
- Open Workflows in a workstream and create a workflow.
- Add a LogicDialog event trigger and select Monitoring alert raised.
- Optionally add a condition to choose which alerts to act on.
- Connect a Slack integration node, select a connection and choose the channel.
- Set the message, save the workflow and apply the workstream to its destination environment.
For example, use these fields in a message:
For conversation errors, use {{data.conversation_id}} and {{data.error.message}} instead. You can build separate workflows for raised and resolved alerts, or connect a different action such as creating a ticket. Alert workflows are notifications; an HTTP response node is not required.
Decide which alerts need action
Monitoring event data includes:
For example, match alert.monitor to webhook_error_spike to send webhook-related alerts to your technical support channel. Other categories include elevated_conversation_failure_rate, elevated_tool_failure_rate, guardrail_trigger_spike, call_initiation_error_spike and low_evaluation_success_score.
Understand workspace and environment scope
Alerts are routed only to the workspace that owns the affected assistant. An alert for another customer’s assistant does not trigger your workflows.
An assistant-wide trend can combine activity from multiple environments. Such alerts reach subscribed workflows in each deployed environment of the owning workspace, with source_environment: null. The workflow decides whether to act. For example, filter on destination_environment if only your Live workflow should send Slack notifications. This selects which workflow sends the notification; it does not prove the problem happened in Live.
Only deployed workflows receive alerts. Saving or previewing a draft does not subscribe it to operational alerts.
Delivery and retries
LogicDialog verifies incoming alerts and deduplicates successful delivery to each destination. Raised, resolved and dismissed notifications are handled separately, and a later occurrence can trigger another run.
A workflow that fails after sending a message can repeat that action on retry. Where needed, use alert.id, alert.action and alert.occurred_at together as an idempotency key in the receiving system. Previewing an integration action can send a real notification.