Nerv Zapier integrationAutomate Nerv with Zapier.
The Nerv Zapier integration offers 2 triggers, 0 actions and 0 searches. It works in one direction: each new contact or contact group in Nerv starts a Zap instantly, and your other tools receive the details without anyone copying them over.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nerv Zapier integration does for you
Nerv is a mobile app for making and sharing digital business cards, with the contacts and contact groups that come with them. The Zapier integration lets those contacts leave the phone: a Zap (the automation you build on Zapier) starts in Nerv and passes each new contact or group to your other tools.
Three results worth building. Contacts that reach your CRM on their own: New Contact starts a Zap that creates the person in your CRM, so a contact saved in Nerv does not stay locked inside the app. A team that hears about new contacts: the same trigger, with a message action behind it, tells your team chat who just came in. A shared list for every new group: New Contact Group fires when a group is created in Nerv, so a spreadsheet or another tool can keep a record of how your contacts are organized.
What Zapier does not do here is just as clear. Nerv has no action, so no Zap can write into Nerv: you cannot create, edit or move a contact in it from another app. It has no search either, so a Zap cannot look up a Nerv contact on the way. And contacts that were in Nerv before you published the Zap are never sent.
For a view of Zapier itself, see our Zapier review, or our Zapier alternatives if you want to weigh other platforms.
Zapier vocabulary in one minute
Seven words you will see in the editor. The page uses each one as defined here.
- Zap
- The automation you build: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap, here a new contact or a new contact group in Nerv. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, in another app since Nerv has none.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
- Instant vs polling trigger
- An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
What a Nerv Zap really costs
Nerv is not a premium app on Zapier, so it is open from the free plan. The bill depends on tasks and on how many steps your Zap has.
- Premium appNo, available on the free plan
- Free plan tasks100 per month
- Free plan ZapsUnlimited, two steps each
- Nerv triggers2 instant, 0 polling
The Nerv trigger itself never costs a task. Each action that succeeds counts once, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps: New Contact feeding one action in your CRM fits. Add a second action or a filter and the Zap becomes multi-step, so it needs a paid plan. The interval grid below is for polling triggers; both Nerv triggers are instant, so it does not apply to them.
Connect your Nerv account to Zapier
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. You need a Nerv account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Pick Nerv
Type Nerv in the dialog's search box, select it, then click Add connection. You connect once, and every Zap that starts in Nerv reuses that connection.
- 03
Sign in and grant access
A tab opens on Nerv. Sign in with the account whose contacts you want to send out, then grant Zapier access to it. Back in Zapier, the connection is ready for the trigger step.
Your first Zap: new Nerv contacts in your CRM, with a heads-up
GoalEach contact created in Nerv is added to your CRM, and your team gets a message about it.
- 01
Create the Zap
Start a new Zap, choose Nerv as the app that starts it and New Contact as the event, then select the Nerv connection you made earlier.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts of the connected account, so you map fields on a real contact rather than a blank template.
- 03
Add the CRM step
Add your CRM and its create-contact action, then map the details that came back from Nerv into its fields. Check at the test which fields Nerv actually sends.
- 04
Add the message
Add your team chat and its send-message action, and write a short line with the contact details the test brought back. A second action makes the Zap multi-step, so it needs a paid plan.
- 05
Test and publish
Test each step once and read the results, then click Publish. From then on, every new Nerv contact goes through; the older ones stay in Nerv.
Nerv triggers
2 events start a Zap when something happens in Nerv, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Contact
Instant triggerIn Zapier“Triggers when a new contact is created.”
Starts the Zap whenever a contact is created in Nerv and passes the contact's details to the steps behind it. Nerv has no action of its own, so a Nerv Zap always starts from one of its two triggers, and this one moves the person: the contact leaves the app and goes wherever your follow-up happens.
New Contact Group
Instant triggerIn Zapier“Triggers when a new contact group is created.”
Reacts to a different event: a new contact group, not a new person. It fits when the way you organize contacts in Nerv should also show up in another tool, for example as a new tab, a new list or a quick note to the team.
When a Nerv Zap breaks
Zapier attaches no help article to Nerv. The cases below follow from how every Zap behaves, applied to a contact app.
Each case has a fix you can apply in the editor. For the general method, see our Zapier troubleshooting guide.
Earlier contacts never arrive
A Zap only reacts to what happens after it is switched on. Contacts already in Nerv are not sent, and moving them is a separate import.A flood held back
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.A Zap that sets itself off
A Zap that writes into the place its own trigger watches can start itself again and again and burn through tasks. Check any Zap that writes into a place another trigger watches.
Need help automating Nerv with Zapier?
A person reads every message.
