Nimbata Zapier integrationAutomate Nimbata with Zapier.
The Nimbata Zapier integration gives you 2 triggers, both instant, and 0 actions, with no search step: Nimbata always starts the Zap and another app does the work. Below, what each trigger does, what it costs, how to connect and where a Zap stops.
Verified Trustpilot reviews · AI, automation & growth agency
What the Nimbata Zapier integration does for you
Nimbata is a call tracking platform: it ties each phone call back to the search, page, ad or campaign that produced it. On Zapier it only speaks first. A completed call or a submitted activity form starts the Zap, and the next steps happen in your other apps.
Three results you can build with the two triggers. First, a call log that keeps itself: New Call starts a Zap when an inbound call to one of your tracking numbers is completed, and its post-call fields go into a sheet. Second, form leads with their origin attached: Form Submitted fires when an activity form is sent, carrying the source, medium, campaign and landing page along with the form's own answers, so the lead lands in your other tool with its context. Third, an alert for the team: either trigger can be followed by a message in the tool your team already reads.
What Zapier does not do with Nimbata: there is no action and no search, so a Zap can never create, change or look up anything inside Nimbata. It only listens and reports. Every action in a Nimbata Zap belongs to another app. Nimbata is not a premium app, so a two-step Zap with one of its operations runs on the free plan.
If you are still weighing tools, open our n8n vs Zapier comparison.
Zapier words in one minute
Eight words keep coming back below. Here they are in plain English, once.
- 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. With Nimbata, it is a completed call or a submitted activity form.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, here in another app.
- Task
- The unit Zapier bills: one action your Zap completed successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Search step
- A step that finds something already stored in an app so later steps can use it. Nimbata offers none on Zapier.
- 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 Nimbata Zap really costs
Nimbata is not a premium app, so it works on the free plan. Its triggers never cost a task: only the actions that follow, in other apps, are counted when they succeed.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- What countsEach successful action, never the trigger
Each successful action counts on its own, so logging a call and then posting an alert uses two tasks per call. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each with two steps: one trigger and one action. A filter or a second action makes it a multi-step Zap, which needs a paid plan.
The grid below is how often Zapier checks a polling trigger on each plan. It does not apply to Nimbata's two triggers, which are both instant.
Connect Nimbata to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open Apps and click + Add connection. A connection is your Nimbata account linked to Zapier once, then reused by every Zap that starts from Nimbata.
- 02
Find Nimbata
Search for Nimbata by name in the dialog, select it, then click Add connection. A new tab opens so you can sign in to your Nimbata account and finish the link.
- 03
Sign in and grant access
Sign in and grant Zapier access to the account. You need an account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Nimbata Zap, step by step
GoalWhen an activity form is submitted in Nimbata, keep only the ones that meet your condition, then add a row to your spreadsheet.
- 01
Create the Zap
Start a new Zap, pick Nimbata as the app that starts it and Form Submitted as the event. Choose your Nimbata connection; this trigger has no required field to fill.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from the connected account, so you see real submissions and the values they actually carry.
- 03
Add the filter
Add a Filter step from the plus icon, then set its three boxes: the field to look at, the rule and the value. A filter makes this a multi-step Zap, so it needs a paid plan.
- 04
Add the spreadsheet row
Add your spreadsheet step and map into its columns the values the test brought back, such as the campaign or the landing page. Check at the test what each column receives.
- 05
Test, then publish
Run each step once and read what came back. When the row looks right, click Publish to switch the Zap on. Our Zapier training is there if you want to go further.
Nimbata triggers on Zapier
2 events start a Zap when something happens in Nimbata, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Form Submitted
Instant triggerIn Zapier“Triggers when an Activity Form is submitted. It includes source, medium, campaign, landing page, and the form's own field values.”
Starts your Zap when someone submits a Nimbata activity form, and passes on the source, medium, campaign and landing page together with the answers given in the form.
New Call
Instant triggerIn Zapier“Triggers when an inbound call to one of your tracking numbers is completed. It includes post call fields (e.g. Caller ID, Source, Duration, etc.”
Fires once an inbound call to one of your tracking numbers is completed, and hands Zapier the post-call fields that come with it.
When a Nimbata Zap stops working
Zapier does not attach a help article to Nimbata, and no limit specific to the app is documented. What remains are three general rules that apply to every Zap.
Keep them in mind before you rely on the Zap. If a run fails anyway, see our Zapier troubleshooting guide.
Nothing before the switch-on
A Zap only reacts to what happens after you publish it. Calls and forms Nimbata recorded earlier are not picked up, and moving that history is a separate job.A sudden flood
If a trigger suddenly sends a huge batch, after a bulk import or a migration for example, Zapier's flood protection can hold those runs back.A Zap that sets itself off
As a general precaution: a Zap that writes into the place its own trigger watches can start itself again and again, and use up tasks fast.
Need help automating Nimbata with Zapier?
A person reads every message.
