Role Routing
AI-generatedSummary
Route input items based on matching roles in a given task, sending matched items to corresponding outputs or proxying data to configured URLs; unmatched or error items are routed to separate outputs.
Inputs
- task (required) — The Pyrus task object in which role calls are checked to identify matching roles.
- roles (required) — A collection of roles to check against the task. For each role, specify the role name, enable proxy if needed, the proxy URL, and optional proxy headers and query parameters.
Output shape
Multiple main outputs equal to the number of configured roles (including separate outputs for proxy-enabled roles), plus one for 'No Match', and one for 'Error'.
Items matching each role are sent to that role's output with an added roleId in the item body. If proxying is enabled for a role, data is sent by HTTP POST to the configured URL with optional headers and query parameters. Items that do not match any role are sent to the 'No Match' output. Errors encountered during matching or proxying are routed to the 'Error' output with error details in the json.