# Choose an automation trigger

A trigger defines what starts a run and which starting data later steps can use. Choose it when creating an automation, or review the trigger included in a template.

> Automations is in Early access. Your workspace permissions determine which actions you can perform.

## Start a flow from scratch

1. Open [**Automations**](https://bird.com/dashboard/w/automations).
2. Select **Create automation** > **Start from scratch**.
3. Choose the starting event and enter a name.
4. Select **Create draft**, then select the trigger on the canvas to configure it.

The draft contains your chosen trigger. New runs require a published, active automation.

## Application event

Choose **Event from your application** when a business event in your system starts the workflow, such as an appointment being confirmed. This creates an **Application event** node. Configure its **Event name** and **Event fields**, including required fields and their types.

Names match exactly. For example, `appointment.confirmed` and `Appointment.Confirmed` are different names. Later steps can use the declared data without requesting it again.

The dashboard's connection guidance describes the event your application must send. Share the event name, fields, and connection details with the person responsible for that application.

With **No authentication**, anyone with the connection URL can submit events.

Use **Start run** on a published application-event automation to supply data manually. That starts a real run; use [Preview workflow](/docs/guides/automations/preview) to simulate draft data.

## Bird event

Choose an incoming-message option such as **Incoming SMS** to respond to SMS, email, or WhatsApp messages. This creates a **Bird event** node. The available events in the picker determine which triggers you can configure.

Set up the receiving channel before activating the trigger.

Add a filter when you want a subset, such as SMS addressed to a particular receiving number. A filter that does not match creates no run.

Trigger filters inspect the incoming event. Later steps can also use the received message details made available with that event. Email bodies require the separate **Read received email body** action.

Test the filter with sample data before publishing.

## Schedule

Use **Schedule** when the clock starts the workflow. Configure its repeat pattern and timezone, then check the next occurrence shown in the editor.

A schedule starts a run for a tick. It does not start one run per contact. Follow [Schedule runs and delay steps](/docs/guides/automations/schedules-and-delays) for timing and overlap behavior.

## Next steps

- [Use data from earlier steps](/docs/guides/automations/data).
- [Control overlapping runs and cancellation](/docs/guides/automations/run-settings).
- [Publish and manage automations](/docs/guides/automations/publishing).
- [Browse the Automations guides](/docs/guides/automations).

## Related resources

- [Preview your first automation](/docs/get-started/automations) (docs)