> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/workflow/build-workflow-steps/pass-inputs-into-a-workflow.md).

# Pass inputs into a workflow

In this section you will learn about Inputs, Outputs and Parameters

Workflow parameters hold values supplied by the trigger. Use them to pass a selected record ID, form value, or array into later steps.

## Understand the data flow

A typical component workflow passes a value along this path:

**Selected ticket → button input binding → workflow parameter → action field**

The older example below uses a record deletion and email action to illustrate two required values: a record ID and an email address. For a first test, use the non-destructive status update in [Build your first workflow](/workflow/build-your-first-workflow.md).

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F53PRd1SPwfrOsHigl8fs%2FSzxdx.png?alt=media\&token=bb61eff4-2c0b-4edc-a933-26878c20932a)

## Define a parameter

1. Open the workflow and select its trigger step.
2. Add a parameter such as `ticket_id`.
3. Choose the type matching the source field.
4. Enter a known fictional record's ID as a test value.

You can access parameters from the trigger action configuration or the workflow's trigger step:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FhUUmKeFsFynVJOw6D7aO%2Ffzbfd.png?alt=media\&token=b3b47dab-3c48-4e65-b979-04188fbe2041)

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FBBp5cnhULwC3wsiZkYGp%2Fdzrxtctr.png?alt=media\&token=2f9ce0d8-8a81-429b-998c-0f1bafac72a9)

A test value helps you configure a step. It does not replace the runtime value binding in the component action.

## Bind the app value

1. Return to the button or list action that runs the workflow.
2. Select the input corresponding to `ticket_id`.
3. Use the value picker to reference the selected row's ID.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FJNEJACvlzgD3N1e8e1lE%2Fzrbdx.png?alt=media\&token=30a0b735-089a-49c0-821a-29c8b82cf8d4)

## Use the parameter in a step

Select the action field, open **Formula**, and reference the workflow parameter.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FAucc6GbTJfIC30gM0pWr%2Fzsrdxctf.png?alt=media\&token=a43cba4e-aac6-4092-a389-65fc2f84c4d6)

The field also supports values exposed directly in the step's context:

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FSqZsSFlxdmDB4wknnSci%2Fsrzgxdc.png?alt=media\&token=f3a4ba9c-d665-4971-a5e5-7b0cca271f68)

Use explicit workflow parameters when you want the required input to be clear. A background automation cannot rely on the selected row of an open component.

## Use an input in a condition

Parameters can also supply rule conditions. The following existing example compares a transaction amount; for Tickets, compare a priority or status value that exists in your source.

![](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2FbNepeHI8FgbY2K3odsFY%2Fzfdxrc.png?alt=media\&token=90284c15-dc58-4d8e-b749-87cc6f327b67)

## Check the result

Run the workflow with two different IDs and inspect the input received by the action. Test missing inputs separately and prevent an update when a required identifier is absent.

If the wrong record changes, inspect both the button binding and the action's ID field. If the operation rejects the value, compare the parameter type with the source ID type.

Next: [Use step outputs and return results](/workflow/build-workflow-steps/use-step-outputs-and-return-results.md).


---

# 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.jetadmin.io/workflow/build-workflow-steps/pass-inputs-into-a-workflow.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.