Automations
An Automation is a when X happens, do Y rule. Konduit runs them for you automatically — they fire reliably regardless of who's logged in.
Anatomy
| Part | Description |
|---|---|
| Trigger | What fires the rule — task created, status changed, time logged, scheduled cron, etc. |
| Conditions | Optional filters on the trigger — only when severity = high, etc. |
| Actions | What to do — change status, assign, post comment, send webhook, send email |
Triggers
| Trigger | Fires when |
|---|---|
task_created |
New task created (UI, API, form) |
task_updated |
Task field changed |
task_status_changed |
Status transitions |
task_deleted |
Task soft-deleted |
task_assigned |
New assignee added |
task_due_soon |
Date-arrival with configurable lead time |
task_blocked / task_unblocked |
Dependency state changes |
comment_added |
New comment on a task |
time_logged |
Manual time entry created or running timer stopped |
row_inserted / row_updated / row_deleted |
DataTable row changes |
form_submitted |
Form submission received |
cron |
Scheduled trigger — every N minutes/hours/days |
Looking to make a single task recur on its own? That's a recurring task, not an automation. Use automations when you need an ACTION (email, webhook, row insert) to fire on a schedule; use recurring tasks when the WORK ITSELF is a task that should clone forward.
Conditions
Conditions filter the trigger. Mix-and-match field comparisons:
- "Only when Severity = High"
- "Only when Customer.Region = EU"
- "Only when assignee is Alice"
Compound logic with AND / OR is supported.
Actions
| Action | What it does |
|---|---|
| Change status | Set the task's status to a specific status |
| Assign | Add or replace assignees |
| Set field | Update any custom field |
| Post comment | Drop a comment on the task (supports template variables) |
| Send email | Send an email to recipients (supports templates) |
| Webhook | POST a JSON payload to a URL (HMAC-signed) |
| Create task | Create a new task in a target list |
| Update related | Update a related task (parent, dependency) |
| Schedule report | Run a query and email the result |
Cron-scheduled automations
Use trigger type cron for "run this every Monday at 9am" workflows. Pair with the send email or post comment action for digests, reminders, status reports.
Webhook signing
Webhook payloads are HMAC-SHA256 signed with a per-action secret. See API → Webhooks for verification details.
Audit log
Every automation run is logged — who triggered it, what conditions matched, what actions ran, success/failure. Available in Settings → Audit Log.
Limits
Automations have per-plan limits on runs/month. Free workspaces don't have automations. See pricing.