ClearedBy GateInstall

Summary

Evaluate each incoming item against a ClearedBy policy for the required action, then pass, route, stop, or pause the workflow according to the verdict and selected mode.

Inputs

• Action (required) — Action identifier to evaluate, such as refund.create.
• Payload — Send all incoming item JSON as action parameters (default), or choose Selected Fields and provide comma-separated field names. Selected fields are read from the top level of the item JSON.
• Policy Name or ID — Select a policy or leave blank to use the organization default.
• Mode — Shadow records the policy result and continues on Cleared; Enforce can pause the workflow for human review.
• Summary — Optional one-line context sent for the human reviewer.
• Timeout Override (Seconds) — Optional positive number of seconds to override the policy review deadline; 0 uses the policy default.
• On Reject — For rejected results, route to the Rejected / Expired output (default), stop with an error, or continue on Cleared with clearedby.cleared set to false.

Output shape

Two outputs: Cleared and Rejected / Expired. Each emitted item retains its original JSON and gains a clearedby object containing the verdict ID, status, decision maker, rule, reason, attestation hash, and shadow/sampled flags.

Cleared verdicts go to the first output. In Enforce mode, pending items pause until ClearedBy posts a decision; cleared decisions resume on the first output, while rejected or expired decisions follow the configured rejection handling. In Shadow mode, the API records the result without pausing. A request error stops the node with an operation error.

Links

• n8n community nodes installation guide