> ## Documentation Index
> Fetch the complete documentation index at: https://docs.elementum.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Automations FAQ

> Frequently asked questions about building automations in Elementum, including how to chain automations and share output between them.

## Chaining Automations

<Accordion title="How do I build an automation that references another automation's output?">
  The simplest pattern is to bridge the two automations through a field on a record. The first automation writes its result to a field with an [Update Record Fields action](/workflows/automation-actions-reference#update-record-fields), and the second automation reads that field.

  **Set up the producer automation**

  1. Add an **Update Record Fields** action at the end of the first automation.
  2. Point it at the record you want to use as the bridge (often the record the automation is running on).
  3. Map the value or variable you want to expose into a field on that record — a dedicated Text, Number, or JSON field works well.

  **Set up the consumer automation**

  You have two options, depending on when the second automation should run:

  * **Fire automatically when the field changes** — Configure the second automation with a [Record is Updated trigger](/workflows/automation-triggers-reference#record-is-updated). Use **Add Changed Condition** to restrict it to changes on the bridge field so the automation does not run every time an unrelated field is edited. All fields on the updated record, including the bridge field, are available as variables in downstream actions.
  * **Read the field on demand** — If the second automation runs on its own schedule, from an [Automation Button](/workflows/automation-buttons), or via webhook, have it look up the record with a **Search Records** action and reference the bridge field from the search result.

  **When to use this pattern**

  * The two automations run under different triggers, schedules, or teams and should stay independent.
  * You want the output persisted and visible on the record for reporting, audit, or manual review.
  * The consumer may need to run more than once against the same producer output, or long after the producer finished.

  <Tip>
    If you want a single, synchronous call — where the caller waits for the callee and reads its outputs directly — use the [Run Automation action](/workflows/automation-actions-reference#run-automation) against a helper automation that has an [On-Demand Trigger](/workflows/automation-triggers-reference#on-demand-trigger). That avoids the round-trip through a record field, but couples the two automations into one execution. See [Automation Chaining](/workflows/automation-best-practices#automation-chaining) for the trade-offs.
  </Tip>
</Accordion>

***

## Related Documentation

<CardGroup cols={2}>
  <Card title="Automation System" icon="workflow" href="/workflows/automation-system">
    Overview of triggers, actions, and how automations run
  </Card>

  <Card title="Automation Triggers" icon="zap" href="/workflows/automation-triggers-reference">
    Reference for every trigger, including Record is Updated
  </Card>

  <Card title="Automation Actions" icon="play" href="/workflows/automation-actions-reference">
    Reference for every action, including Update Record Fields and Run Automation
  </Card>

  <Card title="Automation Best Practices" icon="check" href="/workflows/automation-best-practices">
    Patterns for composable, efficient automations
  </Card>
</CardGroup>