Every Fuse automation is made of three kinds of building blocks.
Triggers
A trigger is the event that starts an automation. An automation needs at least one trigger, and any one of its triggers can start it. Triggers can come from Fuse — for example, signals and engagement — or from connected apps.
Conditions
A condition (sometimes called a gate) checks whether a record should continue. Records that don’t meet the condition stop at that step.
Actions
Actions do the work: for example, enriching a contact, adding a record to a list, updating your CRM, or sending a notification.
Wait steps
A wait step pauses a run before it continues. A run waiting on a wait step can be continued early.
Each step’s output
Each step produces output that later steps can use, so information from the trigger can flow through the whole automation.