Automation triggers
Every automation starts with a trigger, the event that starts the workflow. Triggers run automatically when something happens in your workspace, and each trigger can be filtered to match specific criteria so the automation only runs when the right conditions are met.
Entity triggers
Entity triggers run when a record gets created, updated, or deleted. Supported entities include tasks, invoices, recurring invoices, proposals, contracts, and forms. Forms also support a "submitted" trigger that runs when a respondent completes a form. A "created" trigger runs the moment a new record appears. An "updated" trigger runs when a specific field changes, like a status moving to "Approved" or an assignee being reassigned. A "deleted" trigger runs when a record gets removed.
Date-based triggers
Date-based triggers run relative to a date field on a record, such as a task's due date, an invoice's issue date, or a recurring invoice's upcoming billing date. The trigger runs relative to a date field, with direction options "Before the date", "After the date", or "On the date", and a configurable offset (for example, 3 days before the due date or 1 day after the issue date). The offset supports hours and days, with a maximum offset of 30 days. Date-based triggers are available for tasks, invoices, proposals, contracts, and recurring invoices.
Webhook triggers
Webhook triggers run when an external service sends an HTTP request to a unique webhook URL generated by Plutio. External tools and services that support outbound webhooks can start an automation by posting to that URL, which means automations aren't limited to events that happen inside Plutio.
Trigger filters
Each trigger supports filters that narrow when the automation runs. A "task created" trigger can be filtered to a specific project, status, or assignee. An "invoice status changed" trigger can be scoped to run only when the status moves to "Overdue". Filters on triggers mean one automation runs only for the exact scenarios it's built for, and multiple automations can share the same trigger type with different filters to handle different situations.
