Brixfit Trigger icon

Brixfit Trigger

Starts a workflow when a Brixfit event fires (lead created, status changed, check-in submitted, etc.)

Brixfit Trigger

AI-generated

Summary

Starts a workflow when selected Brixfit events (leads, clients, check-ins) fire. On activation it registers a signed webhook in Brixfit and verifies incoming payloads by HMAC-SHA256.

Inputs

  • events (required) — Multi-select of Brixfit events to listen for: lead.created, lead.updated, lead.status_changed, lead.converted, lead.deleted, client.created, client.updated, client.deleted, checkin.submitted. Default is lead.created. Changing it requires deactivating and reactivating the workflow, and the node re-registers the webhook if the selection differs from the stored one. Payloads for other events get a 200 response and are skipped.
  • options.requireSignature — Default true. Rejects requests whose x-brixfit-signature header is not a valid HMAC-SHA256 of the raw body. If true and no secret is available, the node throws an error. Disable only for testing.
  • options.replayWindowMinutes — Default 5 (UI allows 1–60). After the signature passes, requests whose x-brixfit-timestamp header is missing or older than this window get a 401. The description says 0 disables the check, but the UI minimum is 1.
  • options.webhookDescription — Label for the webhook in Brixfit → Developer → Webhooks. Defaults to 'Created automatically by n8n'.
  • options.webhookSecret — Manual signing secret, used only if no auto-registered secret is stored. Normally left blank.

Output shape

One item per accepted webhook call. The payload's data object is flattened to the top level, plus _event, _timestamp and _coach_id (null if absent).

The webhook responds immediately (onReceived). Invalid signatures and expired or missing timestamps return 401 and don't start the workflow. Events not selected return 200 with {ok:true, skipped:true} and don't start it. Requires brixfitApi credentials (baseUrl and apiKey). The base URL must not be a private or localhost address. Deactivating the workflow deletes the webhook in Brixfit.

Examples

Example 1: Send a welcome email when a new lead arrives

Events: Lead Created. Leave options at defaults. Connect an email node using {{$json.email}}.

Example 2: Notify Slack when a lead's status changes or converts

Events: Lead Status Changed, Lead Converted. Set Webhook Description to 'Lead pipeline alerts'. Use {{$json._event}} to branch.

Example 3: Process client check-ins

Events: Check-in Submitted. Keep Require Valid Signature on and the replay window at 5 minutes.

Links

Discussion