Connect n8n to MailNesto Staging
n8n workflows posting contacts with an HTTP Request node.
n8n and MailNesto Staging, together
n8n is a workflow tool many technical teams run on their own servers. To send contacts to MailNesto Staging, add an HTTP Request node, set it to POST to your private URL and send a JSON body with an email field. There is nothing to install on the MailNesto Staging side.
n8n also works well as the receiving end. MailNesto Staging can post signed events to an n8n Webhook node, so you can react to clicks, unsubscribes, bounces or new orders in your own systems, and check the signature in a Code node before trusting the data.
What moves between n8n and MailNesto Staging
Email, names, tags and any extra values as contact fields. Arrays of up to 100 contacts are accepted in one request.
If you send through a provider MailNesto Staging doesn’t read natively, an n8n workflow can reshape its events into the simple format the “Other providers” bounce webhook expects.
Signed with a signature header (a timestamp and an HMAC-SHA256 of the timestamp and body), and retried with growing gaps if your endpoint is down.
Connect n8n in a few minutes
- 1
Connect n8n in MailNesto Staging
Go to Integrations → Connect an app → n8n, choose a list and tags and click Connect. Copy the private URL.
- 2
Add an HTTP Request node
Method POST, URL from MailNesto Staging, body content type JSON, with at least {"email": …}. Add first_name, last_name, tags and other fields as needed.
- 3
Try it from the command line
The drawer shows a curl command under “Try it” that posts a sample contact. Running it is a quick way to confirm the URL before you build the workflow.
- 4
Receive events (optional)
Add a Webhook node in n8n and copy its production URL. In MailNesto Staging open Developers → Webhooks, add the endpoint, pick events and copy the signing secret into your workflow.
What you can do with it
A SaaS team can run a scheduled n8n workflow that reads new users from their database and posts them with plan and signup_date fields, so onboarding emails match each plan.
Use the “Spam complaint” event to create a ticket in your help desk, so someone checks why that person felt the need to report the email.
Post contacts with a field your sales team cares about, such as company_size, then use it in a segment or a split step in an automation.
Stream “Email opened”, “Link clicked” and “Order received” events into your warehouse for your own reporting alongside MailNesto Staging’s reports.
Questions about the n8n integration
Does it work with my own n8n server?
Yes. Your n8n server only needs to reach your private MailNesto Staging URL over HTTPS. For events going the other way, your n8n webhook must be reachable from the internet.
How often are failed event deliveries retried?
Up to five retries after the first try, at about 30 seconds, 1, 2, 4 and 8 minutes. Every attempt is logged, and you can retry a delivery by hand from Developers.
Can I map fields explicitly?
Shape the JSON in n8n so the keys are the field names you want in MailNesto Staging. Common names like email, first_name and tags are recognised automatically.
Is there a limit on requests?
Each request can carry up to 100 contacts. For large one-off loads, a CSV import or a scheduled import is usually faster.