> 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/action.md).

# Action

Run an app function using values from your workflow

The **Action** step passes configured inputs to an app function. Actions commonly send data from Middle to another system or perform an operation in a connected app.

### Configure action inputs

Click the **+** on a workflow branch and add an **Action** step. Choose the action you want to perform, then configure its inputs.

An input can be a fixed value or a dynamic value built with [workflow parameters](https://docs.middle.app/middle-docs/accounts/workflow-parameters). For example, you could map a member's email address from the triggering record and supply a fixed category for every record processed by the action.

Actions are generally presented as forms where you map values into the fields the app function expects.

<figure><img src="https://932524191-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Mks_UuU2atghAuA9bQz%2Fuploads%2FOXt3AeLf0VBt2z7urvzY%2FScreenshot%202026-10-09%20at%2011.37.50%E2%80%AFAM.png?alt=media&amp;token=3f86d485-b4df-49b0-8557-a2c100569254" alt=""><figcaption></figcaption></figure>

### Use action outputs

Save Action outputs in [workflow variables](https://docs.middle.app/middle-docs/accounts/defining-workflow-variables) to reference them in later steps.

For example, an action that creates a record in another system might return its ID. Saving that ID in a workflow variable lets a later step use it to perform another operation on the same record.

### Related documentation

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

{% content-ref url="/pages/VwpSQ6iUzDSY7aFIbigv" %}
[Workflow parameters](https://docs.middle.app/middle-docs/product/accounts/workflow-parameters.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/action.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.
