msu-crm

Send leads into MSU CRM. Pick a campaign type and its fields load automatically.

Package Information

Released: this month
Downloads: 0 weekly / 0 monthly
Latest Version: 0.4.0
Author: MSMedia

Available Nodes

Documentation generating…

MSU CRM icon
MSU CRM
הכנסת ליד ל-CRM של מיינסטרים, או הוספת מידע לליד קיים

Documentation

n8n-nodes-msu-crm

n8n community node for MSU CRM — send leads from any automation into a
client's CRM.

Pick the campaign type from a dropdown and its fields load automatically,
so you map real field names instead of guessing at a JSON body.

Installation

Self-hosted n8n → Settings → Community nodes → Install →
n8n-nodes-msu-crm

Credentials

Field Value
כתובת המערכת (Base URL) e.g. https://crm.msmedia.dev — no trailing slash
מפתח API (API key) agk_… (agency) or msk_… (single client)

Two kinds of key:

  • Agency key (agk_) — opens every client of the agency. Created in the
    agency settings → מפתח לאינטגרציות. Shown once; if lost, rotate it.
    With this key, pick the לקוח (client) in the node first.
  • Client key (msk_) — opens one client. Created inside the client →
    סוגי קמפיינים (Campaign types) → מפתח לכלי אוטומציה. The לקוח
    field can stay empty.

A leaked client key opens one client; a leaked agency key opens all of them.
Pick the narrower one when you only work with a single client.

Usage

  1. With an agency key, choose לקוח (client) — loaded from the CRM
  2. Choose סוג קמפיין (campaign type) — loaded from the CRM
  3. The fields of that type appear — map values from your workflow
  4. Optionally flag the lead as a test

A campaign type marked ⚠️ has no pipeline stages yet, so the CRM has nowhere
to put the lead. Fix it in the CRM before running.

No field is required. The CRM accepts partial leads on purpose — a lead
missing a name is stored as "ליד ללא שם" rather than rejected, because
dropping a real lead is worse than storing an incomplete one.

Notes

  • Duplicate detection runs in the CRM: same phone or email, within 24
    hours, inside the same campaign type.
  • On HTTP 503 the CRM is saturated. The node retries twice on its own
    (after 1s and 3s) before failing. Such a response writes nothing at all, so
    a retry cannot create a duplicate. The retry lives in the node rather than
    relying on n8n's Retry On Fail setting, which is off by default — a lost
    lead is not an acceptable default.
  • On HTTP 409 multiple_matches (enrich only) the CRM found more than one
    lead matching your lookup value and refuses to guess which one to write to.
    The node surfaces the candidates in the error. With Continue On Fail
    enabled, the full response — including the matches array — is passed to
    the error output so you can branch on it. Looking up by lead ID is the
    only method that cannot collide.

License

MIT

Discussion