n8n recipes

What you can do with n8n + RemixCRM

n8n is a self-hostable workflow automation tool — think Zapier but open-source and runs on your own server. RemixCRM works with n8n in both directions:

• Outbound — RemixCRM events trigger n8n workflows (lead.created, etc.)
• Inbound — n8n workflows write data into RemixCRM (create leads, post events)

Combined, you can build anything from "post new leads to Slack" to "if a deposit is paid, create a Trello card for prep, generate a Google Calendar invite, and send a welcome SMS via Twilio."

Why n8n over Zapier

Both work great with RemixCRM via generic HTTP nodes — there's no RemixCRM-specific node yet, but you don't need one.

Outbound — n8n receives events from RemixCRM

How RemixCRM fires events

Whenever something important happens in your org (a lead is created, a payment is recorded, a lead converts), RemixCRM POSTs a JSON payload to a single URL you configure under Settings → Integrations → Workflow Automation → n8n Webhook URL.

The payload format:

{
  "event": "lead.created",
  "org_id": "uuid",
  "timestamp": "2026-05-25T20:30:00Z",
  "data": { ... }
}

See Outbound webhooks for the full list of events and their data schemas.

Setup in n8n

1. New workflow → + → Trigger → Webhook
2. HTTP Method: POST
3. Path: anything memorable, e.g. remixcrm-events
4. Authentication: None (the URL itself is the secret — keep it private)
5. Respond: Immediately
6. Click "Listen for test event" / activate the workflow → copy the Production URL
7. Paste it into RemixCRM Settings → Integrations → n8n Webhook URL

n8n will receive every event for your org. Add a Switch or IF node right after the trigger to route by {{$json.event}} — lead.created, payment.recorded, etc.

Outbound triggers — every event RemixCRM fires

See Outbound webhooks for full payload examples.

Recipe: New-lead Slack alert

1. Webhook trigger (from above)
2. IF node: {{$json.event}} equals lead.created
3. Slack → Send Message node, channel #leads:

   🎯 New lead: {{$json.data.first_name}} {{$json.data.last_name}}
   📧 {{$json.data.email}}
   📅 Event: {{$json.data.event_date}}
   

Recipe: Payment → Slack + QuickBooks

1. Webhook trigger
2. IF: event = payment.recorded AND status = completed
3. Branch A — Slack → #payments: "💰 $X paid by Y for event on Z"
4. Branch B — QuickBooks → Create Invoice node (n8n has a native QuickBooks node) → reconciles automatically

Recipe: Send SMS confirmation on lead conversion

1. Webhook trigger
2. IF: event = lead.converted
3. HTTP Request node (to Twilio direct or to RemixCRM if we add a send-sms endpoint) — text the client: "Hi! We've set up your event in our system. Check your email for next steps."

Inbound — n8n writes data into RemixCRM

The Lead API

Easiest entry point: POST /api/v1/leads. Use an HTTP Request node:

• Method: POST
• URL: https://app.remixcrm.com/api/v1/leads
• Authentication: Header — name Authorization, value Bearer rmx_yourkey (store the key in n8n's credentials manager)
• Body (JSON):

  {
    "name": "{{$json.full_name}}",
    "email": "{{$json.email}}",
    "phone": "{{$json.phone}}",
    "event_date": "{{$json.event_date}}",
    "source": "n8n — {{$workflow.name}}",
    "notes": "{{$json.message}}"
  }
  

See Lead API for the full request schema. Response is 201 Created with { id, status, lead_url }.

Inbound trigger sources — what can feed RemixCRM via n8n

Recipe: Email → lead

Forward all inquiry emails to a dedicated address (e.g. leads@yourdomain.com):

1. Email Trigger (IMAP) node — connects to that mailbox
2. AI/Function node — extract name, email, phone, event date from email body using a regex or an LLM (provider nodes are built in)
3. HTTP Request → /api/v1/leads with extracted fields, source: "Email — leads@yourdomain.com"

Recipe: Cron-based weekly digest

1. Schedule trigger — every Monday 9am
2. HTTP Request → fetch this week's events from RemixCRM (you'd need to add a read endpoint, currently only write endpoints are public)
3. Email/Slack the digest

Note: read-only API endpoints are on the roadmap. For now, n8n can write to RemixCRM but reads must go through Supabase directly with a service role key (advanced — not recommended for most users).

n8n in production

Hosting

Three options:

1. n8n Cloud ($20/mo Starter, includes workflows + maintenance) — easiest, just sign up at n8n.io
2. Self-host on Railway — one-click template, ~$5/mo
3. Self-host on your own server (Docker on a VPS, ~$5/mo on DigitalOcean)

Security

• Webhook URLs are unauthenticated. Anyone with the URL can POST to it. Don't share screenshots that include the URL. Rotate by regenerating the webhook trigger if a URL leaks.
• API keys (RemixCRM Lead API key, third-party keys) belong in n8n's Credentials manager, never hard-coded in nodes.
• Workflow logs retain the request body — be aware that PII (client names, emails) is captured in n8n's execution history. Configure retention to clear old runs.

Reliability

• n8n retries failed HTTP calls automatically (configurable per-node)
• Failed executions surface in the Executions panel with full stack trace
• Hook up Slack/email alerts on workflow failure (Workflow Settings → Error Workflow)