> For the complete documentation index, see [llms.txt](https://docs.middle.app/middle-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.middle.app/middle-docs/product/accounts/workflow-steps/begin.md).

# Begin

Make the inputs that start a workflow available to its steps

The **Begin** step defines the inputs a workflow receives, such as the triggering record, the previous version of that record, or other values supplied by the trigger. These inputs are available as global variables within the workflow.

### Configure record inputs

Open the Begin step and configure the record input your workflow needs.

For a record input, the foreign key references the primary ID of the record supplied by the trigger or manual execution. The **Key to?** setting identifies that record's type.

<figure><img src="https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2Frl8RffQpufQApKHdlDVu%2FScreenshot%202026-10-09%20at%2011.32.16%E2%80%AFAM.png?alt=media&amp;token=133b5ab9-1c8b-49be-ba9d-2db2cc8add02" alt=""><figcaption></figcaption></figure>

In this example, the Begin step receives a single record. Later steps can use that record when building conditions or mapping values into an action.

### Scheduled workflows

Scheduled triggers do not supply inputs. Configure the Begin step without record inputs for a workflow that starts on a schedule.

A scheduled workflow can use a Bulk Workflow Execution Step to run another workflow against stored records.

### Related documentation

{% content-ref url="/pages/-MlClKo-Xl6F31yC\_oE4" %}
[Triggers](https://docs.middle.app/middle-docs/product/accounts/workflow-triggers.md)
{% endcontent-ref %}

{% content-ref url="/pages/VwpSQ6iUzDSY7aFIbigv" %}
[Workflow parameters](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters.md)
{% endcontent-ref %}

{% content-ref url="/pages/f8bDcFLfVUcP4y5qTbaH" %}
[Defining workflow variables](https://docs.middle.app/middle-docs/product/accounts/defining-workflow-variables.md)
{% endcontent-ref %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.middle.app/middle-docs/product/accounts/workflow-steps/begin.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
