> ## Documentation Index > Fetch the complete documentation index at: https://80x.mintlify.site/llms.txt > Use this file to discover all available pages before exploring further. # Record added to list > The Record added to list trigger (List triggers) starts a workflow whenever a record joins the selected list. The **Record added to list** trigger (List triggers) starts a workflow whenever a record joins the selected list. A list is a saved collection of records, such as your active deal pipeline. The trigger fires no matter how the record was added. That covers a person dragging it in, another workflow adding it, or the API adding it. Treat it as the "something just entered this process" signal. Use it for pipeline-entry automation such as intake checklists, owner assignment, and stage-zero hygiene. | | | | - | - | | **Category** | List triggers | | **Credit cost** | Free. Triggers consume no credits. | | **Engine** | New Workflows engine (June 2026+) | | **Plan availability** | All plans | | **Limits** | None documented. | ## Inputs | Input | Type | Required | Default | Notes | | - | - | - | - | - | | List | List | Yes | None | The list to monitor. The workflow fires once for each record added to this list. | ## Outputs A list entry is the row that represents one record's membership in a list. It carries the record itself plus any attributes that belong only to that list. | Output | Type | Example | Notes | | - | - | - | - | | List entry | List entry | `Acme: Investment pipeline` | The new entry, including its list attributes and its parent record. | | Actor | Actor | `Priya Sharma` | Who or what added the record. This is a member, a workflow, or the API. | | Timestamp | Datetime | `2026-06-11T14:32:00Z` | When the record joined the list. | Reference the new entry's parent record downstream as `{{ steps.record_added_to_list.record }}`, and the actor as `{{ steps.record_added_to_list.actor }}`. ## Behavior The trigger fires once each time a record is added to the chosen list, in the order the additions happen. Each addition starts its own independent run. So adding ten records to the list starts ten runs. The actor reflects whatever performed the addition. A workflow that adds records to this list counts as an actor. So this trigger fires for workflow-added records exactly as it does for manual ones. That is the mechanism behind chained automations, and the cause of the first gotcha below. List attributes on a brand-new entry are usually empty at the moment the record is added. A stage attribute may apply its default, but the rest of the entry's list attributes have no value yet. Most values land a beat later, when a person or a follow-up workflow fills them in. A record can sit in a given list only once at a time. So the trigger fires once per record, per membership. Remove the record from the list and add it again, and that starts a fresh run. Historically, Attio's API let a record hold more than one entry in the same list. The current workflows model treats membership as a single entry. That is why you re-fire this trigger by removing and re-adding the record, not by adding it twice. ## Gotchas * **Workflow-added records re-trigger this workflow.** A workflow counts as the actor. So any automation that runs [Add record to list](/reference/lists/add-record-to-list) on the monitored list fires this trigger too, chaining the two workflows. When that chain is the design, leave it. When it is not, filter on the actor. Set *Updated by → Type → is not → Workflow* right after the trigger. See [Infinite loops and safety](/explanation/infinite-loops-and-safety). * **Re-adding a recycled record fires the trigger again.** Removing a record from the list and adding it back starts a new run, since each membership is a separate add. When you design for it, re-adding is a deliberate "recycle this lead" signal. When you do not, it is a source of duplicate tasks and Slack pings. Add a [Filter](/reference/conditions/filter) on entry state if a recycled record should follow a different path. * **List attributes are empty at add time.** Say your logic reads a list attribute that gets its first value during the add. The read returns nothing, because the value is not set yet when the trigger fires. Trigger on [Attribute value changed](/reference/triggers/attribute-value-changed) pointed at that list attribute instead. It fires when the value is set, including at add time. ## Examples ### Running an intake checklist on a new pipeline entry This example screens every company that enters an investment pipeline and assigns the first task automatically. | Field | Value | | - | - | | Trigger | Record added to list | | List | `Investment pipeline` | | Step 1 | [Update list entry](/reference/lists/update-list-entry): set `stage` to `New`, set `source` to its default | | Step 2 | [Create task](/reference/tasks/create-task): `Initial screen`, assigned to the analyst, due in 2 days | | Step 3 | Slack message to `#dealflow` with the parent company's name and domain | A company added to `Investment pipeline` lands on stage `New`, gets an `Initial screen` task due in two days, and posts a one-line alert to `#dealflow`. ### Ignoring records that another workflow added This example runs the intake checklist only for records a person added, so a feeder workflow that bulk-adds records does not trigger a second round of tasks. | Field | Value | | - | - | | Trigger | Record added to list | | List | `Investment pipeline` | | Step 1 | [Filter](/reference/conditions/filter): `Updated by → Type → is not → Workflow` | | Step 2 | [Create task](/reference/tasks/create-task): `Initial screen`, assigned to the analyst | A record dragged in by `Priya Sharma` reaches the [Create task](/reference/tasks/create-task) step and produces an `Initial screen` task. A record added by a feeding workflow stops at the [Filter](/reference/conditions/filter) and creates nothing. ## Source [Attio Workflows block library](https://attio.com/help/reference/automations/workflows/workflows-block-library). Last reviewed against the Attio Help Center, June 2026. ## See also * [List entry updated](/reference/triggers/list-entry-updated) * [Add record to list](/reference/lists/add-record-to-list) * [Records vs list entries](/explanation/records-vs-list-entries) * [Choosing the right trigger](/explanation/triggers) * [Attio Workflows block library](https://attio.com/help/reference/automations/workflows/workflows-block-library) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.