Metadata Zapier integrationAutomate Metadata with Zapier.
The Metadata Zapier integration gives you 1 trigger, 0 actions and 0 searches. Its single trigger, New Lead, starts a Zap when Metadata records a new lead, so you can pass it to your CRM, a spreadsheet or your team's chat without exporting anything by hand.
Verified Trustpilot reviews · AI, automation & growth agency
What the Metadata Zapier integration does
Metadata is a marketing automation platform that runs B2B campaigns and produces leads. On Zapier it offers one thing: a trigger on each new lead. You build a Zap (the automation you set up on Zapier: one trigger, then one or more actions that run each time the trigger event happens) where Metadata starts and other apps do the work.
A contact that is already in your CRM. New Lead hands each fresh lead to a create-contact step in your CRM, so your team finds it in the tool it already opens.
A log your whole team can read. The same trigger can add one row per lead in a spreadsheet, a simple record that does not need a Metadata login.
A heads-up in the team chat. A message posted for each lead tells the right people something came in, without anyone watching a dashboard.
Know the limits too. Metadata has no action and no search on Zapier, so a Zap never writes to or looks up anything in it; leads only travel out to your other apps. New Lead is a polling trigger, a type the app sets and the editor cannot change, so a lead reaches the Zap at your plan's interval rather than the moment it appears. On the free plan, Zapier checks for new leads every 15 minutes; paid plans check far more often. For more, see our Zapier review.
Zapier words in one minute
Eight terms come back across this page. Here they are in plain words.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event in an app that starts the Zap. For Metadata there is one, New Lead; once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, in another app here.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The Metadata trigger itself never uses one.
- Polling trigger
- A trigger Zapier checks on a timer: it asks the app for new items at a fixed interval and keeps only what it has not seen yet.
- 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 second action or a filter makes one, and it then needs a paid plan.
- Connection
- Your Metadata account linked to Zapier once, then reused by every Zap that starts from New Lead.
What it really costs you
Zapier bills in tasks, and New Lead never costs one. Checking Metadata for new leads is free too, however often Zapier looks.
- New Lead trigger0 tasks
- Each successful action1 task
- Free plan100 tasks a month, two-step Zaps
- Premium appNo, works on the free plan
What counts is the action that follows: each one that succeeds is one task, and one that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps, each held to two steps, so New Lead plus one action fits. A filter or a second action makes the Zap multi-step, which needs a paid plan. Metadata is not a premium app. The grid below sets how often Zapier checks New Lead on each plan.
Connect your Metadata account
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. Type Metadata in the search box of the dialog, pick it, then click Add connection.
- 02
Sign in and grant access
A tab opens on Metadata. Sign in there 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.
- 03
Reuse it in every Zap
The account is now linked to Zapier once. Every Zap you start from New Lead, today or later, picks that same connection from the list instead of asking you to connect Metadata again.
Your first Zap: only the right leads go to the CRM
GoalCreate a CRM contact for each new Metadata lead that meets a condition you choose, and leave the others out.
- 01
Build the trigger
Start a new Zap, choose Metadata as the app that starts it and New Lead as the event, then select the Metadata connection you just made.
- 02
Test on real leads
Run the trigger test. Zapier brings back the three most recent items of the connected account, so you see which details a lead really carries before mapping anything.
- 03
Add the filter
From the plus icon, add Filter and set its three boxes: the field to look at, the rule, and the value to compare with. Use a text rule on text. This makes the Zap multi-step, so a paid plan.
- 04
Add your CRM
Add your CRM with its create-contact action, connect it, and map the lead details you saw at the test into its fields. Test that step once and read what came back.
- 05
Publish
Publish the Zap to switch it on. From then on Zapier checks for new leads at your plan's interval, and each contact created is one task. For a guided start, see our Zapier training.
The trigger
1 event starts a Zap when something happens in Metadata. Zapier checks for them at the interval your plan allows.
New Lead
Polling triggerIn Zapier“Trigger when a new lead is created.”
Starts your Zap each time Metadata creates a new lead, and hands that lead to the steps you add after it, in whatever app you send it to.
When it breaks
Zapier links no help article to Metadata. What follows is the general behaviour of a Zap built on a polling trigger.
These four cases are the general limits of a lead Zap. If yours still misbehaves, see our Zapier troubleshooting guide.
Old leads never arrive
A Zap only reacts to what happens after it is switched on. Leads that already existed are never picked up; moving that backlog is a separate job.A lead that seems late
New Lead is checked at your plan's interval, every 15 minutes on Free. A lead created just after a check waits for the next one.No duplicates, by design
Zapier keeps track of what it has already seen on a polling trigger, so the same lead does not start the Zap twice, even across checks.A sudden flood 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.
Need help automating Metadata with Zapier?
A person reads every message.
