n8n-nodes-brixfit

What is Brixfit?

Brixfit is an AI-powered coaching CRM built for fitness and health coaches. It manages leads, clients, check-ins, workout plans, diet plans, progress photos, and automated health reports — all in one place.

This node lets you connect Brixfit to any tool in your n8n workflow.

Nodes Included

Prerequisites

• A Brixfit account (coach plan)
• An API key — generate one at Brixfit → Developer → API Keys
• n8n v1.0.0 or later

Installation

n8n Cloud / Self-hosted UI (recommended)

1. Go to Settings → Community Nodes
2. Click Install
3. Enter n8n-nodes-brixfit
4. Click Install and confirm

Self-hosted (manual)

# Navigate to your n8n installation
cd /usr/local/lib/node_modules/n8n

# Install the package
npm install n8n-nodes-brixfit

# Restart n8n

Setup

1. Add Brixfit credentials

In n8n, go to Credentials → New and search for Brixfit API.

Click Save — n8n automatically tests the connection with a live API call and confirms your key is valid before saving.

2. Add the Brixfit node to a workflow

Drag the Brixfit node from the node panel and select your resource and operation.

3. Add the Brixfit Trigger (for event-driven workflows)

Drag Brixfit Trigger as the first node in your workflow:

1. Select the events you want to listen for
2. Activate the workflow — n8n automatically registers the webhook in Brixfit and stores the signing secret

That's it — no manual copy-paste. When you deactivate the workflow, the webhook is automatically removed from Brixfit.

Development note: Brixfit requires HTTPS webhook URLs. For local development use a tunnel such as ngrok to expose your n8n instance.

Operations

Lead

Dynamic fields: When you create or update a lead, the node automatically fetches your custom field definitions from Brixfit and shows them as individual inputs. Click Refresh to reload after adding new fields.

Plan-gated metrics: Health metrics (BMI, BMR, TDEE, body fat %) in Create and health report responses are filtered to only include what your Brixfit plan allows.

Client

Check-in

Webhook

Trigger Events

The Brixfit Trigger node starts your workflow when any of these events fire:

All payloads are HMAC-SHA256 signed. The node verifies signatures using the original raw bytes and constant-time comparison — tampered or unsigned requests are rejected with HTTP 401. Replay protection rejects requests older than 5 minutes (configurable). The signing secret is stored internally after auto-registration; you never need to copy it manually.

Output format: payload fields are flattened to the top level so you can use $json.name, $json.email, $json.id directly in expressions. Meta fields are available as $json._event, $json._timestamp, $json._coach_id.

Example Workflows

1. Capture leads from any form → Brixfit

Typeform / Tally / Facebook Lead Ads Trigger
  → Set (map name, email, phone, goal)
  → Brixfit: Create Lead

2. New lead → WhatsApp + Google Sheets

Brixfit Trigger (lead.created)
  → WhatsApp: Send welcome message to lead
  → Google Sheets: Append row

3. Client check-in submitted → Slack notification

Brixfit Trigger (checkin.submitted)
  → Slack: Send message to #coach-alerts
        "{{ $json.client_name }} just submitted their check-in"

4. Daily check-in report → Email

Schedule Trigger (every day at 9am)
  → Brixfit: Get All Check-ins (from_date: today, status: pending)
  → Gmail: Send summary to coach

5. Lead status changed → CRM sync

Brixfit Trigger (lead.status_changed)
  → IF (status == "converted")
      → HubSpot: Create Contact
      → Slack: Notify sales team

6. Auto-assign workout when client is created

Brixfit Trigger (client.created)
  → Brixfit: Get client details
  → HTTP Request: Trigger internal workflow

Data Handling

When creating or updating leads via this node, Brixfit automatically:

• Calculates body metrics (BMI, BMR, TDEE, body fat %) from height, weight, age, gender, and activity level fields — no manual calculation needed
• Normalizes phone numbers — strips trunk zeros, handles international formats (00XX → +XX)
• Validates and casts field types — numbers stay numbers, dates become ISO strings, booleans are properly coerced

Security

This node follows security best practices out of the box:

• HMAC-SHA256 webhook verification — uses raw request bytes and constant-time comparison
• SSRF protection — Base URL is validated; private/internal network addresses are rejected
• Path traversal prevention — all ID parameters are validated against an allowlist before use in URLs
• 30-second request timeout — prevents n8n executions from hanging on slow API responses
• Live credential testing — API key is verified immediately on Save

Resources

• Brixfit website
• API documentation
• Developer dashboard (login required — API keys & webhooks)
• npm package
• GitHub repository
• Changelog
• Report a bug
• Contact support

Changelog

See the CHANGELOG folder for full version history.

Support

• Bugs / feature requests: GitHub Issues
• General support: support@brixfit.app
• API reference: brixfit.app/api-docs
• Developer dashboard: brixfit.app/coach/developer

Contributing

Pull requests are welcome. For major changes, please open an issue first.

License

MIT — © 2026 Jatin Beniwal / Brixfit