- Home
- Resources
- Integrations
- Metaview
Metaview Zapier integrationAutomate Metaview with Zapier.
The Metaview Zapier integration gives you 2 triggers, 1 action and 2 searches. A new conversation or a new conversation property in Metaview can start a Zap right away, and other apps can write properties back or look a conversation up. Here is the detail, the cost and the traps.
Verified Trustpilot reviews · AI, automation & growth agency
What the Metaview Zapier integration does for you
Metaview writes recruiting notes for you, so interviewers can focus on the conversation with candidates and hiring teams. Connecting it to Zapier lets those notes leave Metaview on their own: a conversation or a property can start a Zap, and other apps can add properties to a conversation or find one.
Three results, each on a real operation. Notes where the team works: New Conversation starts a Zap once a conversation is available in Metaview, so it can be logged in a spreadsheet or announced in a team channel. Changes that travel: New Conversation Property fires when a property on a conversation is added or updated, so another tool hears about it. Data written back: Create or Update Conversation Property sets a property on a conversation from another app, and Find Conversation or Find Conversation Property fetch what already exists for the next steps.
Both triggers are instant, so the interval of your Zapier plan never slows them. What Zapier does not do for Metaview: there is no action to create a conversation or delete one, and Find Conversation works from a Conversation ID, so an earlier step must already carry one. New Conversation also gives you a choice: let it fire automatically when AI Notes are first generated, or set that to False and push each conversation by hand with Push to Zapier on the AI Notes page. To weigh other platforms on these points, see our n8n vs Zapier and Make vs Zapier comparisons.
Zapier vocabulary in one minute
Eight words from the editor, each explained once here and used as is afterwards.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time that event happens.
- Trigger
- The event that starts the Zap. With Metaview, a new conversation, or a property added or updated on one.
- Action
- What the Zap does once started. With Metaview, creating or updating a property on a conversation.
- Task
- The unit Zapier bills: one action completed successfully. The number on your plan counts those and nothing else.
- Polling vs instant trigger
- Zapier checks a polling trigger on a timer. An instant trigger, like both Metaview triggers, is reported by the app itself.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it otherwise.
- Search step
- A step that looks up something already in an app, so the following steps can use what it found.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes one, on a paid plan.
What a Metaview Zap really costs
Metaview is not a premium app on Zapier, so its triggers, action and searches work on the free plan. You pay in tasks.
- Free plan100 tasks a month, unlimited two-step Zaps
- Metaview triggersBoth instant, free to run
- SearchesMake the Zap multi-step, paid plan
A conversation or a property that starts the Zap costs nothing. Each action that goes through is one task, and a failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps of two steps: one trigger, one action. Adding a filter, a Find Conversation search or a second action makes a multi-step Zap, which needs a paid plan. The grid below shows how often Zapier checks a polling trigger on each plan. It does not apply to the two Metaview triggers, which are instant; it only matters when another app's polling trigger feeds the Metaview action.
Connect your Metaview account in three steps
- 01
Open the Apps page
In your Zapier account, go to Apps and click + Add connection. You need an account on Metaview, plus read or write access on anything you do not own yourself and want the Zap to touch, such as a colleague's conversations.
- 02
Choose Metaview
Search for Metaview in the dialog, pick it and click Add connection. Sign in to Metaview in the tab that opens, with the account whose conversations the Zap should follow.
- 03
Grant access
Approve the access Zapier requests on that account. The connection is stored, and every Metaview step in your Zaps reuses it instead of asking you to sign in again.
Your first Zap: log each interview in a spreadsheet
GoalEvery new Metaview conversation that meets your condition becomes a row in your hiring spreadsheet.
- 01
Pick the trigger
Create a Zap with Metaview and New Conversation. Fill in Trigger on, Private and Label, and decide whether it should fire automatically when AI Notes are generated.
- 02
Test on real conversations
Run the test. Zapier brings back the three most recent items of the connected account; pick one so the next steps are mapped on real values.
- 03
Add a filter
Click the plus icon, add Filter, and set the field to look at, the rule and the value. A text rule only works on text, a number rule only on numbers.
- 04
Add the spreadsheet
Add your spreadsheet as the action with the event that adds a row, then map the values from the conversation into the columns you want.
- 05
Test and publish
Test the action, check the row, then click Publish. With the filter this is a multi-step Zap on a paid plan; without it, it fits the free plan.
Metaview triggers
2 events start a Zap when something happens in Metaview, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
New Conversation
Instant triggerIn Zapier“Triggers when a new conversation is available in Metaview.”
Starts your Zap once a new conversation is available in Metaview, so the conversation can be logged, shared or filed in another tool without anyone pasting it. You label the Zap so it can be recognised on the AI Notes page, and can keep it private.
New Conversation Property
Instant triggerIn Zapier“Triggers when a conversation property is added or updated.”
Fires when a property on a conversation is added or updated, so a change in what Metaview holds about an interview can move on to another app. It follows the data attached to conversations rather than the conversations themselves.
The Metaview action
Metaview gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Create or Update Conversation Property
ActionIn Zapier“Creates or updates a property in a conversation on Metaview.”
Writes a property onto a Metaview conversation, adding it or updating it, with a value coming from another step of the Zap.
Metaview searches
2 search steps look for data that already exists in Metaview, so a later step can use it.
A search step looks up something that already exists in Metaview and hands it to the next steps. Searches sit at the bottom of the Action event list, under SEARCH, and some action fields offer + Add search step to insert one just before. Each search makes the Zap multi-step.
Find Conversation
SearchIn Zapier“Finds a conversation in Metaview by ID.”
Looks up a Metaview conversation from its ID and passes what it found to the following steps.
Find Conversation Property
SearchIn Zapier“Finds a conversation property by name”
Fetches one property of a conversation by its name, so a later step can read the value or decide whether to overwrite it.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that depended on it are skipped. Switched on, the Zap carries on without a result.
- Create X if it doesn't exist yet?On apps that offer it, this box turns a search into a find-or-create. Metaview exposes no find-or-create variant, so its two searches only ever look things up.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a Metaview Zap breaks
Zapier links no help article and no specific limit to Metaview. The cases below come from how every Zap behaves.
Four situations to know before switching a Zap on. If one already misbehaves, see our Zapier troubleshooting guide.
Past conversations are skipped
A Zap only reacts to what happens after it is switched on. Conversations that already existed are not picked up, and moving that backlog into another tool is a separate job.A Zap that sets itself off
A Zap that writes into the very place its own trigger watches can start itself again and again and burn through tasks. Keep what the trigger watches apart from what the Zap writes.A sudden batch held back
After a bulk import or a migration, a trigger that suddenly returns a huge batch can be held back by Zapier's flood protection rather than run for every item.A search that stops the Zap
With its default setting, a Find Conversation or Find Conversation Property that finds nothing stops the Zap, and the steps that depended on it are skipped.
Need help automating Metaview with Zapier?
A person reads every message.



