Give your n8n workflows a CRM

n8n handles triggers, logic and hundreds of integrations. It does not ship a CRM, so people bolt on Airtable, a Google Sheet, or a full HubSpot seat just to store contacts and deals. Relm is a lighter, agent-native fit: an API-first CRM with a real object model (contacts, companies, deals, activities, pipelines), a free tier with no card, and a native MCP server that n8n's AI Agent can drive directly.

Option A - the HTTP Request node (no code)

For any workflow, call Relm's REST API from n8n's built-in HTTP Request node. Set it up once:

• Credential. Create a Header Auth credential: name Authorization, value Bearer relm_live_... (mint a key - and a free relm_test_ one to rehearse - at app.relmcrm.com).
• Node. Method POST, URL https://api.relmcrm.com/v1/contacts, Body Content Type JSON, and map your trigger's fields into the body.

# What the HTTP Request node sends to create a contact
POST https://api.relmcrm.com/v1/contacts
Authorization: Bearer relm_live_...
Content-Type: application/json

{ "email": "{{ $json.email }}", "first_name": "{{ $json.first_name }}",
  "type": "lead", "custom_fields": { "source": "n8n-webhook" } }
# -> { "id": "con_...", "object": "contact", ... }

Point the same node at /v1/companies, /v1/deals or /v1/activities for the other objects, or at /v1/batch to write up to 100 records in one call. If a field or value is wrong, Relm answers with a 422 that lists valid_options - so you see the fix in the node output instead of a silent miss.

Option B - the AI Agent node over MCP

If your workflow uses n8n's AI Agent node, skip the field-mapping entirely. Connect Relm's MCP server as a tool via the MCP Client Tool node:

• Endpoint. https://api.relmcrm.com/mcp (Streamable HTTP).
• Auth. Header Authorization: Bearer relm_live_....

The agent now has 37 typed CRM tools and a relm_describe_schema tool for the live contract. Give it an instruction and it does the rest:

You are an SDR assistant. When a new lead arrives, call relm_describe_schema,
then create the contact (email or phone is enough), attach the company if you
can infer it from the email domain, and open a deal in the default pipeline.
Log a note with anything useful from the message. Never invent an email.

Because the tools are typed and the errors are self-correcting, the agent recovers from its own mistakes inside the run rather than dropping rows. A native n8n-nodes-relm community node is on the roadmap; until then the MCP Client Tool and HTTP Request node cover every operation.

Three workflows worth stealing

• Form / webhook → CRM. A Webhook trigger fires the HTTP Request node to upsert a contact (a duplicate email returns the existing record, so re-runs never fork data) and open a deal. Ten-minute build.
• Meeting notes → activities. A trigger with a transcript feeds the AI Agent node; it extracts the people and action items and logs them as activity records with occurred_at set to the meeting date. See the meeting-notes agent prompt.
• Relm webhook → n8n. Subscribe an n8n Webhook URL to deal.stage_changed in Relm; when a deal reaches won, n8n kicks off onboarding, billing or a Slack ping. HMAC-signed, retried, dead-lettered - see the webhook cookbook.

FAQ

How do I connect a CRM to n8n?

With Relm, either the HTTP Request node (Header Auth credential + a JSON body to https://api.relmcrm.com/v1/...) for plain workflows, or the MCP Client Tool pointed at https://api.relmcrm.com/mcp for the AI Agent node.

Does Relm work with the n8n AI Agent node?

Yes - connect its MCP server through the MCP Client Tool and the agent gets 37 typed CRM tools plus relm_describe_schema, and manages contacts, deals and activities in natural language.

Do I need to write code?

No. The HTTP Request node and the MCP Client Tool are configuration-only, and Relm's clear JSON plus valid_options errors keep workflow debugging simple.

What can I automate with n8n and Relm?

Form/webhook-to-CRM, lead enrollment into sequences, meeting-notes-to-activities via the AI Agent, and Relm webhooks that trigger n8n on a stage change. Every write is one request, so it fits Free or Pro.