Triggers and Actions Explained: How Automations Actually Work

A trigger is the event that starts an automation, such as a form submission. Actions are the steps that run afterwards, such as creating a record or sending an email. Conditions, delays and error handling sit between them to control when and whether each step runs.

What is a trigger?

A trigger is the thing that makes an automation start. It is always an event or a point in time: a form is submitted, a payment arrives, a record changes status, an email lands in a shared inbox, a file is added to a folder, or a schedule says it is nine o'clock on Monday.

Triggers come in a few broad kinds. Event triggers react to something happening in another system. Schedule triggers run at set times. Manual triggers start when a person presses a button. Some tools also support triggers that wait for a message from another system, often called a webhook. The names differ between tools, but the idea is the same.

What is an action?

An action is a step the automation carries out once it has started. Typical actions include creating or updating a record, sending an email or text message, adding a row to a spreadsheet, creating a task, posting a notification to a team channel, or calling another system to fetch or send information.

A single trigger can lead to many actions in order. The output of one step, such as the ID of a record just created, is often passed to the next step as input. Thinking about what each step needs from the one before it is the key to designing a flow that works.

What does a worked example look like?

Take a business that receives enquiries through a web form. A generic automation might look like this.

Nothing in this flow is specific to one product. Almost every automation tool, from simple visual builders to custom code, expresses the same sequence of a trigger followed by conditions and actions.

What are conditions and filters?

A condition is a yes-or-no check that decides whether the flow carries on, takes a different path or stops. A filter is a condition placed near the start so that only relevant events proceed. For example, only run for form submissions where the type is quote request, or only notify the sales team when the budget field is above a threshold you set.

Branching lets one trigger lead to different outcomes. If the enquiry is about support, create a ticket. Otherwise, create a sales lead. Keep branches few and well named. Many branches make a flow hard to read, test and hand over to someone else.

How do delays and waits work?

A delay pauses the flow for a fixed period, such as wait two days, or until a particular date. A wait-for-event step pauses until something happens, such as the customer replying or the invoice being paid, with a time limit after which the flow continues.

Delays are what make follow-up flows possible, but they carry a risk. The world may change while the flow is waiting. Always re-check the current state, for example whether the task has already been done, immediately before acting after a delay, rather than trusting what was true at the start.

What happens when something goes wrong?

Every automation will eventually meet a failure: a connected system is down, a field is empty, a password has expired or a record cannot be found. Good design assumes this and decides in advance what should happen.

Retries: for temporary problems, such as a service being briefly unavailable, trying again after a short wait is often enough.

Alerts: when a step fails for good, notify a named person with the details, so failures are not silent.

Logging: record what triggered the run, which steps completed and what went wrong, so someone can diagnose it later.

Safe stopping: if a step fails, think about whether earlier steps should be undone or flagged, so you are not left with a half-finished record.

Duplicate protection: make sure that running the same trigger twice does not create two records or send two emails.

How do you design a good automation?

Mapping the process before building, as described in our guide on how to map a process before automating, makes each of these steps easier.

Write the trigger in one sentence. If you cannot, the flow is probably trying to do too much.

List the data each step needs and where it comes from.

Add conditions for the cases you do not want to automate, and send those to a person.

Decide what a failure looks like and who is told.

Test with realistic examples, including awkward ones such as empty fields and repeated submissions.

Name the owner and note where the logs are.

Erudience services related to this guide

Use cases related to this guide

Terms used in this guide

Webhook

Frequently asked questions

What is the difference between a trigger and an action?

A trigger is the event that starts an automation, such as a form being submitted. An action is something the automation does afterwards, such as creating a record or sending an email. Every automation has one starting trigger and one or more actions.

Can an automation have more than one trigger?

Some tools allow it, and in others you build separate automations that share the same later steps. Either way, it is usually clearer to keep each flow focused on one starting event so that it is easy to understand and test.

What is a condition in an automation?

A condition is a check that decides whether the flow continues, branches or stops, based on data such as a field value or a status. Conditions stop automations acting on events they should ignore.

Why did my automation run twice?

Common causes include a trigger that fires on every edit to a record rather than only the first, two automations reacting to the same event, or a retry after a timeout. Add a check for whether the work has already been done, and look at the run log to see what started each run.

Do I need to write code to use triggers and actions?

Not necessarily. Many tools let you configure them visually. Code becomes useful for unusual systems, complex logic or strict data handling. The concepts are the same either way, which is why learning them first is worthwhile.