Description

n8n Community Nodes – Tollara

Single n8n action node for Tollara: verify inbound gateway traffic, invoke listed services, poll async jobs, and report usage.

Package: n8n-nodes-tollara (bundles @tollara/service-sdk at build time — no separate install)

Install in n8n

Self-hosted n8n only (Community Nodes must be enabled). n8n Cloud may block unverified community packages.

1. Open Settings → Community Nodes.
2. Install n8n-nodes-tollara.
3. Search the node picker for Tollara.

Add one Tollara node, then choose Resource and Operation. Set Service Secret (and other fields) on the node, or optionally attach a Tollara API credential.

Node: Tollara

Tollara integrations fall into two roles:

• Backend (seller) — your n8n workflow receives traffic from the Tollara gateway (Webhook) or validates direct callers, then runs your logic and reports usage or async progress.
• Subscriber (buyer) — your workflow calls another party’s listed service via the gateway (invoke, estimate, poll async jobs).

The package registers one regular node (n8n-nodes-tollara.tollara) with a single main output. Auth operations emit tollaraOk (and related fields); branch with IF / Switch.

| Resource | Operation | Purpose |
|———-|———–|———|
| Authentication | Verify Request | After a Webhook: verify gateway HMAC and subscription access. Emits tollaraOk, userContext, or tollaraErrorCode / tollaraHttpStatus. Enable Raw Body on the Webhook. |
| Authentication | Validate Key | Validate a caller’s service key (typical non-proxied pattern). Branch on tollaraOk; for infra failures use tollaraBranch === 'error' (else denied). |
| Invocation | Invoke | Call a listed endpoint (sync or async). Emits tollaraOk, statusCode, parsed data, and async requestId / URLs when applicable. |
| Job | Get Status | Poll async job status by requestId. |
| Job | Get Result | Fetch async job result by requestId. |
| 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 | Estimate Usage | Check whether the caller has quota/cap for N units (wouldAllow, estimatedCost, breakdown). Branch before expensive work or Invoke. |
| Usage | Report Usage | Report billable units to the Usage API (non-proxied backends). |

Typical proxied async backend: Webhook → Tollara (Authentication / Verify Request) → IF tollaraOk → [your logic] → Tollara (Async Callback / Report Progress) → [your logic] → Tollara (Async Callback / Complete)

Typical non-proxied backend: Webhook → Tollara (Authentication / Validate Key) → IF tollaraOk → [your logic] → Tollara (Usage / Report Usage)

Typical async subscriber: Tollara (Invocation / Invoke, async) → Tollara (Job / Get Status) → Tollara (Job / Get Result)

Optional pre-check: Tollara (Usage / Estimate Usage) → IF wouldAllow → Tollara (Invocation / Invoke) (see subscriber-proxied-sync-agent-estimate.json)

Set Service Key, Service ID, and Endpoint ID on Invoke (from the listing in the Tollara app). Job Status/Result only need the service key and request ID.

Example workflows

Demo workflow JSON files are bundled in the npm package (generic templates with YOUR_* placeholders — not the maintainer local/ folder).

After installing n8n-nodes-tollara, import from:

| Install context | Path |
|—————–|——|
| n8n Community Nodes (typical self-hosted) | ~/.n8n/nodes/node_modules/n8n-nodes-tollara/example-workflows/ |
| Windows (Community Nodes) | %USERPROFILE%.n8nnodesnode_modulesn8n-nodes-tollaraexample-workflows |
| npm dependency in a project | node_modules/n8n-nodes-tollara/example-workflows/ |

Use n8n Workflow menu → Import from File and pick a .json file from that folder. Replace YOURSERVICESECRET, YOURSERVICEKEY, and other placeholders before activating. See example-workflows/README.md in the same directory for setup notes.

| Workflow | Role |
|———-|——|
| backend-url-metadata-sync.json | Backend — proxied sync |
| backend-topic-brief-async.json | Backend — proxied async |
| backend-echo-non-proxied.json | Backend — non-proxied |
| subscriber-proxied-sync-agent.json | Subscriber — proxied sync |
| subscriber-proxied-sync-agent-estimate.json | Subscriber — estimate + invoke |
| subscriber-proxied-async-agent.json | Subscriber — async + poll |
| subscriber-non-proxied-sync-agent.json | Subscriber — direct HTTP (no gateway invoke) |

Point your listing realUrl (backend) or subscriber Set Config values at your n8n or agent URLs as described in each workflow’s sticky notes and the bundled example-workflows/README.md.

API endpoints

Leave Set API Endpoints disabled on each node for production Tollara.

For custom deployments, enable Set API Endpoints and set the validation, invoke, and usage reporting URLs for your environment.

Set Service Secret and Service ID on each node where those fields appear (or use a Tollara API credential). The credential’s masked key field is named apiKey internally (display name Service Key); the Tollara API still receives serviceKey.

Developing this package

Maintainers: build, test, Docker-based local n8n, and e2e fixture workflows are documented in LOCAL-DEVELOPMENT.md.