Pass data between actions in a flow
When you build a flow in Cloud Automation, some actions produce an entity as output. For example, the Start Jira sprint action produces a sprint. Other actions, however, need a specific entity as input. For example, Add work item to sprint needs a sprint to act on.
To understand how these work, imagine a flow where Start Jira sprint runs first, followed by Add work item to sprint. The first action produces a sprint as its output. You can pass that sprint directly to the Sprint field in the second action using a smart value — no manual ID lookup needed.
You can validate your inputs as you configure each action, so you can catch mismatches before your flow goes live.
はじめる前に
Make sure the actions in your flow are ordered so that the action producing an entity comes before the action that needs it as input.
Pass valid data between actions
To pass the output of one action to another in a flow:
If you’re not already there, navigate to Studio, then Automations, or select Automations from your Jira or Confluence space.
Open the automation flow you’d like to edit.
Select the action that needs an entity as input.
In the action's configuration panel, find the field that expects an entity.
Select a smart value that references the output of an earlier action. Only smart values that match the required entity type for that field will show.
To validate your input, go to More actions (), then select Check for errors.
Once your field is validated, select Save and enable.
At runtime, the flow automatically extracts the correct identifier from the earlier action's output and passes it to the next action.
How action inputs are validated
Each action that produces an entity declares what type of entity it outputs. When you configure a field that expects a specific entity type, a validation runs to check your input against that requirement.
Enter a smart value in the field. Here’s what’s accepted:
Smart values with a matching entity type. Only smart values that reference the correct entity type are shown as available in the field.
Smart values without type information, but these aren’t guaranteed to work. Native automation smart values and smart values from actions that haven't declared an entity type pass validation, but they might not produce the right entity at runtime.
If your input doesn't meet these requirements, you’ll receive an inline error.
Example errors and solutions
Enter a valid smart value. Use a smart value with the correct entity type to keep the flow dynamic.
Why? The value you entered isn't a valid smart value — it may be an incorrect format, be a plain text string, or include a “child field”.
With entity-aware fields, you use the root smart value and the flow will extract the right data automatically, no child field needed.
What to do: Replace the value with a valid smart value that references the correct entity type.
This smart value doesn't contain the specified entity. Select a smart value that outputs the correct entity.
Why? The smart value is valid, but it references the wrong type of entity for this field.
What to do: Select a smart value from an action earlier in the flow that produces the entity type this field expects.
この内容はお役に立ちましたか?