Magnetis Zapier integrationAutomate Magnetis with Zapier.
The Magnetis Zapier integration offers 1 trigger, 0 actions and 0 searches. Every incoming call on your tracked numbers, missed or answered, can start an automation that carries the call into your CRM, a spreadsheet or a team chat.
Verified Trustpilot reviews · AI, automation & growth agency
What the Magnetis Zapier integration is good for
Magnetis tracks the calls that reach your numbers. On Zapier it does one thing: it starts Zaps, the automations you build there, each time a call comes in. The call then travels to whatever app you pick for the next step. Magnetis itself only sends; nothing gets written back into it.
Three results come out of New Incoming Call. A call log your team actually reads: each call becomes an activity or a note in the CRM, where the sales team already looks. An alert on missed calls: a filter keeps only the calls nobody picked up and posts them to a team chat, so someone calls back. A running spreadsheet of calls: one row per call, ready to be sorted and shared outside Magnetis.
Each of these starts from the same event, and both missed and answered calls fire it, so the filter is what turns a raw call feed into something useful.
What Zapier does not do here matters just as much. There is no action, so a Zap cannot create, edit or tag anything inside Magnetis. There is no search either. The channel and campaign analysis that Magnetis is built for stays in Magnetis: Zapier only moves the calls one by one. And the single trigger is a polling one, so calls arrive with the delay of your plan, not the instant they ring. See also our Zapier review.
Zapier vocabulary in one minute
Seven words cover what you will see on screen. Each one, once, in plain English.
- Zap
- One automation: a starting event in one app, then one or more steps that run each time that event happens.
- Trigger
- The event that starts a Zap. With Magnetis there is only one: a new incoming call on a tracked number.
- Action
- What the Zap does once started. Magnetis offers none, so every action of your Zap belongs to another app.
- Task
- The unit Zapier bills: one action that went through. The allowance of your plan is counted in tasks.
- Polling trigger
- A trigger Zapier checks on a timer, keeping only what is new. New Incoming Call works this way.
- Filter
- A step that lets the Zap continue only when the incoming data meets your condition, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes one, and it needs a paid plan.
What the Magnetis Zapier integration costs
Magnetis is not a premium app, so it runs on the free plan. You pay in tasks, and only the actions in your other apps produce them.
- Premium appNo, free plan works
- Trigger typePolling
- Free plan100 tasks a month, two-step Zaps
- BilledEach action in the next app that succeeds
New Incoming Call costs nothing, and Zapier checking for new calls costs nothing either, however often it looks. Each action that completes after it counts one task; a failed one counts nothing. The free plan gives 100 tasks a month and two-step Zaps, so a filter on missed calls already needs a paid plan. Because the trigger is polling, the grid below decides how long a call may wait before Zapier picks it up.
Connect Magnetis to Zapier in 3 steps
- 01
Open the Apps page
In Zapier, go to the Apps page of your account and click + Add connection. You need a Magnetis account, plus read access to the tracked numbers you want the Zap to follow.
- 02
Pick Magnetis
Search for Magnetis in the dialog, select it from the results and click Add connection. A new browser tab then opens so you can sign in on the Magnetis side.
- 03
Sign in and grant access
Log in to Magnetis in that tab and allow Zapier to read the account. The connection is saved, and every Zap that starts from a Magnetis call reuses it.
Your first Zap: missed Magnetis calls posted to your team chat
GoalCalls that meet your condition, such as unanswered ones, are posted to a team chat channel so someone calls back.
- 01
Create the Zap
Start a new Zap, pick Magnetis as the app that starts it and New Incoming Call as the trigger, then choose your Magnetis connection.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent calls of your tracked numbers, so you can build the next steps on a real one.
- 03
Add the filter
Add a Filter step and fill its three boxes: the field to look at, the rule, the value to compare with. The filter makes the Zap multi-step, so it needs a paid plan.
- 04
Add the chat message
Add the send-message action of your team chat, choose the channel and drop the call details that come from Magnetis into the message body.
- 05
Test and publish
Test the message, check it in the channel, then publish the Zap. Zapier will look for new calls at the interval of your plan.
The Magnetis trigger
1 event starts a Zap when something happens in Magnetis. Zapier checks for them at the interval your plan allows.
New Incoming Call
Polling triggerIn Zapier“Triggers when an incoming call (missed or answered) is received on your tracked numbers.”
Starts your Zap for each call received on one of your tracked numbers. It does not wait for a conversation: a missed call counts just as much as an answered one, which is exactly what lets you build callback alerts or a full call log in another tool.
When a Magnetis Zap breaks
Zapier ties no help article to Magnetis, so the weak points are Zapier's general limits plus the shape of the trigger.
None of them throws an alarm. You notice a call missing from the CRM, or a chat flooded with alerts. To track the cause, see our Zapier troubleshooting guide.
Past calls never arrive
A Zap only reacts to what happens after it is switched on. Calls received before that stay in Magnetis; moving that history is a separate job.Too many alerts
Missed and answered calls both start the Zap. Without a filter, every ring on every tracked number ends up in the next app and costs a task.A burst held back
When the trigger suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those items back instead of running them all.No double runs on one call
On a polling trigger Zapier remembers what it has already seen, so the same call does not start the Zap twice. A duplicate is worth checking at the source first.
Need help automating Magnetis with Zapier?
A person reads every message.
