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.
“What triggers exist?” (quick answer)
If you just want to know whether Dailybot can react to something, the short list:
- Time: on a schedule (cron-like) or at a fixed cadence.
- Check-in events: when a round completes, when a blocker is flagged, or when a response is submitted.
- Form / table events: when a Dailybot form receives a submission.
- Member events: when a user joins (or, on some plans, leaves) the org.
- Inbound webhook: an external system POSTs to your automation URL.
- Kudos events: when a kudo is given (subject to plan).
Want the full behavior, including parameters and examples? See the Triggers and Conditions tables below.
If your trigger does not fire, do not edit it blindly. Start at Automations troubleshooting.
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. |