n8n

The n8n-nodes-sightradar package adds two nodes to n8n:

• SightRadar, an action node with Collection, Face, Batch and Account resources. It is also usable as an AI Agent tool.
• SightRadar Trigger, which starts a workflow when batch photos finish or a collection deletion completes. It verifies every delivery's signature.

It is built for the event-photo workflow: index every photo after the event, then let each guest upload a selfie and email them the photos they appear in.

InstallCopy Anchor Link

OperationsCopy Anchor Link

Details that matter when you build a workflow:

• Image Source. Index, Search by Image, Register Selfie and Detect take either a public HTTPS URL that SightRadar downloads, or a Binary File from a previous node, such as a form upload (default binary field data). Compare and Batch take URLs only. Images can be up to 30 MB in JPEG, PNG, WebP, HEIC, TIFF, GIF or BMP.
• Simplify (on by default) trims Index, both searches and Register Selfie to the fields a workflow uses. Search output becomes match_count, photo_ids, matches and, when nothing matched, reason. Turn it off for the raw API response.
• Minimum Similarity and Max Matches (defaults 0.5 and 100) filter the searches. Scores are cosine similarity from 0 to 1, and no one threshold fits every use case. Start at 0.5 for gallery search, check results by hand and adjust. See Choosing a threshold.
• Idempotency Key on every Face operation. A retry under the same key is never charged twice. Reusing a key for a different request returns 409, so the key must be unique to the operation, the collection and the photo, for example {{ 'index:' + $json.collectionId + ':' + $json.photoId }}. A bare photo id collides as soon as the same photo is indexed into a second collection or also sent to Detect.
• Credits remaining. Billable Face operations add credits_remaining from the X-Credits-Remaining header.
• Batch Submit runs once for all input items, not once per item, and outputs one item per batch with its batch_id.

SightRadar TriggerCopy Anchor Link

How it registersCopy Anchor Link

When you activate the workflow, the trigger registers its Production URL with SightRadar (POST /v1/webhooks) and stores the signing secret SightRadar returns once. On deactivation it disables the endpoint. You do not create the webhook yourself.

To route a batch to the trigger, paste the trigger's Production URL into Batch → Submit → Options → Notify Webhook URL. SightRadar sends batch results only to the endpoint named on the batch. The Submit node looks up the endpoint ID for that URL, so the trigger's workflow must be active first.

Signature verificationCopy Anchor Link

Every delivery carries X-SightRadar-Timestamp and X-SightRadar-Signature. The trigger recomputes HMAC-SHA256(secret, "<timestamp>.<raw body>") over the raw body, compares it in constant time and rejects timestamps more than five minutes old. A delivery that fails gets 401 and never starts the workflow. Delivery is at least once, so the trigger also drops repeats by X-SightRadar-Idempotency-Key. The scheme is the one in batch and webhooks.

EventsCopy Anchor Link

Batch Completed is derivedCopy Anchor Link

SightRadar has no "batch finished" event; it sends one webhook per photo. The trigger works out completion itself. After each photo result it calls the free batch status endpoint, and the first delivery that finds no pending or in-progress photos fires Batch Completed. It remembers the batch so a late retry cannot fire it twice.

The catch is that if that status check fails, for example on a network blip, the event waits for the next photo's delivery. If the failure happens on the last photo, no later delivery comes and Batch Completed never fires for that batch. Two ways to cover it:

• Poll as a fallback. Add a schedule that runs Batch → Get Status on recent batch_ids and treats pending + claimed = 0 as done. Batch status is free.
• Use Photo Result and count results yourself if you need every photo in real time anyway.

Example workflowsCopy Anchor Link

Both workflows are in the package's examples/ folder. Import them with Workflows → Import from File, then attach your SightRadar and SMTP credentials.

Batch index, then notifyCopy Anchor Link

Loads an event gallery at the batch rate and emails you when indexing is done.

Activate the workflow before you run the first flow, so the trigger is registered when Submit looks up its URL.

Event selfie finderCopy Anchor Link

A guest opens a form, uploads a selfie and gets an email with every event photo they appear in.

Index the gallery first with the batch workflow, using file names as Photo IDs, then set your collection ID and base URLs.

CostsCopy Anchor Link

1 credit is $0.00001, prepaid. You are never charged for a 4xx or 5xx, and a photo with no faces is still one charge. See Billing.

For a 2,000-photo wedding with 500 guests searching once each:

Storing faceprints also costs $6 per million faces per month. If a guest searches more than once, Register Selfie (93) and then Search by Face ID (62) beats repeating Search by Image. Delete the collection when the event's purpose ends: Collection → Delete → Compliance Erasure erases it immediately and records the erasure. See deleting data.