Use case · Support operations · n8n

Keep the workflow. Put refund decisions under company policy.

Your n8n automation handles the request. Talon decides whether the exact refund action can run, holds it for a human when needed, and dispatches only a valid claim. Every decision and attempt has a signed record you can inspect.

Self-hosted · Company policy + one use-case override · No replacement orchestrator required

Three outcomes, one policy

Not every requested refund should execute.

The reference example uses a company-wide upper bound and a narrower reviewer rule for the support use case. n8n branches on Talon's verdict—not on a copy of those thresholds.

01 / Allowed

€30

Policy allows the requested operation. n8n claims it; Talon dispatches to the trusted destination.

DecisionALLOW
02 / Human review

€75

A support lead reviews the bound operation. A decision alone never sends a refund; a later claim is required.

DecisionREQUIRE_APPROVAL
03 / Denied

€900

The company limit blocks the action, even if the use case attempts to loosen its own rules.

DecisionDENY

Amounts are illustrative EUR policy rules, not built-in refund logic. The runnable example uses a deterministic counting service, not a live payment processor.

Inspect it in the Operations Console

See the rule, the reviewer queue and the signed attempt.

The console is a read-only projection of the same decisions and evidence available to the CLI. These images come from Talon's synthetic action-and-approval fixture.

Explore the console →

How it works

n8n orchestrates. Talon authorizes and dispatches.

01

Register the AI use case

Run talon agents add, receive its key, connect the importable workflow and configure the exact action under company and use-case policy.

02

Decide or request approval

Talon binds the operation and typed arguments. Reviewers have their own credentials and can approve or reject requests in the CLI or reviewer API.

03

Claim and verify

n8n claims the authorized operation. Talon dispatches to the business adapter and records decision, review, attempt and outcome in verifiable evidence.

Follow the complete operator walkthrough →

Operate and investigate

A reviewer decision is not a business effect.

Effective policy

Know which rule fired

Inspect the composed company and use-case action policy with rule provenance. Typed argument rules decide the requested amount.

Separate identity

Keep approvers distinct

The n8n webhook trigger credential, use-case key, reviewer credential and operator admin key have different authority. The use-case key cannot approve.

Signed lifecycle

Show what Talon did

Investigate the operation, approval and attempt. Verify the signed lifecycle and compare it with the destination's own result.

This is the HTTP Action Gateway path. MCP tool permission checks do not inherit its exact-operation approval/claim guarantees. Direct calls that bypass Talon remain outside its control.

Reproduce the proof

Three test inputs. Inspect the decision and the actual attempt.

Import the workflow, run the sample requests, make a reviewer decision and check Talon's signed operation lifecycle against the counting adapter.

Bring your own workflow

Which business action needs an approval boundary?

Start with a refund, account change, deployment or external message. Keep the orchestrator; route the consequential action through Talon.