Frigate Trigger icon

Frigate Trigger

Starts a workflow when Frigate publishes a matching /ws event

Frigate Trigger

AI-generated

Summary

Listens to a selected Frigate WebSocket topic and starts the workflow when a matching message arrives. Choose a built-in event or subscribe to a custom topic; optional filters such as camera, object, zone, audio type, role, or model name narrow the topic pattern.

Inputs

  • Event (required) — Select the Frigate topic to monitor. Defaults to tracked object events; choices also include reviews, statistics, camera status and counts, audio events, motion, and other state changes, or a custom topic.
  • Custom Topic (required) — Shown for a custom subscription. Enter an exact topic or a pattern using MQTT-style + and # wildcards; omit the frigate/ prefix.
  • Camera — For camera-scoped topics, provide a camera name. Leave blank to match any camera.
  • Object — For object-count topics, provide an object type such as person. Leave blank to match any object.
  • Zone — For zone-count topics, provide a zone name. Leave blank to match any zone.
  • Audio Type — For audio-type topics, provide a type such as speech. Leave blank to match any audio type.
  • Role — For camera role-status topics, provide a stream role such as detect. Leave blank to match any role.
  • Model Name — For classification-result topics, provide a model name. Leave blank to match any model.

Output shape

One n8n item per matching WebSocket message, emitted as the event arrives.

Each item contains json.topic, json.payload, and json.raw. String payloads that contain JSON are parsed when possible. Binary messages are attached as binary.data when supported, otherwise their base64 content is placed in json.binaryBase64. Requires Frigate API credentials and maintains a persistent WebSocket connection with automatic reconnection.

Links

Discussion