Connect Make to MailNesto
Send contacts from any Make scenario with an HTTP module.
Make and MailNesto, together
Make scenarios can add and update MailNesto contacts with one HTTP module. Point an HTTP “Make a request” module at your private URL, send a JSON body with an email field, and the person appears in MailNesto with whatever else you included.
This suits teams who already use Make to glue tools together: a scenario that watches a form, a CRM, an event platform or a payment tool can feed your email list in the same run. Because the URL accepts arrays, a scenario can also send a batch of up to 100 people in one request.
What moves between Make and MailNesto
Email, names and tags, plus every other plain value in the body as a contact field (city, plan, course, source and so on).
Send an array of up to 100 objects. The reply reports added, updated and skipped counts with a reason per skipped row.
Signed webhooks from Developers → Webhooks for contact, email activity, campaign, order and transactional events, which a Make custom webhook can receive.
Connect Make in a few minutes
- 1
Connect Make in MailNesto
Open Integrations → Connect an app → Make. Pick a list and tags, decide whether to require consent=true in the payload, and click Connect. Copy the private URL.
- 2
Add the HTTP module
In your scenario add HTTP → Make a request. Method POST, the URL from MailNesto, body type raw with content type JSON. Map at least email, and add first_name, last_name, tags and any fields you want.
- 3
Run once and check
Run the scenario once. The module’s output shows the reply, and the Activity tab in MailNesto shows what happened to each contact.
- 4
Receive events (optional)
To react in Make when something happens in MailNesto, create a custom webhook in Make, copy its address and add it as an endpoint under Developers → Webhooks with the events you want.
What you can do with it
If your event app records check-ins, a scenario can send attendees with the tag “attended-mumbai-meetup”. The Post-event follow-up recipe can then thank them and ask two quick questions.
Send city as a field. A split step in your welcome automation can then give Delhi, Mumbai and Bengaluru leads their own store addresses and offers.
Let Make look up the company or plan first and send it along. Segments in MailNesto can then target “plan is Pro” without a second import.
Route the “Email bounced” event through Make to message the account manager responsible for that client, so the address gets fixed quickly.
Questions about the Make integration
Does it accept form data as well as JSON?
Yes. JSON and URL-encoded form data both work. JSON is easier to map in Make and keeps arrays intact.
How are field names stored?
They are lower-cased with spaces and symbols turned into underscores, so “Course Name” becomes course_name. Each value is kept up to 500 characters.
Can I turn off saving extra fields?
Contacts keep email, names and tags plus extra fields by default. If you only want the basics, send only those keys from Make.
What does a skipped contact mean?
The reply gives the reason: no valid email, the address is suppressed, consent was required but missing, or the plan’s contact limit has been reached.