Automation and developers
Rules that move designs and orders along.
An automation runs its actions when something happens to a design, a print or an order, and its conditions hold.
Pro and Business
When
A design is committed, approved, or its customer asks for changes or gives an address; a print is made or fails; an order is placed, moves, fails, is cancelled or changes its delivery.
Then
- Approve the design, make its print, place its order
- Retry a failed order at another printshop, or cancel it
- Notify members, or email someone who is not one
- Call a webhook endpoint
- Filter, branch, wait for something to happen, or wait a while
Every run, recorded
Each time an automation fires, it records what each action did: done, skipped, blocked or failed, with the reason. Start from a recipe, such as approving on commit or ordering once printed.