← API Documentation
n8n template
Tested on n8n Cloud, real Slack and EVIDE with a test identity

Human approvals of AI agent actions, recorded in EVIDE

An agent proposes, an authorized person decides in Slack, and EVIDE keeps, outside the system, the declaration of what was proposed, who decided and when.
n8n 2.32.0 or later · Slack · OpenAI or another model · EVIDE Schema 2.1 · November 2026
n8n runs the workflow.
Slack collects the answer.
EVIDE keeps, outside the system, two linked and verifiable records: the escalation and the declared outcome of the human review.
The template connects an AI agent built in n8n to a human approval in Slack. For each approval request the workflow attempts two EVIDE deposits: the linked pair exists when both are confirmed. The action branch is enabled only after an approval from an authorized person. The action nodes are placeholders to replace: the template does not perform concrete operational actions.
Section 1
1. The problem

An AI agent proposes an action: a refund, a change to an order, a message to send. Before it runs, a person approves or declines it. n8n already does this.

The problem comes later, weeks or months on, when someone asks: what exactly did the agent propose? Who approved it? When? Did the action run without approval?

n8n execution data can be deleted according to the retention policy configured in the n8n instance, and it stays under the control of whoever runs the workflow. The Slack message can be edited or deleted. Answering those questions takes records kept outside the system that acted, with a receipt time assigned by EVIDE, not by the workflow.

The agent proposes. An authorized person decides.
EVIDE keeps the declaration of both moments.
Section 2
2. How it works
1
The agent proposes an action
A chat message reaches an AI agent, which proposes a single action in a structured format. The agent has no tools that act: it can only propose.
2
A fixed rule decides whether a person is needed
The model does not decide this. By default every action needs approval. Exemptions are explicit and apply only to actions without an amount.
3
The chat answers at once
The approval runs in a separate execution. The user is told straight away that the request is waiting for review, not approved, and that no action has been taken.
4
The workflow deposits the escalation in EVIDE
The first deposit contains the rule that was applied and the SHA-256 fingerprint of the agent output. The fingerprint identifies the output but does not contain it: the complete original output stays in n8n execution data and is not sent to EVIDE.
5
An authorized person answers in Slack
The message has Approve and Decline buttons. Only Slack accounts in the approver list can answer; clicks from other accounts are ignored. If nobody answers within the configured time, the request closes and a notice appears in Slack.
6
The workflow deposits the outcome in EVIDE
If both deposits are confirmed, the second record is linked to the first: same matter, position 2 in the chain.
7
The action branch is enabled only after an authorized approval
Every other outcome goes to the «Do not run the action» branch. An EVIDE deposit that is not confirmed alerts the operator in Slack: it does not approve, decline or block the decision.
The action nodes are placeholders. «Run approved action (replace me)» and «Run exempt action (replace me)» do nothing. The template takes the request up to the point where the action can run, but the operational action (a refund, an order update, a message) has to be built by you in place of those nodes, with its own error handling.
The template open in the n8n editor
The template open in n8n: the yellow note summarizes how it works and how to set it up, the white notes describe the six stages. Click the image to open it at full size.
Section 3
3. What EVIDE records

For each approval request the workflow attempts two deposits, linked with chain.parent_evide_id.

Escalation (position 1)Outcome (position 2)
WhenAs soon as the rule requires approvalAfter the answer in Slack or the wait limit
TitleShort and fixed, for example «Escalated for approval: refund 40 EUR»For example «Approved via Slack: refund 40 EUR»
ContentChecked action type, amount, rule reasons, SHA-256 fingerprint of the agent output, references to the n8n executionOutcome, Slack member ID of the authorized approver, channel and message IDs, declared uncertainties
Agent outputNot in the record. EVIDE keeps only the fingerprint; the complete original output stays in n8n execution data.
Verified identityThe DAPI of the API key holder. The approver is a Slack account reported by Slack to n8n.

The linked pair of records exists only when EVIDE confirms both deposits. If a deposit is not confirmed, the operator gets an alert in Slack with the error:

  • if the escalation is not confirmed, the workflow still attempts the outcome deposit, which may fail as well; if it succeeds, the outcome is recorded without a link and the record states this among its uncertainties;
  • if the outcome is not confirmed, the decision taken in Slack does not change, but EVIDE holds only the escalation.
What is not sent to EVIDE: the agent output, text written by the model, chat messages, the approver's name or email, credentials. EVIDE receives only checked values, fixed sentences and the fingerprint.
Section 4
4. The five possible outcomes
OutcomeWhenAction branch
approvedApprove from an account in the authorized listyes
declinedDecline from an account in the authorized listno
approval_not_acceptedApprove that cannot be attributed to an authorized accountno
decline_not_attributedDecline that cannot be attributed to an authorized accountno
no_valid_responseWait limit reached, Slack error or unexpected answerno

For the two unattributed outcomes the record states the reason and does not contain the ID of the account that clicked.

Section 5
5. Checks that do not depend on the model
  • Fail-closed rule: if the configuration is incomplete or ambiguous, human review stays mandatory.
  • Fixed formats: action type in snake_case only, three-letter currency, numeric amount.
  • Approvers: the list is checked twice, by the Slack node and by the workflow. Only the ID of an authorized approver is sent to EVIDE.
  • Duplicates: each deposit uses an Idempotency-Key. For 7 days, new attempts with the same key and the same content receive the stored response and create no duplicate records. An execution retried after 7 days creates a new record.
  • Fingerprint: the SHA-256 is computed on the agent output exactly as it reaches the workflow, not normalized or truncated. It does not cover the model's raw text before the parser, which the workflow cannot see.
Limits of the personal data filter. In the texts shown in Slack the workflow removes fixed patterns only: email addresses, phone numbers, IBANs, payment card numbers with a Luhn check and Italian tax codes. It does not recognize names, postal addresses or other personal data written as free text, and an unusual format can slip through. The message typed in the chat stays in n8n execution data in any case. No free text from the model is sent to EVIDE, whatever the filter does.
Good to know: the Idempotency-Key protects the EVIDE deposits, not your action. If you retry an execution, n8n runs the action node again: make it idempotent using escalation_uuid.
Section 6
6. What EVIDE does not verify
  • EVIDE records what the workflow declares, with its own receipt time and integrity data.
  • It does not verify the decision, the agent output or who uses a Slack account.
  • An approval record does not show that the action was executed.
  • The fingerprint lets you check a copy of the agent output later, but it does not keep the output: the output stays in n8n execution data, which can be deleted according to the retention policy configured in the instance. If you need it, store it in your own system.
Section 7
7. Requirements
  • n8n 2.32.0 or later, self-hosted or Cloud. It is the first release with the Slack options «Capture Who Responded» and «Restrict Who Can Approve».
  • An EVIDE account with a verified DAPI identity and an API key accepted in the profile, with billing confirmed.
  • A Slack workspace where you can install an app with interactivity.
  • An OpenAI key, or another model node.
  • Your own operational action, to connect in place of the placeholder nodes.

Standard n8n nodes only, no community nodes. Each confirmed deposit is a paid EVIDE record: for each approval request the workflow attempts two. See Pricing.

Section 8
8. How to get access
1
Verify your DAPI identity
The DAPI is the verified identity of the record holder: dapi-certification.com.
2
Request API access
Write to info@certifywebcontent.com. You receive the API key and the endpoint address to enter in the template together.
3
Activate the key
Accept the key in your EVIDE profile and confirm billing. Before activation the API answers 403 client_activation_pending or 403 billing_not_confirmed.
4
Configure the template
In n8n create a Header Auth credential with the name X-API-Key and your key as the value. In the «Set up EVIDE and approval rule» node enter the endpoint, DAPI number, Slack channel and approvers, then save and publish. The SETUP.md file in the zip describes every step.
5
Connect your action
Replace the «(replace me)» nodes with your action and make it idempotent with escalation_uuid.
Want to try it before creating records? On request we send you a stand-in workflow that answers like EVIDE without depositing anything, so you can test the whole flow with real Slack and a real model.
Section 9
9. How it was tested
EnvironmentWhat was tested
n8n 2.32.0 and 2.47.7 self-hosted, with a local copy of EVIDEEvery branch: approved, declined, unauthorized click, wait limit, EVIDE unreachable, wrong DAPI, lost HTTP response with a retry and no duplicate record
Code node logic47 checks: rule, filters, fingerprint, outcomes, idempotency, chain, title length
n8n Cloud 2.47.7, real Slack, gpt-5-mini, with an EVIDE stand-in that deposits nothingThe real scenarios, including a chat closed right after sending, a click from an unauthorized account and a click after the wait limit
EVIDE in production, test identityThree complete cycles (approved, declined, expired), that is six linked records, checked in the EVIDE portal: chain, positions, DAPI and EAR

The three production cycles were run with the previous version of the template. The later changes (short titles, closing notice in Slack) were tested on n8n Cloud with the EVIDE stand-in. The downloadable version differs from the tested one only in the canvas notes, the workflow name and the endpoint left as a placeholder.

Section 10
10. Download and references

The zip contains the template to import into n8n with «Import from File» and the setup guide SETUP.md, in English. The template contains no credentials, which you create in n8n, and leaves the endpoint as a placeholder: you receive it together with the API key.

EVIDE API Documentation: app.certifywebcontent.com/docs/evide-intake-schema/

EVIDE MCP Server: app.certifywebcontent.com/docs/evide-mcp/

DAPI identity: dapi-certification.com

Pricing and service conditions: app.certifywebcontent.com/pricing

API access: info@certifywebcontent.com

Who decided what, and when.

For each approval request, two linked deposits: the escalation and the outcome.
The action branch is enabled only after an authorized approval.
The declaration stays outside the system that acted.

API access: info@certifywebcontent.com