Tollara icon

Tollara

Tollara marketplace operations: authenticate requests, invoke services, manage async jobs, and report usage

Actions9

Authentication → Verify Request

AI-generated

Summary

Verify a Tollara HMAC signature and subscription access on incoming webhook items using the configured service secret and optional raw body binary data for HMAC validation.

Inputs

  • Service Secret — Secret for this Tollara service used to verify the HMAC signature; set per node when multiple services are used.
  • Raw Body Binary Property — Name of the binary property from the Webhook node that contains the raw body, used for generating the exact payload for HMAC verification when the Webhook node raw body option is enabled (default: 'data').

Output shape

a list of items matching the input; each item JSON augmented with verification result fields

For each input item, returns an output item with JSON containing 'tollaraOk' (boolean), 'userContext' (object with user and subscription details if verified), or error fields like 'tollaraErrorCode' and 'tollaraErrorMessage' if verification fails. Items with invalid HMAC signatures or insufficient subscription access are flagged accordingly for branching.

Examples

Example 1: Use after an n8n Webhook node with raw body enabled to verify Tollara signature and subscription.

Set 'Service Secret' to your Tollara service secret and 'Raw Body Binary Property' to the binary property name that holds the raw webhook body (default 'data'). Connect the output to nodes that branch on 'tollaraOk'. The node verifies the HMAC from headers against the reconstructed payload and includes user subscription info in output.

Links

Discussion