Mica Zapier integrationAutomate Mica with Zapier.
Mica Zapier integration: 0 triggers, 1 action and 0 searches. Mica cannot start a Zap, but any Zap can hand it a recorded sales call so it builds the landing page you share with the prospect. Here is how that one step works, what it costs and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mica Zapier integration does for you
The integration lets a Zap send your recorded sales calls to Mica. Mica turns a call into a personalised landing page that helps close the deal, and you share that page with the prospect. On Zapier, Mica offers a single action and no trigger, so the Zap always starts in another app.
A page for every recorded call. When a new recording lands in your cloud storage, Create New Landing Page sends its download link to Mica, and the page gets built without anyone uploading the file by hand.
Only the calls that matter. Put a filter between the storage and Mica, so only the recordings that meet your rule reach the action and spend a task.
A list your team already keeps. If reps paste recording links into a spreadsheet, a new row can be the trigger, and the link goes straight into the Video Download URL field.
Mica is not a premium app: a Zap made of one trigger and Create New Landing Page runs on the free plan, and each page built counts one task.
What Zapier does not do here: Mica has no trigger, so a Zap cannot react to a finished landing page or pass it on; it has no search either, so a Zap cannot look up an existing page. To weigh Zapier against other tools, open our n8n vs Zapier comparison or see our Zapier review.
Zapier words, in plain English
Eight terms you will meet on this page. One line each.
- Zap
- Your automation on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts the Zap. Mica has none, so it always comes from another app, such as your storage.
- Action
- What the Zap does once started: the step that writes, sends or moves something. Here, Create New Landing Page.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan counts those.
- Polling trigger
- A trigger Zapier checks on a timer, asking the app for new items and keeping only the ones it has not seen before.
- Instant trigger
- A trigger the app reports itself: it calls Zapier the moment the event happens, so nothing waits for a check.
- 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 filter or a second action makes one, and it then needs a paid plan.
What a Mica Zap really costs
The trigger in the other app never costs a task. Only a completed action is billed: each Create New Landing Page that goes through counts one task, and one that fails costs nothing.
- TriggerNever counted
- Each landing page created1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
Mica is not a premium app, so it works on the free plan: 100 tasks a month and unlimited Zaps, each limited to two steps, one trigger and one action. A recording trigger followed by Mica fits exactly. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The grid below is how often Zapier checks a polling trigger; it applies to the app that starts the Zap, if its trigger polls.
Connect Mica to Zapier in three steps
- 01
Open the Apps page
In your Zapier account, open the Apps page and click + Add connection. A connection is your Mica account linked once, then reused by every Zap that sends calls to Mica.
- 02
Pick Mica
Search for Mica in the dialog, pick it and click Add connection. 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.
- 03
Sign in and grant access
Sign in to Mica in the tab that opens, then grant Zapier access to the account. Back in the editor, pick that connection on the Create New Landing Page step.
Your first Zap: a landing page for the calls you choose
GoalEach new recording in your cloud storage starts the Zap, a filter keeps only the ones that match your rule, and Mica builds the landing page.
- 01
Set the trigger
Create a new Zap and pick your cloud storage as the app that starts it, with the event that reports a new file. Choose your connection to that app.
- 02
Test it on a real file
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real recording. Read what came back.
- 03
Add the filter
Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule and the value. This step makes the Zap multi-step, so it needs a paid plan.
- 04
Add Create New Landing Page
Add Mica with Create New Landing Page and map the recording's download link into Video Download URL. Check at the test that the link points to the video file itself.
- 05
Test, then publish
Test the action once and read what came back. Then click Publish to switch the Zap on. For a guided practice run, see our Zapier training.
The Mica action
Mica gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Create New Landing Page
ActionIn Zapier“Sends your meeting recording to Mica to create the landing page”
Sends a meeting recording to Mica, which builds the landing page from it. It requires a Video Download URL, which the field's note describes as most commonly a link to an mp4 file.
When a Mica Zap breaks
Zapier links no help article to Mica, so the cases below are Zapier's general limits. They apply to the Zap around Mica.
These cases cover the general limits, mostly on the trigger side, since Mica only acts. When a run fails and the reason is not obvious, see our Zapier troubleshooting guide.
Old recordings are not picked up
A Zap reacts only to what happens after you switch it on. Recordings already in your storage never reach Mica; sending that backlog is a separate job.A Zap that sets itself off
A general precaution: a Zap that writes into the place its own trigger watches can start itself again and again and burn through your tasks. Check at the test that no later step writes where the trigger watches.A bulk upload is held back
After a bulk import or a migration, a trigger that returns a huge batch at once can be held back by Zapier's flood protection.The same recording is sent once
On a polling trigger, Zapier keeps track of what it has already seen, so the same item does not start the Zap twice.
Need help automating Mica with Zapier?
A person reads every message.
