Input Mapping and Workflow References

Purpose

Pass data from the trigger or from previous tasks into later task inputs. Use references instead of hard-coding when the value comes from an earlier step.

Reference syntax

• $trigger.<triggerId>.<fieldKey> – Value from the trigger's inputs. Replace triggerId with the trigger's ID and fieldKey with the input key.
• $task.<taskId>.outputs.<fieldKey> – Value from a previous task's outputs. Replace taskId with the task's ID and fieldKey with the output key.

Where to use

Use these references in any task input that supports mapping: AI model prompts, platform tool inputs, template placeholders, condition operands, and code inputs. The workflow builder often provides a picker for trigger and task outputs; the stored value is one of these reference strings.

Tips

• Ensure the referenced task runs before the current task (respect execution order).
• In parallel branches, you can reference outputs of sibling branches that have already completed.
• If a reference cannot be resolved at runtime (e.g. wrong ID or missing output), the run may fail or use an empty value; double-check IDs in the builder.

For code-task placeholders (for example {{$trigger.user.email}} and {{$task.someTask.outputs.result}}) and custom value examples, see Code Task Placeholders and Custom Values.