n8n integration

Video demo

See how to turn an n8n workflow into a paid API using Tollara.

Backend operations (seller)

Use these when n8n is the service backend (proxied webhook or non-proxied API). Add Tollara, pick Resource Authentication, then pair with a standard n8n Webhook.

• Authentication → Verify Request — After a Webhook: verify gateway HMAC and subscription access. Emits tollaraOk; branch with IF. Enable Raw Body on the Webhook.
• Authentication → Validate Key — Validate a caller's service key (typical non-proxied pattern). Branch on tollaraOk; infra failures set tollaraBranch === 'error'.
• Usage → Estimate Usage — After auth: check whether the caller has quota/cap for N units before expensive work (wouldAllow, estimated cost).
• Async Callback → Report Progress — Send async job progress to the progressUrl from the gateway invoke response.
• Async Callback → Complete — Send async completion to the callbackUrl from the gateway invoke response.
• Usage → Report Usage — Report billable units to the Usage API (non-proxied backends).

Typical proxied async: Webhook → Tollara (Verify Request) → IF tollaraOk → [logic] → Progress → Complete. Typical non-proxied: Webhook → Tollara (Validate Key) → IF tollaraOk → [logic] → Report Usage.

Subscriber operations (buyer)

Use these when your workflow consumes a Tollara listing (you hold a service key for that product).

• Invocation → Invoke — Call a listed endpoint (sync or async) via the gateway /api/service/{serviceId}/endpoint/{endpointId}/invoke. Set service key, service ID, and endpoint ID on the node.
• Usage → Estimate Usage — Optional pre-invoke check: would this call be allowed for N units, and what is the estimated cost? Branch on wouldAllow before Invoke.
• Job → Get Status — Poll async job status by requestId.
• Job → Get Result — Fetch async job result by requestId.

Typical async subscriber: Invoke (async) → Get Status → Get Result.

Install

Self-hosted n8n only (Community Nodes must be enabled). n8n Cloud may block unverified community packages. Open Settings → Community nodes → install n8n-nodes-tollara, then search the node picker for Tollara. Source and build steps live in the tollara-sdk monorepo (integration-n8n/). The package bundles @tollara/service-sdk at build time — no separate SDK install is required in n8n.

Demo workflow JSON ships in the npm package under example-workflows/ (for example ~/.n8n/nodes/node_modules/n8n-nodes-tollara/example-workflows/). Import via Workflow menu → Import from File and replace YOUR_* placeholders before activating.

Configuration

An optional Tollara API credential can store Service Secret and Service Key (credential field apiKey). You can also set those values on each node. For non-production hosts, enable Set API Endpoints on nodes that call Tollara APIs and override gateway, core, and usage base URLs. Production defaults are used when that option is left off.

First workflow

For a proxied listing: add a Webhook (enable Raw Body), connect Tollara (Authentication / Verify Request), branch on tollaraOk, run your logic, then respond. Point the service endpoint backend URL at the Webhook's production URL when listing on tollara.ai. For async backends, add Progress and Complete against the URLs from the invoke response. To call another listing from n8n, use Invocation / Invoke (and Job / Get Status / Get Result for async).