Integration
Make and Naffes CRM: scenarios that start when deals move
Every time a deal enters a new stage, Naffes CRM posts a JSON event to your Make webhook, so scenarios can connect that deal to the rest of your tools: finance sheets, project folders and team alerts.
What you can build with it
Make is a visual automation platform that chains app modules into scenarios. Naffes is the starting point: each deal stage change reaches the scenario with the deal name, amount, pipeline, and the stage it left and entered.
Scenarios operations teams build without a developer:
- When a deal reaches the contract stage, add a row with the amount and customer to the finance sheet.
- When a deal enters delivery, create a project folder in your file tool and notify the project manager.
- When a deal slips back a stage, alert the sales manager in your internal chat tool.
What is possible depends on the apps in your Make account; on the Naffes side you only need one URL. For automation inside Naffes itself, such as creating a task or sending a WhatsApp template, use the built-in workflows.
Setup
Create a webhook in Make
Start a scenario with Webhooks > Custom webhook as the first module, add a new webhook and copy its URL.
Paste it into Naffes
As an admin, open Marketplace > Make > Configure Make, paste the address into Webhook URL and click Save. Leave the optional API Token field empty; Naffes does not use it when sending.
Confirm requests arrive
Click Test connection. Naffes posts a test request and shows the response code. The test carries a test event only, without deal fields.
Teach Make the data structure
Run the scenario once so the webhook is listening, then change a test deal's stage in Naffes. A real event arrives and Make learns its structure.
Add filters and activate
Filter on data.stage, for example, using the stage name exactly as it appeared in the real event, then finish the modules and activate the scenario so it processes events as they arrive.
Use the Make card in the Marketplace. Automation links on the Developer tab can be saved and tested, but Naffes never sends events to them.
The payload Make receives
Events arrive as a JSON POST with a fixed envelope: event set to deal.stage_changed, delivered_at with the send time, and data holding these fields:
| Field | Meaning |
|---|---|
| deal_id | The deal's Naffes ID |
| name | Deal name |
| amount | Deal amount |
| pipeline | Pipeline name |
| previous_stage | Name of the stage it left |
| stage | Name of the stage it entered |
| updated_at | When the deal was last updated |
Stage and pipeline arrive as display names, not internal IDs. Data flows from Naffes to Make only. To write back, for example to update a deal or create a contact, use Make's HTTP module with the REST API and a personal access token, keeping in mind tokens expire after 14 days by default.
Delivery limits
- One event. Stage changes only; no contact or company events.
- Unsigned, no retries. Each event is posted once with a short timeout. If Make is unreachable, it is lost.
- Public URLs only. Make's own webhook URLs qualify; any private or internal address is blocked.
- Make's own limits. Make accepts up to 300 incoming webhook requests per 10-second window and answers 429 above that, queues unprocessed items up to a plan-based limit, and deactivates webhooks left without a scenario after 5 days.
For more events, such as contact created or deal deleted, with signatures and automatic retries, create an outgoing webhook in Settings pointing at the same Make URL. That is included in the Pro plan.
Questions
Questions 4
Why doesn't Make see the deal fields after Test connection?
The test request carries a test event with no deal fields. Move a test deal between stages while the scenario is listening so a real event arrives.
Does Naffes resend the event if Make was down?
No. Events from the Make card are sent once. For reliable delivery, use outgoing webhooks from Settings, which make up to 7 delivery attempts before giving up.
Do I need a developer?
Not for the basics: paste one URL into Naffes and build the scenario in Make. Writing back into Naffes through the API is where technical help is useful.
Can Make and n8n both receive events?
Yes. When configured, every stage change goes to Make, n8n and the Custom Webhook URL at the same time.
Sources
- Make Help Center: WebhooksAccessed