Back to Nodes

Magnet Customer

v1.9.1
Last updated Nov 7, 2025

Rest api for CRM Magnet customer

4 Weekly Downloads
227 Monthly Downloads

Included Nodes

Magnet Customer
Magnet Customer Trigger

Description

License
n8n
dt
dw

Magnet Customer

n8n-nodes-magnetcustomer

This is a N8n community node. It allows you to use Magnet Customer API api to communicate with CRM Magnet Customer in your workflow.

Available Resources

This node provides operations for the following Magnet Customer resources:

  • Customer (Get, Get Many, Search, Create, Update, Delete)
  • Deal (Get, Get Many, Search, Create, Update, Delete)
  • Lead (Get, Get Many, Search, Create, Update, Delete)
  • Organization (Get, Get Many, Search, Create, Update, Delete)
  • Prospect (Get, Get Many, Search, Create, Update, Delete)
  • Task (Get, Get Many, Search, Create, Update, Delete)
  • Staff (Get, Get Many, Search, Create, Update, Delete) – Including loading Roles and Custom Fields.
  • Workspace (Get, Get Many, Search, Create, Update, Delete)
  • Pipeline (Get, Get Many, Search, Create, Update, Delete) – Including filtering, sorting, and detailed updates with stages.
  • Custom Field (Get, Get Many, Search, Create, Update, Delete)
  • Custom Field Block (Get, Get Many, Search, Create, Update, Delete)
  • Custom Field Type (Get, Get Many, Search)

Compatibility

Tested on n8n version 1.62.0

License

MIT

Notas de Compatibilidade – Custom Fields

  • A partir da versão 1.8.3, os carregadores de opções de campos customizados passam a retornar o ObjectId puro dos campos (sem o prefixo customField_).
  • Fluxos existentes que ainda utilizam valores com o prefixo customField_ continuam funcionando: o node sanitiza o valor automaticamente antes de enviar à API.
  • Formato enviado ao backend: cada item em customFields é { customField: "<ObjectId>", v: <valor> }.

Flags de Custom Fields no Node

  • Resolve Custom Fields (para get/getAll em customer/deal/organization/prospect/lead): quando ativado, os campos customizados retornados como customField_<id> são resolvidos para seus nomes e, quando aplicável, para os rótulos das opções.
  • Encode Custom Fields (para update nos mesmos recursos): quando ativado, o node aceita no corpo os nomes dos campos ou valores legíveis, e faz o encode para o formato esperado pela API automaticamente.