Automations overview

An automation is a rule that runs by itself: when something happens, Fiddle does something in response — no manual steps required. You build them in a visual builder, so no coding is involved.

The “when X, do Y” model

Every automation has two parts:

Part	What it is	Example
Trigger	The event that starts the rule	A sales order is created
Action	What Fiddle does in response	Notify the warehouse team

Most automations pair one trigger with one or more actions. You can also add conditions to narrow when the rule fires — for example, only when an order exceeds a value.

What you can automate

Common uses include alerting a team when stock runs low, assigning new orders to a board stage, emailing a customer when an order ships, and flagging records that need attention.

Automations run in the background. Once active, they apply to every matching event going forward — they do not act on records created before the rule existed.

Building blocks

• A trigger to start it.
• Optional conditions to filter when it runs.
• One or more actions to perform.

For the full list of options, see automation triggers and actions.

Next steps

Ready to create one? Follow build an automation.