Resources · Zapier integration

NMI Merchant Central Zapier integrationAutomate NMI Merchant Central with Zapier.

The NMI Merchant Central Zapier integration gives you 14 triggers, 12 actions and 0 searches. Every trigger is instant, so lead and ticket events reach Zapier as they happen, and the actions write leads, notes, files, tickets, emails and texts back.

See the 26 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the NMI Merchant Central Zapier integration does for a payments team

The NMI Merchant Central Zapier integration links your payments CRM to the rest of your stack in both directions. NMI Merchant Central tracks merchants from first lead through onboarding and support. Zapier can react when a lead or ticket changes, and it can also create and update leads and tickets for you.

Three outcomes come up again and again. Leads that arrive already sorted: a web form or an ad tool feeds Create New Lead, and the record lands in the right group and status with an owner assigned. Follow-ups nobody has to remember: Lead Status Updated fires when a merchant moves stage, and Send Email to Lead or Send SMS to Lead sends the next message from your own templates. Support that stays visible: Ticket Created and Ticket Resolved push support activity to the chat or reporting tool your managers already read.

What Zapier does not do here: there is no search step for this app, so a Zap cannot look up an existing lead or ticket by email or name before acting on it. The update actions work on a record your trigger already handed over. There is also no trigger for new merchants, payments or reports as such; everything revolves around leads and tickets. For anything outside those, the API Request (Beta) action is the only door, and it is a technical one.

If you are still weighing tools, put Zapier side by side with another option in our n8n vs Zapier comparison before you commit.

Vocabulary

Zapier vocabulary in one minute

A handful of Zapier words carry this whole page. Here they are once, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier simply waits for that event to occur.
Action
What the Zap does after it starts: the step that writes, sends or moves something for you in an app.
Task
The unit Zapier bills. One task equals one action your Zap completes successfully; your plan counts those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens.
Filter
A step that lets the Zap continue only when the incoming data meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap with more than one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
Connection
Your NMI Merchant Central account linked to Zapier once, then reused by every step that talks to that app.
Cost

What NMI Merchant Central on Zapier really costs

The triggers are free. The actions are what you pay for, one task at a time.

  • Paid plan required for the appNo
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Triggers14, all instant

A trigger never uses a task, so listening for 14 kinds of lead and ticket events costs nothing. Each action that succeeds counts as one task, and one that fails is not counted. A Zap that creates a lead, adds a note and sends an email therefore costs three tasks per run. NMI Merchant Central is not reserved for paid plans, so the free plan works: 100 tasks a month, unlimited Zaps, two steps per Zap. The moment you chain two actions or add a filter, you need a paid plan.

Connect

Connect NMI Merchant Central to Zapier

  1. 01

    Open your Zapier apps

    Log in to Zapier and open the Apps page of your account, then click + Add connection. You need an existing NMI Merchant Central account, with access to the leads and tickets you want your Zaps to touch.

  2. 02

    Find the app

    In the dialog, type NMI Merchant Central, pick it from the results and click Add connection. A new tab opens on the NMI Merchant Central side so you can identify yourself.

  3. 03

    Sign in and grant access

    Sign in to NMI Merchant Central in that tab and allow Zapier to use the account. The connection is saved in your Apps list, and every Zap step on this app reuses it.

First Zap

Your first Zap: welcome every new lead by email

GoalEach lead created in a chosen status gets a welcome email from your own template, and is assigned to a sales rep.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose NMI Merchant Central as the app and Lead Created as the event, then select the connection you set up earlier.

  2. 02

    Set the status

    The trigger asks for a Current Status. Leave the default to fire on every new lead, or pick the statuses that should start this welcome flow.

  3. 03

    Test the trigger

    Run the test. Zapier pulls the three most recent leads from your account, so you map fields on a real merchant rather than placeholder data.

  4. 04

    Add the email action

    Add Send Email to Lead, choose the lead email field and your template. Check that every field the template uses has a value on that lead, or the email goes out incomplete.

  5. 05

    Assign an owner

    Add Assign User(s) to Lead and pick the rep who should own it. This second action makes the Zap multi-step, so it needs a paid plan.

  6. 06

    Test and publish

    Test each action once, read what came back, then click Publish. Leads created before that moment are not picked up afterwards.

Triggers

The 14 NMI Merchant Central triggers

14 events start a Zap when something happens in NMI Merchant Central, and 14 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Lead Created

Instant trigger

In Zapier“Triggers when a lead is created.”

Starts a Zap the moment a new lead appears in NMI Merchant Central, whether your team typed it in or another tool pushed it there. The whole lead record travels to your next step.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a new merchant prospect should trigger a welcome email and a notice to the sales rep straight away.
Watch out
the Current Status setting is required; keeping the default of any status fires on every single lead, including test ones.
2

Lead Deleted

Instant trigger

In Zapier“Triggers when a lead is deleted.”

Reacts when someone removes a lead from NMI Merchant Central. Useful to keep other systems honest, so a record that disappeared from the CRM does not live on in a mailing list or a spreadsheet.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
your marketing list must drop prospects as soon as sales deletes them from the pipeline.
Watch out
a deleted lead can come back through Lead Restored, so plan what the other tool should do in that case too.
3

Lead File Uploaded

Instant trigger

In Zapier“Triggers when a lead file is uploaded.”

Fires each time a file is attached to a lead: a signed application, an ID scan, a bank statement. The Zap receives the file details so it can be copied, logged or flagged for review.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
underwriting wants a heads-up whenever a merchant uploads onboarding paperwork.
Watch out
the required Current Status lets you limit this to leads in a given stage; the default ignores the stage entirely.
4

Lead Email Received

Instant trigger

In Zapier“Triggers when a lead email is received.”

Kicks in when an email from a lead arrives in NMI Merchant Central. That reply is often the signal a deal is moving, and this trigger lets you act on it outside the CRM.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the assigned rep should get a chat ping when a hot prospect answers, instead of finding it hours later.
Watch out
you must pick a Current Status; choose any status only if every reply, from every stage, deserves the alert.
5

Lead Note Added

Instant trigger

In Zapier“Triggers when a lead note is added.”

Runs whenever someone writes a note on a lead. Notes hold call summaries and internal context, and this trigger lets that context travel to wherever the rest of the team reads.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a manager wants a running log of notes on leads in the final negotiation stage.
Watch out
if the same Zap also uses Add Note to Lead, each note it writes fires the trigger again and loops.
6

Lead Restored

Instant trigger

In Zapier“Triggers when a lead is restored.”

Responds when a previously deleted lead is brought back. Rare, but when it happens, the tools you cleaned up after the deletion need to hear about it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a lead removed by mistake must reappear in your mailing list or reporting sheet without anyone thinking about it.
Watch out
it only makes sense paired with a Lead Deleted Zap; on its own, it rarely fires.
7

Lead Status Updated

Instant trigger

In Zapier“Triggers when a lead's status is updated.”

Watches stage changes on leads, the moves that actually matter in a merchant pipeline. You choose which transition counts, from one status to another, so the Zap fires only on the step you care about.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a lead moving to approved should get a text and an onboarding checklist without anyone pressing a button.
Watch out
Previous Status and New Status are both required; leaving both on any status fires on every move.
8

Lead Updated

Instant trigger

In Zapier“Triggers when a lead is updated.”

Fires on any change to a lead record: a phone number fixed, an address added, a field filled in. It is broad by design, which makes it handy for syncing but noisy for alerts.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a second system holds a copy of your leads and must stay identical to the CRM.
Watch out
pairing it with Update Lead in the same Zap is a classic loop: each update sets the trigger off again.
9

Ticket Checklist Updated

Instant trigger

In Zapier“Triggers when a ticket checklist is updated.”

Wakes up when the checklist on a support ticket is updated, for instance when an agent works through the steps of an onboarding routine.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a team lead wants to follow progress on long setup tickets without opening each one.
Watch out
each checklist update can start the Zap again, so a long checklist means many runs; a filter keeps only the updates you care about, on a paid plan.
10

Ticket Commented

Instant trigger

In Zapier“Triggers when a ticket is commented.”

Reacts to every new comment on a ticket, from an agent or from the merchant side. Comments are where the conversation happens, so this is the trigger for keeping people in the loop.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
the account manager should see each exchange on tickets opened by a key merchant.
Watch out
a Zap that answers with Add Comment to Ticket will fire itself again; keep those two apart.
11

Ticket Created

Instant trigger

In Zapier“Triggers when a ticket is created.”

Fires the moment a support ticket is opened in NMI Merchant Central. The new ticket reaches the next step, ready to be routed to the tool your team watches.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
new tickets should show up in the team chat channel so nobody waits for the next inbox check.
Watch out
tickets opened before the Zap was published never come through; the backlog needs its own handling.
12

Ticket Resolved

Instant trigger

In Zapier“Triggers when a ticket is Resolved.”

Runs when a ticket is marked resolved. That closing moment is the right time to measure, to thank the merchant, or to ask how the support went.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
each resolved ticket should add a row to the reporting sheet your support lead keeps.
Watch out
tickets resolved before the Zap was published never come through, so your report starts on the day you switch it on.
13

Ticket Type Updated

Instant trigger

In Zapier“Triggers when a ticket type is updated.”

Triggers when an agent reclassifies a ticket, for instance moving it from a general question to a chargeback or a technical incident. A change of type often means a change of owner.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
escalated categories should alert a specialist team the second a ticket is reclassified.
Watch out
only the type change counts; other edits to the ticket go through Ticket Updated instead.
14

Ticket Updated

Instant trigger

In Zapier“Triggers when a ticket is updated.”

The catch-all for tickets: any update to an existing ticket starts the Zap, which makes it the broadest of the ticket triggers.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
a mirror of your tickets in another tool must reflect every change.
Watch out
combined with Update Existing Ticket in the same Zap, it triggers itself in a loop and burns through tasks quickly.
Actions

The 12 NMI Merchant Central actions

NMI Merchant Central gives you 12 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add Comment to Ticket

Action

In Zapier“Add Comment to Ticket.”

Posts a comment on an existing ticket, so updates from other tools show up in the ticket's history.

When to use it
a status change in your project tool should be noted on the related support ticket.
Watch out
decide whether merchants can see the comment before any internal wording goes into it.
2

Add File to Lead

Action

In Zapier“Add file to a lead.”

Attaches a document to a lead, filed under the tab and label you pick, using a file the trigger app provides.

When to use it
a contract signed in an e-signature tool should be stored on the merchant's lead.
Watch out
the file name and file source must come from the trigger step; typing them by hand will not work.
3

Add Note to Lead

Action

In Zapier“Add note to a lead.”

Writes a note on an existing lead, in the note tab you choose, optionally pinned as sticky so it stays on top.

When to use it
a call summary from your phone tool should land on the lead automatically.
Watch out
note tab, sticky choice and content are all required, and a Lead Note Added Zap will react to it.
4

Assign User(s) to Lead

Action

In Zapier“Assign user(s) to a lead.”

Puts one or more team members on a lead, and can add their managers too.

When to use it
leads from a given region should go straight to the rep who covers it.
Watch out
if no user is picked or no email matches, the lead goes to whoever created the API key behind the Zap.
5

Create New Lead

Action

In Zapier“Create a new lead.”

Adds a fresh lead to NMI Merchant Central from whatever your trigger collected, a form, an ad, a spreadsheet row.

When to use it
prospects from your website form should enter the pipeline without retyping.
Watch out
group, status and assigned user are required, so decide where new leads belong before building the Zap.
6

Create New Ticket

Action

In Zapier“Create a new Ticket.”

Opens a support ticket for you, with its type, subject and who it is assigned to.

When to use it
an issue reported in another tool, a form or an email inbox, should become a tracked ticket.
Watch out
a visibility switch decides whether merchants see the ticket; check it before sending internal notes their way.
7

Send Email to Lead

Action

In Zapier“Send email to a lead.”

Sends an email to a lead from one of your NMI Merchant Central templates, to the address field you point at.

When to use it
a status change should trigger the matching follow-up message.
Watch out
every field your template uses needs a value on that lead, or the merchant gets a message with gaps.
8

Send SMS to Lead

Action

In Zapier“Send SMS to a lead.”

Texts a lead using an SMS template stored in your account, sent to the phone field you select.

When to use it
a merchant approved for onboarding gets a short text with the next step.
Watch out
as with email, empty fields in the template produce incomplete texts; check the lead's data first.
9

Update Lead

Action

In Zapier“Update an existing lead.”

Changes the details of an existing lead with new values coming from your trigger or earlier steps.

When to use it
a merchant corrects their address in a form, and the CRM should reflect it.
Watch out
with no search step on this app, the Zap needs the lead from its trigger to know which record to change.
10

Update Lead Status

Action

In Zapier“Update status of a lead.”

Moves a lead to a new status, and to a new group if that status does not exist in its current one.

When to use it
a signed contract elsewhere should push the lead to the next pipeline stage.
Watch out
both new status and fallback group are required, and a Lead Status Updated Zap will fire.
11

Update Existing Ticket

Action

In Zapier“Update Existing Ticket.”

Edits a ticket that already exists, for example its details or whether merchants can see it.

When to use it
a fix confirmed in your engineering tracker should update the related support ticket.
Watch out
never pair it with Ticket Updated on the same ticket flow, or the Zap loops.
12

API Request (Beta)

Action

In Zapier“This is an advanced action which makes a raw HTTP request that includes this integration's authentication.”

An advanced action that sends a raw request to NMI Merchant Central with your connection already attached, for things no other action covers.

When to use it
a developer on your team needs one specific operation the list above lacks.
Watch out
it only reaches the app's own domains, and the stop-on-error choice decides whether a failure halts the Zap.
When it breaks

When an NMI Merchant Central Zap breaks

Zapier links no help article and no rate limit to this app. What goes wrong is the general Zapier behaviour, sharpened by how many triggers and actions here touch the same records.

With 14 triggers and 12 actions on the same leads and tickets, the most common failure is a Zap that sets itself off. The others are quieter but just as costly. If one of your Zaps still misbehaves after these checks, our Zapier troubleshooting guide takes you through the next steps.

  • The Zap triggers itself

    Lead Updated plus Update Lead, Ticket Updated plus Update Existing Ticket, Lead Note Added plus Add Note to Lead: each pair writes where its own trigger watches and loops.

  • Older leads and tickets never arrive

    A Zap only sees what happens after it is published. Leads and tickets created before that stay out, and migrating them is a separate job.

  • A bulk import gets held back

    Importing many leads at once can produce a sudden batch of events. Zapier's flood protection may hold them instead of running each one.

  • Messages go out with blanks

    Email and SMS templates pull values from the lead. If a field used by the template is empty, the merchant receives an incomplete message.

  • The wrong person owns the lead

    When no user is selected or no email matches, the lead is assigned to whoever created the API key behind the Zap, not to a sales rep.

  • The filter never lets anything through

    Filter rules are typed: a number rule on a text field, or the reverse, never matches, so the actions after the filter never run.
Need help

Need help automating NMI Merchant Central with Zapier?

A person reads every message.

FAQ

NMI Merchant Central Zapier integration: frequently asked questions

01Is the NMI Merchant Central Zapier integration free?
Yes, within the free plan's limits. NMI Merchant Central is not one of the apps Zapier reserves for paid plans, so you can connect it at no cost. The free plan gives 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger and one action. A Zap that sends an email and then assigns a rep has two actions, which makes it multi-step and requires a paid plan. Plenty of useful flows fit in two steps, such as a status change that sends one text.
02How many tasks does an NMI Merchant Central Zap use?
One task per action that succeeds, and nothing for the trigger. Listening for new leads, comments or status changes is free however many arrive. A Zap that creates a lead, adds a note and sends an email uses three tasks on each run. An action that fails is not counted against your plan. A few apps and actions take more than one task when they complete, so if your count climbs faster than expected, look at the action steps first, then at any loop between triggers and updates.
03Do NMI Merchant Central triggers run in real time?
Yes. All 14 triggers are instant: NMI Merchant Central itself tells Zapier when a lead or ticket event happens, and the Zap starts straight away whatever your plan. The editor shows a lightning bolt on those Zaps. The interval grid on Zapier pricing, 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers, and this app has none. That makes it one of the cases where a free plan reacts as fast as a paid one.
04What does it take to connect NMI Merchant Central to Zapier?
An NMI Merchant Central account and a Zapier account. In Zapier, open the Apps page, click + Add connection, search for NMI Merchant Central, then click Add connection and sign in on the tab that opens. Grant Zapier access and the connection is stored. Your account needs access to the leads and tickets the Zaps will touch. Before building, prepare what the actions rely on: groups and statuses, email and SMS templates, file tabs and labels. They have to exist in the app first.
05Why does a lead Zap fire on every single lead?
Because the status settings were left on their default. Lead Created, Lead File Uploaded, Lead Email Received and Lead Note Added all require a Current Status, and Lead Status Updated requires both a Previous Status and a New Status. Keeping any status on those fields makes the Zap run on every event, whatever stage the lead is in. Pick the specific statuses that matter instead. It saves tasks downstream and keeps merchants from receiving messages meant for a different stage of the pipeline.
06What if the NMI Merchant Central operation you need is missing?
Then the standard list cannot do it. This page covers every visible operation: 14 triggers and 12 actions, with no search step. If you need to look up a lead before acting, or reach data beyond leads and tickets, the API Request (Beta) action sends a raw request to the app using your existing connection. It is meant for someone comfortable with technical documentation. Otherwise, check whether a different trigger covers the same moment, or ask NMI whether new operations are planned for the Zapier app.
07Zapier, Make or n8n for NMI Merchant Central?
It depends on your criteria rather than on a single winner. On Zapier, NMI Merchant Central gives you 14 instant triggers and 12 actions, usable from the free plan, but no search step, so a Zap cannot look up a lead or ticket on its own. Before weighing Make or n8n, check whether each one offers an NMI Merchant Central connector and which operations it exposes; a search would change the picture. Then compare what matters to your team: how you like to build, where the automations should run and who will maintain them.
Same platform

Other docs you might need on this stack.

Browse all integrations