Use Cases

What teams build on Magnet Customer, and which pieces of the platform each scenario uses.

Capture leads from your website

Forms and landing pages collect contacts that someone retypes into the CRM later — or never.

  1. Your backend receives the form submission.
  2. It creates the lead in the CRM with the fields and the custom fields you map.
  3. The lead enters the owner's queue right away, with the source recorded.
POST /api/leadsGET /api/customfields
Create leads from web forms →

Keep the CRM and your ERP in sync

Customer data lives in two systems and drifts apart.

  1. A scheduled job reads the contacts changed since the last run, page by page.
  2. It writes the changes to the ERP and sends the ERP changes back to the CRM.
  3. Webhooks cover what cannot wait for the next run.
GET /api/contactsPUT /api/contacts/{id}contact.updated
Sync contacts with an ERP →

React when a deal is won

Closing a sale should start billing, onboarding and the contract — today someone has to remember.

  1. An administrator creates a webhook in the CRM (Integrations › Webhooks) for the deal events you care about. Close deals through the API or the deal screen.
  2. Validate the signature and acknowledge with 200.
  3. Start the next step in your billing or onboarding system.
Webhooksdeal.wondeal.stageChanged
Set up webhooks →

Open and follow support tickets from another system

Requests arrive through a portal, an app or a monitoring tool, outside the service desk.

  1. Your system creates the ticket in the CRM, linked to the contact.
  2. A webhook tells your system when the status changes or the ticket is finished.
  3. The customer sees the progress where the request was made.
POST /api/ticketsticket.statusChangedticket.finished

Act before a customer churns

The signs of churn are in the customer journey, but nobody is watching all of them.

  1. An administrator creates a webhook in the CRM for the journey health events.
  2. When the health score drops below the limit, create a task for the account owner.
  3. Read the health score of each journey to prioritize who to call first.
journey.health_score_belowGET /api/journeys/{id}/health-scorePOST /api/tasks

Take CRM numbers to your BI

Management wants pipeline and activity numbers next to the rest of the company data.

  1. A scheduled job reads deals, tasks and meetings with pagination.
  2. It loads the data into your warehouse.
  3. Your BI tool reads from there, next to the rest of the company data.
GET /api/dealsGET /api/tasksGET /api/meetings

Automate without writing code

The operations team wants to connect the CRM to spreadsheets, chat and forms without waiting for development.

  1. Install the Magnet Customer node in n8n, or accept the Zapier invitation.
  2. Connect it to your account.
  3. Combine CRM triggers and actions with the other tools in the workflow.
n8nZapier

Put an AI assistant to work on the CRM

Finding a customer's history, summarizing a ticket or updating a deal takes many clicks.

  1. Create an assistant in the CRM and choose what it can reach.
  2. Connect your AI client to the assistant's address.
  3. Ask in natural language; the assistant reads and, if allowed, updates the records.
MCP
See the integrationsAPI Reference