Triggers and conditions reference
Use this table when designing automations. Exact names in the UI may differ slightly by release; the behavior column is authoritative.
Triggers
| Trigger | Type | Description | Example |
|---|
| Schedule | Scheduled | Fires at intervals you define (daily, weekly, cron expression). | Every Monday 09:00 org timezone — post weekly goals reminder. |
| Check-in completed | Event | Fires when a check-in run finishes or a threshold of responses is met. | When standup closes — send summary webhook to BI tool. |
| Form submitted | Event | Fires when a Dailybot form receives a submission. | IT request form submitted — notify #it-triage. |
| New member joined | Event | Fires when a user joins the org on the connected chat platform. | Welcome DM sequence for new hires. |
| Webhook received | Webhook | Fires when an HTTP request hits your automation’s inbound URL with valid auth. | CI pipeline posts build status — post pass/fail to channel. |
Conditions
| Condition | Type | Description | Example |
|---|
| Time window | Time | Only run if current time is inside start/end hours (respects timezone). | Actions run 08:00—18:00 local only. |
| Day of week | Time | Restrict to selected weekdays. | Skip weekends for digest posts. |
| User role | User role | Require actor or target to be Org Admin, Team Manager, or Member. | Notify managers only when blocker from Member. |
| Value match | Value match | Compare form field or check-in answer to string, number, or regex. | If priority field equals P1, page on-call. |
| Channel scope | Value match | Limit to specific channel IDs or names configured in the automation. | Only mirror events from #sales. |
Related articles