PhoneTapify Zapier integrationAutomate PhoneTapify with Zapier.
The PhoneTapify Zapier integration has 1 trigger and no action: it hands every new contact from your NFC digital profile to the rest of your tools. Below, what that trigger does, what it costs, how to connect it and where it can trip you up.
Verified Trustpilot reviews · AI, automation & growth agency
What the PhoneTapify Zapier integration does
PhoneTapify gives people and businesses a digital profile they share with a tap of an NFC card or phone, and that profile collects contact details from the people met along the way. The Zapier integration takes each of those new contacts and sends it to another app, so nothing stays stuck inside PhoneTapify.
Three results come out of that single trigger. A CRM that fills itself after a trade show: every visitor who leaves their details on your profile becomes a contact in your sales tool, through New Connection. A follow-up that does not wait for you: the same trigger feeds your email tool, which sends the thank you message. A shared list the whole team sees: each new contact lands as a row in a spreadsheet, so the person who met them is not the only one who knows.
Now the limits. PhoneTapify only works as a starting point in Zapier: there is no action, so no Zap can write into PhoneTapify, update a profile or add a contact to it. There is no search either. And the one trigger is not instant: Zapier checks PhoneTapify at the interval of your plan, so a contact collected now arrives a little later, never on the spot.
If you are deciding whether Zapier is the right tool at all, the Zapier review and Zapier alternatives pages are the next stops.
Zapier vocabulary, the short version
A handful of Zapier words do all the work on this page. One line each, then they are used as is.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event takes place.
- Trigger
- The event that starts the Zap. For PhoneTapify it is a new contact on your profile; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does after it starts: the step that writes, sends or moves something for you. With PhoneTapify, it always runs in another app.
- Task
- What Zapier bills: one action your Zap completes successfully. The number on your plan counts those, not triggers or checks.
- Polling vs instant
- A polling trigger is checked on a timer, Zapier asking the app for new items. An instant one is reported by the app the moment it happens.
- Filter
- A step that lets the Zap continue only when what arrived meets a condition you set, and stops it there the rest of the time.
- Connection
- Your account of an app linked to Zapier once, then reused by every step that uses that app. Not the same thing as a PhoneTapify contact.
What a PhoneTapify Zap costs
Zapier bills tasks, one per action that works. The PhoneTapify trigger costs nothing, however often Zapier checks your profile for new contacts.
- Free plan100 tasks a month, unlimited Zaps
- Zap size on freeTwo steps: one trigger, one action
- Trigger checksNever billed, whatever the interval
- Premium appNo, PhoneTapify works on the free plan
A Zap that sends each new contact to one other app costs one task per contact. Add a second action, say an email after the CRM, and each contact costs two. An action that fails is not counted. PhoneTapify is not a premium app, so it runs on the free plan, which builds two-step Zaps only: one trigger, one action. A filter or a second action makes the Zap multi-step, and that needs a paid plan. The trigger checks themselves never count.
Connect your PhoneTapify account to Zapier
- 01
Open your app connections
In Zapier, open the Apps page of your account and click + Add connection. You link PhoneTapify once here, and every Zap that starts from your profile reuses that link.
- 02
Find PhoneTapify
Type PhoneTapify in the search box of the dialog, pick it, then click Add connection. You need a PhoneTapify account with a profile already set up: Zapier does not create one.
- 03
Sign in and allow access
A tab opens on PhoneTapify. Sign in with the account that owns the profile, then grant Zapier access. If the profile belongs to a colleague or to the company, you need access rights on it first.
Your first PhoneTapify Zap
GoalEvery new contact from your digital profile that meets your condition becomes a contact in your CRM.
- 01
Create the Zap, set the trigger
Start a new Zap, choose PhoneTapify as the app and New Connection as the event, then pick the PhoneTapify connection you added earlier.
- 02
Test with real contacts
Run the test. Zapier brings back the three most recent contacts collected by your profile, so you can map the next step on a real one. Share your profile once beforehand if it is still empty.
- 03
Add a filter if you need one
Click the plus icon, choose Filter, then set the field, the rule and the value. Use a text rule on text. This step makes the Zap multi-step, which means a paid plan; skip it on the free one.
- 04
Add the action in your other app
Pick the app that should receive the contact, its action, then map what PhoneTapify brought back into its fields. Run the action test and check the result in that app.
- 05
Publish
When the test looks right, click Publish to switch the Zap on. From then on, each new contact goes through it at the next check.
The PhoneTapify trigger
1 event starts a Zap when something happens in PhoneTapify. Zapier checks for them at the interval your plan allows.
New Connection
Polling triggerIn Zapier“Triggers when you get a new connection via your PhoneTapify digital profile.”
Starts the Zap each time someone gets in touch through your PhoneTapify digital profile and becomes a new contact for you. Despite the name, it has nothing to do with the Zapier connection that links your account: here a connection is a person you met.
When a PhoneTapify Zap breaks
Zapier lists no help article and no specific limit for PhoneTapify. What can go wrong is what goes wrong on any polling trigger, in four cases.
Each case below comes from the way Zapier itself works. If a run still fails, the Zapier troubleshooting page is where to start.
Earlier contacts never show up
A Zap only reacts to what happens after you switch it on. Contacts collected before that stay in PhoneTapify; moving them is a separate job.A big batch gets held back
If the trigger suddenly returns a huge batch of contacts, say after a large event, Zapier's flood protection can hold it back instead of running it all.The same contact is not sent twice
On a polling trigger Zapier keeps track of what it has already seen, so one contact does not start the Zap a second time at the next check.A filter that never lets anything through
Filter rules are typed: a text rule only works on text, a number rule only on numbers. Pick the wrong one and the filter never passes, so no contact goes further.
Need help automating PhoneTapify with Zapier?
A person reads every message.
