Automation integration

Connect Incoming webhook to MailNesto

A private URL any system can post contacts to — JSON or form data.

Overview

Incoming webhook and MailNesto, together

The incoming webhook is the simplest way into MailNesto: a private URL that accepts contacts from anything able to make an HTTP POST. A booking system, a custom-built form, an internal tool or a script on your server can all use it without an API key.

You decide where new people go and how they are tagged when you create it. Each request is answered with how many contacts were added, updated and skipped, and every request appears in the Activity tab, so you can see what a system actually sent when something looks wrong.

What syncs

What moves between Incoming webhook and MailNesto

Into MailNestoSingle contacts

JSON or form data with at least an email. Names, tags and any other plain values are saved; nested values are ignored except where MailNesto looks for the email.

Into MailNestoBatches

A JSON array adds up to 100 contacts per request, each with its own result.

Into MailNestoConsent

Optionally only add people whose payload has consent set to true, yes, 1 or on.

Set it up

Connect Incoming webhook in a few minutes

  1. 1

    Create the webhook

    Go to Integrations → Connect an app → Incoming webhook. Choose “Add new contacts to” a list, add tags, and decide whether to require consent=true. Click Connect and copy the private URL.

  2. 2

    Post a test contact

    Use the curl command shown under “Try it”, which sends {"email":"priya@example.com","first_name":"Priya","city":"Hyderabad","tags":"rsvp"}. You get back {"ok":true,"added":1,…}.

  3. 3

    Wire up your system

    Point your form handler or script at the same URL. Keep sending the fields you care about under stable names, because those names become the contact fields you’ll use in segments.

  4. 4

    Keep the URL private

    Only owners and admins see the URL. If it ends up somewhere it shouldn’t, use “New secret URL” and the old one stops working immediately.

Ideas

What you can do with it

Walk-in sign-ups from a tablet

A salon in Chandigarh can collect emails on a tablet at the counter with a small web page that posts to the webhook, tagging each person with the branch they visited.

Event RSVPs into reminders

Tag RSVPs with the event name and start an automation on that tag: confirmation now, directions the day before, and a thank-you after.

Trial users into onboarding

Post new trial users from your app with a plan field. The welcome automation can split on plan to send the right getting-started steps.

FAQ

Questions about the Incoming webhook integration

Where does MailNesto look for the email?

In email, Email, email_address and similar keys at the top of the body, and inside a data, contact, customer, subscriber, user, payload or fields object.

How are tags sent?

As a list (["rsvp","pune"]) or as comma-separated text ("rsvp, pune"). They are added on top of the tags set on the webhook, up to 20 per contact.

Will it create duplicates?

No. Emails are matched without regard to case, and an existing contact is updated instead of added again.

Can I see what a system sent?

The Activity tab lists every request with its result, such as “2 added, 1 updated, 1 skipped (no valid email)”. The last 500 events per connection are kept.