Automations can react when a document is generated
Run workflows after an invoice or receipt is generated and combine them with a document-presence condition on the order.
Automations can react when a document is generated
What changed?
Automations now support the invoice_generated and paragon_generated events. You can also use order_has_invoice and order_has_paragon conditions to check whether an order already has a valid document number.
Benefit
You can build workflows that depend on a document being ready, such as performing a follow-up action after a receipt is generated successfully. A presence condition lets you combine that state with another event without triggering a workflow by itself.
How to use it
Open the automation builder, add a document-generated event or an invoice/receipt presence condition, then configure the action and any other conditions. For a receipt, the event occurs after the first successful number assignment and PDF generation.
Important limitations
The order_has_* conditions are passive: they work together with an active event and AND logic, but do not start a workflow on their own. An HTML preview and downloading an existing document do not trigger a generated event. Documents in NULL or GENERATING state are treated as absent.