Test and Troubleshoot Automations
Test automations before relying on them for recurring work.
Run a private test from the editor
Section titled “Run a private test from the editor”Open the automation in a channel, then select Test automation. This runs the automation in a private thread in that channel, visible only to you. The thread is labeled with the automation name and links back to the automation editor so you can adjust the instructions after reviewing the response.
Private editor tests do not wait for a real schedule, webhook, Slack event, or RSS item. Use them to validate instructions and AI behavior before relying on live events.
Test checklist
Section titled “Test checklist”- Confirm the Space has the connections it needs.
- Send or wait for a representative trigger event.
- Open the generated thread.
- Inspect AI’s response and tool calls.
- Tune the automation instructions.
- Confirm the right people are notified.
Common issues
Section titled “Common issues”| Issue | What to check |
|---|---|
| No thread was created | Trigger setup, webhook URL, app permissions, schedule timing. |
| AI cannot access data | Connector scope, Space connection assignment, expired credentials. |
| Output is too broad | Narrow the trigger or add clearer instructions. |
| Too many notifications | Tune Space notification settings or automation instructions. |
Keep a feedback thread
Section titled “Keep a feedback thread”When an automation produces a weak result, fix the instructions close to the example. The best automation instructions usually come from real event payloads and real review feedback.