n8n-nodes-emberrms

An n8n community node for Ember — the referral intelligence platform. Adds an
Ember RMS action node and an Ember RMS Trigger so anyone can wire referrals, partners, contacts,
and outreach into their own automations.

This is one of three connectors that share the same Ember /v1 API and event surface (n8n, Make, Zapier).
The full operation list is the Ember Connector Reference — 17
triggers and 64 actions.

Install

In n8n: Settings → Community Nodes → Install and enter n8n-nodes-emberrms.

For local development:

cd integrations/n8n-nodes-emberrms
npm install
npm run build          # tsc + copies the icon into dist/

Then link it into a local n8n:

npm link
cd ~/.n8n/nodes && npm link n8n-nodes-emberrms

Credentials

Ember RMS API — a per-tenant API key created in Ember under Settings → Connected Accounts → API
keys. It is sent as a Bearer token and is scoped to a single organization, so a workflow can only ever
touch that tenant's own data. The Base URL defaults to https://api.emberrms.com/v1 (change it only for
self-hosted or staging).

The Ember RMS node (actions)

Pick a Resource, then an Operation. Resources: Contact, Partner, Referral, Interaction, Outreach,
Task, Invite, Tag, Intelligence, Network Card, Utility. Each operation maps to one /v1 REST call.

• Operations that target a record show an ID field.
• Write operations take a generic Fields (JSON) body. (Typed per-operation fields are planned; the
  endpoint contract will not change.)
• List/search operations take Query Parameters (JSON).
• Utility → Custom API Call is an escape hatch: choose a method and path to hit any /v1 endpoint.

Actions that spend credits (Smart Touch, Send Card) or send on the user's behalf are enforced server-side:
Ember debits credits atomically and refuses to send into an Automation-Paused relationship. The connector
is never trusted to make those decisions.

The Ember RMS Trigger (events)

Select one or more events (referral created, referral booked, partner at risk, loop closed, …). On
activation the node registers a webhook subscription with Ember (POST /v1/hooks); Ember then POSTs a
signed payload whenever an event fires. Deactivating removes the subscription.

Layout

credentials/EmberRmsApi.credentials.ts   Bearer API-key credential + connection test
nodes/EmberRms/EmberRms.node.ts          the action node (execute loop)
nodes/EmberRms/EmberRmsTrigger.node.ts   the webhook trigger node
nodes/EmberRms/operations.ts             resource/operation catalog + endpoint map (source of truth)
nodes/EmberRms/emberRms.svg              node icon (the Ember flame mark)

Status

v0.1.0 — full resource/operation surface and the trigger are wired against the /v1 contract. The
matching /v1 API is built separately in the Ember repo; several endpoints already exist as edge
functions (send-email, smart-touch, create-invite, crm-sync) and are being exposed under /v1.