Automation triggers
Every automation starts with a trigger, the event that sets the chain in motion. Triggers fire 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 fire when a record gets created, updated, or deleted. Supported entities include tasks, invoices, recurring invoices, proposals, contracts, forms, and contacts. Forms also support a "submitted" trigger that fires when a respondent completes a form. A "created" trigger fires the moment a new record appears. An "updated" trigger fires when a specific field changes, like a status moving to "Approved" or an assignee being reassigned. A "deleted" trigger fires when a record gets removed.
Date-based triggers
Date-based triggers fire 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. A scheduled trigger can fire before, after, or on a specific date field, with a configurable offset (for example, 3 days before the due date or 1 day after the issue date). The offset supports minutes, 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 fire 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 fires. A "task created" trigger can be filtered to a specific project, status, or assignee. An "invoice status changed" trigger can be scoped to fire 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.
