spurvik

Designed to support Article 50 interaction notices, and Article 12 HMAC-SHA256 record-keeping and Article 14 human approval requests for high-risk AI systems, for n8n, with optional console.spurvik.com sync. Channels: Slack, Telegram, Email (Resend), Disc

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 1.0.5
Author: EyeTea Solutions ApS

Documentation

n8n-nodes-spurvik

n8n community node designed to support four separate workflow steps:

  1. Add an AI interaction notice to one text field.
  2. Record the call as an HMAC-SHA256 digest instead of the raw prompt text. The digest is spurvik:workflow:input:v1| plus the input field. This is designed to support Article 12 record-keeping for high-risk AI systems. The notice operation reads outputField (default outputText) and inputField (default promptText). inputField is shown for the notice and the digest. It throws if outputField is missing or is not a string, if outputField equals inputField in any letter case, or if outputField matches promptText, prompt, chatInput, query, or input in any letter case. It does not read the prompt field. Output is { spurvik: result } plus explicitly named fields other than those prompt names. Those prompt names and the configured inputField are never copied (name check only, any letter case). The field value is not returned, including when that name is listed in passThroughFields. The digest is HMAC-SHA256 of the prefix spurvik:workflow:input:v1| plus the input field.
  3. Send an ask_human() approval request. This is designed to support Article 14 human oversight for high-risk AI systems.
  4. Scan a live client site for AI chat widgets and an Art. 50 notice, with no API key. See Scan Live Domain.

The node does not mark content. Using it does not by itself mean anyone meets the AI Act.

n8n keeps each node's input and output on the execution. The Spurvik node output does not copy prompt text, but the incoming item is still that node's input. Set the instance's execution data retention yourself: EXECUTIONS_DATA_SAVE_ON_SUCCESS, EXECUTIONS_DATA_SAVE_ON_ERROR, EXECUTIONS_DATA_SAVE_MANUAL_EXECUTIONS, EXECUTIONS_DATA_PRUNE, EXECUTIONS_DATA_MAX_AGE, and EXECUTIONS_DATA_PRUNE_MAX_COUNT. n8n's execution history keeps those inputs and outputs until you change those retention settings.

Channels

Slack, Telegram, Email (Resend), Discord, Microsoft Teams, Linear, Jira, Monday.com, and Asana.

Monday.com only creates a board item. It does not send Approve or Block links.

Slack, Discord, and Teams use a webhook credential. The other channels use an approver target (chat id, email recipient, team id, project key, board id, or project gid) plus the matching token on the spurvikApi credential.

callbackBaseUrl is required for an approval request. Pass a URL that accepts GET clicks. By default (when consoleApiKey is left empty), the notice, digest, and approval operations run locally without calling the Spurvik HTTP API; setting consoleApiKey on the spurvikApi credential enables optional sync to consoleBaseUrl (https://console.spurvik.com by default). Scan Live Domain is the one operation that always calls consoleBaseUrl, and it sends only a hostname.

Scan Live Domain (Art. 50 & Client Brief)

Operation value scanDomain. It needs no credential and no API key: n8n hides the spurvikApi credential for this operation, the node does not read it, and the request carries no Authorization header. Drop the node into a workflow, set Domain or URL, and run it.

  • Domain or URL (domainOrUrl, required): a bare domain (stepnetwork.dk) or an http(s) URL (https://Www.StepNetwork.dk/path?x=1 becomes www.stepnetwork.dk). Only the lower-case hostname is used. The node refuses localhost and *.localhost, IPv4 and IPv6 literals (including decimal, hex, and octal forms such as 2130706433 or 0x7f000001), .local, .internal, .lan, .home.arpa, single-label hosts, user@host, non-default ports, and labels outside a-z, 0-9, and -. Those inputs stop the node with an error before any request is made. Punycode (xn--) hosts are fine.
  • Console Base URL (consoleBaseUrl, default https://console.spurvik.com): the node calls GET {consoleBaseUrl}/api/v1/sandbox/scan?url=<host> with an 8 second timeout and refuses redirects. It must use https:// (http:// is allowed only for localhost testing).

If the console cannot be reached, times out, answers with a non-2xx status or invalid JSON, or returns ok: false, the node does not fail the workflow. It returns reachable: false, empty lists, art50NoticeDetected: false, scanStatus: "offline", and a short reason code (timeout, network_error, upstream_http_503, ...), with every link still filled in. The error text and the response body are never copied to the output.

The output item holds only the scan. Nothing from the incoming item is copied, and passThroughFields does not apply. Example for stepnetwork.dk:

{
  "domain": "stepnetwork.dk",
  "reachable": true,
  "detectedWidgets": [],
  "detectedSdks": [],
  "art50NoticeDetected": false,
  "badgeSnippet": "<script src=\"https://spurvik.com/badge.js\" data-system=\"stepnetwork.dk\" data-locale=\"da\" data-theme=\"dark\" data-attribution=\"true\" defer></script>",
  "reportUrl": "https://console.spurvik.com/report?domain=stepnetwork.dk",
  "sandboxUrl": "https://console.spurvik.com/sandbox?scan=stepnetwork.dk",
  "agencyCalculatorUrl": "https://spurvik.com/eu-ai-act-for-agencies",
  "upgradeUrls": {
    "proWhiteLabelEur19": "https://console.spurvik.com/signup?plan=pro&appUrl=stepnetwork.dk",
    "teamAgencyEur79": "https://console.spurvik.com/signup?plan=team&appUrl=stepnetwork.dk",
    "doneForYou24hEur199": "https://console.spurvik.com/signup?plan=concierge&appUrl=stepnetwork.dk"
  },
  "scanStatus": "not_measured",
  "reason": "no_ai_surface",
  "markers": {
    "art50_1_disclosure": false,
    "art50_2_provenance": false,
    "art50_4_synthetic": false,
    "art12_telemetry": false
  }
}
  • art50NoticeDetected is markers.art50_1_disclosure from the console scan. It is false when the page could not be read.
  • detectedWidgets and detectedSdks are strings only, at most 20 each.
  • badgeSnippet is the same badge.js tag the MCP server's scan tool returns: the host as data-system, a locale from the country-code TLD (.dk gives da, otherwise en), dark theme, and the free "Art. 50 · Spurvik" attribution link. Paste it before </body>.
  • reportUrl and sandboxUrl are shareable client-brief links. upgradeUrls open console signup with the domain prefilled (appUrl): Pro €19/mo (white-label badge), Team €79/mo (for agencies), and Done-For-You €199 once (24h setup). Prices excl. VAT, B2B only.
  • agencyCalculatorUrl links the EU AI Act calculator for agencies.

The scan is a heuristic check of one public page. It can miss a widget or a notice that loads later.

Credential

spurvikApi stores the HMAC signing secret, optional consoleApiKey, and channel tokens as password fields. Scan Live Domain does not use it. The node reads the secret only from that credential. It throws if the secret is missing, shorter than 16 characters, or padded with whitespace. It does not read SPURVIK_HMAC_SECRET.

Layout

n8n loads:

  • dist/nodes/SpurvikEuAiActGuard/SpurvikEuAiActGuard.node.js (class SpurvikEuAiActGuard)
  • dist/credentials/SpurvikApi.credentials.js (class SpurvikApi, credential name spurvikApi)

The node type id stays spurvikEuAiActGuard, the same id as 1.0.1.

dist/index.js still exports executeSpurvikWorkflowStep, SpurvikN8nNodeDescription, and SpurvikEuAiActGuard.

Make.com

make-com-blueprint.json in this repository posts actionName and payloadSummary to the hosted HITL create route. The bearer token in the file is {{var.organization.spurvikApiKey}}. Make organization variables and scenario inputs are plain text, not secret storage. Make's custom-variables page states that organization variables need Make Pro, Teams, or Enterprise, and that the values are stored in plain text and are not for secrets. The Make API organizations reference states that creating an organization variable returns 404 when the organization license does not include customVariables. This blueprint has not been test-imported in Make. The {{var.input.spurvikApiKey}} option needs scenario inputs (Pro+ and on-demand scheduling). A webhook-triggered blueprint is not started with scenario inputs, so that mapping likely won't work there. Make's scenario-input page shows the scenario editor inserts {{var.input.<name>}} for a scenario input. Enabling inputs requires on-demand scheduling; the scenario update API returns 422 (IM016) otherwise, and an older sentence on that page still says Pro or higher, while a later Make release note says scenario inputs were opened to all plans. For production, use a Make keychain or connection. Do not map the API key from the webhook payload. Free workspaces sign up at https://console.spurvik.com/signup; paid plans (Pro €19/mo · Team €79/mo, excl. VAT · B2B only) upgrade through Stripe Checkout.

Discussion