GlobiGuard Action Gate icon

GlobiGuard Action Gate

Route a proposed action by policy; use a governed executor for an actual side effect

Actions2

Reauthorize After Approval

AI-generated

Summary

Check the approval queue entry, then request a fresh policy decision for the current input item when it is approved. Approval does not authorize a downstream side effect; route the result by its decision and use a governed executor for any action.

Inputs

  • Queue Entry ID (required) — ID of the approval queue entry created by an earlier QUEUE decision.
  • Action Type (required) — Stable verb for the downstream side effect, such as email.send or database.write.
  • Destination Type — Destination category: CRM, custom, database, email, Slack, storage, ticketing, or webhook.
  • Destination Name (required) — Stable logical destination name; do not use a secret or full payload value.
  • Destination Resource — Optional logical resource, table, channel, or device group affected.
  • Data Classes — Sensitivity classes present in the action payload; defaults to INTERNAL. Use GlobiGuard Detect upstream when unknown.
  • Purpose — Business purpose evaluated by purpose-limitation policies.
  • Workflow Run ID — Execution identifier for evidence correlation; defaults to the n8n execution ID.
  • Workflow Step ID — Step identifier for evidence correlation; defaults to the node name.
  • Correlation ID — Optional end-to-end correlation identifier.
  • Idempotency Key — Recommended for side effects; use a stable business key that survives workflow retries.

Output shape

Routes each input item to one of five outputs: allow, modified, blocked, queued, or error.

For approved or auto-approved entries, sends the current item’s payload summary and configured action context to the authorization API for a fresh decision. Pending or escalated entries route to queued; rejected, expired, failed, or already resumed entries route to blocked. A reviewer-modified entry routes to modified with the reviewed summary; apply that change to the authoritative payload and authorize it separately. Each routed item retains its input JSON and gains a globiguard object with decision and authorization metadata. This node does not execute the side effect. Errors normally stop execution; with Continue On Fail enabled, they route to error.

Links

Discussion