Pass Through

A structural placeholder that passes its input straight through.

Pass Through does nothing to your data, on purpose. It receives input and returns it unchanged.

Its value is structural. Complex workflows fork, and those forks have to rejoin somewhere. A Pass Through gives divergent paths a single, named place to converge — which makes the workflow readable to whoever inherits it.

How it works

• Input resolution — $input receives the aggregated output of every preceding step that transitions into it. $secret can be referenced, but the skill doesn't use secrets for its own work.

• Processing — none. The input is returned as-is, unmodified and unvalidated.

• Execution — blocking. It completes before the workflow proceeds.

• Response — success returns the input as the output. Failure is unlikely, since there's no logic to fail; an internal system error would produce a 500.

Worked example: merging divergent paths

Configuration:

{
  "name": "Merge Property Details",
  "description": "Combines details from different property collection paths."
}

Input, from the preceding steps:

{
  "propertyType": "Residential",
  "address": "123 Main St",
  "ownerDetails": {
    "name": "Jane Doe",
    "contact": "[email protected]"
  }
}

Output — identical:

{
  "propertyType": "Residential",
  "address": "123 Main St",
  "ownerDetails": {
    "name": "Jane Doe",
    "contact": "[email protected]"
  }
}

Note the name and description. They're the entire point: this skill's only lasting contribution is that the workflow now says Merge Property Details at the junction where three paths meet, instead of nothing.

The Pass Through skill as a workflow conjunction point

Configuration reference

Field	Type	Required	Description
name	string	—	Name for this Pass Through instance.
description	string	—	Description for this Pass Through instance.

Both are optional and neither affects behavior — but a Pass Through without a name is a junction with no explanation, which defeats the reason for adding one.

Configuring Pass Through with an optional name and description

Output

Dynamic: the output schema mirrors whatever came in. The skill doesn't modify the data, so the output is an exact copy.

Errors

Status	Cause
500	An unexpected runtime failure in the execution environment.

Missing input and misconfiguration are not errors here — the skill is designed to pass through whatever it receives.

Security

Input and output are not redacted. Whatever passes through appears as it arrived. Don't route sensitive data through this skill unless that's intended and handled elsewhere — for example by PII Guard upstream or downstream.

• The skill does not use $secret for its own functionality.

• Data is processed in memory and is not persisted by the skill.

Testing in isolation

• Path — /skill-runtime/workflows/nodes/PassThrough/execute

• Method — POST

• Body:

{
  "config": { "name": "Placeholder Node", "description": "For better workflow structure" },
  "input":  { "userId": 12345, "status": "active" }
}

---

To add this skill to an agent, see Adding a Skill to the Agent.