HumanStep Trigger icon

HumanStep Trigger

Triggers when a decision is resolved in HumanStep

HumanStep Trigger

AI-generated

Summary

Starts a workflow when a HumanStep decision is resolved by registering a webhook in HumanStep that points at the node's n8n webhook URL. Optionally restricts runs to one template or one category.

Inputs

  • event — Event to listen for. Only 'Decision Resolved' (decision.resolved) is available, and it is the default.
  • useTemplate — Turn on to filter by a specific review template. Default false.
  • templateId (required) — Template to filter on, chosen from a searchable list of active templates or entered by ID. Shown and required only when Use Template is on. Decisions whose template_id differs are ignored.
  • useCategory — Turn on to filter by category. Shown only when Use Template is off. Default false.
  • categoryId (required) — Category to filter on, chosen from a searchable list or entered by ID. Required when Use Category is on. Decisions whose category_id differs are ignored.
  • waitForRealData — When off (default), a sample test payload is requested from HumanStep right after the webhook is registered. When on, the node waits for a real event instead.

Output shape

One workflow item per received webhook POST. The item's JSON is the full request body sent by HumanStep, typically including the decision object.

Requires HumanStep API credentials, and n8n must be reachable from the internet. On activation the node creates a HumanStep webhook (named n8n-trigger-) and deletes it on deactivation. The template and category filters are checked on each incoming event. Non-matching events produce no output and do not start the workflow. The sample test delivery is best-effort, and failures are silently ignored. Template and category filters are also sent to HumanStep when the webhook is created. Template takes precedence over category.

Examples

Example 1: Run a follow-up whenever any decision is resolved

Event: Decision Resolved; Use Template off; Use Category off. Activate the workflow.

Example 2: React only to decisions from one review template

Use Template on; Templates: pick from list or enter the template ID.

Example 3: Receive a real event instead of a sample while testing

Set Wait for Real Data on, click Execute step, then resolve a decision in HumanStep.

Links

Discussion