> For the complete documentation index, see [llms.txt](https://flapjax.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flapjax.gitbook.io/docs/automations/sequences.md). # Sequences {% hint style="info" %} **Tip:** reach for sequences on onboarding flows, lead nurturing, drip campaigns, re-engagement series, and anything built around one person's experience. {% endhint %} ### How Sequences Work A person who qualifies for a sequence enters at the trigger and moves through each action in order. The whole flow can read that person's data: their attributes, their labels and anything from the triggering event. Actions such as Send Email, Update Person and Assign Label act on the trigger person by default. That person context is what separates sequences from [workflows](/docs/automations/workflows.md). You never look up or select a person, since the sequence already knows who it works with. *** ### Trigger Types Sequences take four trigger types. The [Triggers guide](/docs/automations/triggers-and-scheduling.md) covers the full configuration. #### Manual A manual sequence runs on nobody's schedule. You enrol people explicitly: from a person's detail page, in bulk from the People list, or through another automation's Enrol in Sequence action. The trigger itself needs no configuration. #### Rule-Based The sequence fires whenever a specific event happens. The available events are: * **Person events**: person created, updated or deleted * **Label events**: label assigned to or removed from a person * **Communication events**: an email or SMS delivery status arriving * **Stack events**: a record created or updated in a stack that carries a person attribute Stack events appear only for stacks with a person or people attribute, which keeps a person in front of the sequence at all times. Narrow which people qualify with a segment filter and custom rules from the rule builder. #### Specific Date and Time The sequence runs once, at a moment you choose. Set a date, a time and a timezone. Add a segment filter and custom rules to control who takes part. Activating it moves the sequence to Scheduled. Once it executes, the status becomes Fired and it never runs again. #### Recurring Schedule The sequence runs repeatedly on a pattern: hourly, daily, weekly or monthly. Each firing brings qualifying people into the flow. A segment filter and custom rules narrow who joins on each run. *** ### Re-Entry Policy The re-entry policy decides what happens when a person qualifies to enter a sequence they are already inside. * **Unlimited re-entries** lets the person enter as often as they qualify. * **No re-entries allowed** keeps them out until they exit. * **Limited re-entries** sets a maximum number of entries, with 1 as the minimum. The setting appears on Manual, Rule-based and Recurring Schedule triggers. Specific Date and Time triggers skip it, since they run once. *** ### Statuses Sequences carry five possible statuses: * **Active**, live and processing people. It shows as "Live". * **Inactive**, off and processing nothing. It shows as "Draft". * **Paused**, stopped by the system over an issue such as a deleted segment or a missing attribute. An orange warning banner explains what went wrong. * **Scheduled**, set to activate at a future date and time. Unique to sequences. * **Fired**, a one-time scheduled sequence that already ran. Unique to sequences. Scheduled and Fired apply to the Specific Date and Time trigger alone. Every other trigger type moves between Active, Inactive and Paused. *** ### Enrolling People Three routes get a person into a sequence with a Manual trigger. #### From a person's detail page Open any person and use **Enrol in Sequence** to add them to an active manual sequence. #### In bulk from the People list Tick people with the checkboxes on the People page, then choose **Enrol in Sequence** from the batch action bar. Enrol your current selection, or everyone matching your filters. #### From another automation Use the **Enrol in Sequence** action inside any automation to push a person into an active manual sequence. In a sequence, the action takes the current person on its own. In a workflow, you specify the person with a variable. *** ### Monitoring Participants Sequences track **participants**, the people who entered the flow. Open the monitoring page from the **Participants** button in the builder toolbar, or from the three-dot menu on any sequence in the list. The participants table shows each person's name, external ID, entry count and entry timestamp. Search participants by name, select rows with the checkboxes, and scroll to load more. Click any row for an activity timeline of that person's journey through the sequence: every action processed, message sent, delay completed and error hit. The [Monitoring guide](/docs/automations/monitoring-runs-and-participants.md) covers the page in full.