Resources · Zapier integration

Metorik Zapier integrationAutomate Metorik with Zapier.

The Metorik Zapier integration gives you 4 actions, 0 triggers and 0 searches. Every Zap therefore starts in another app and ends in Metorik. It is not one of the apps Zapier keeps for paid plans, so the free plan runs it, one trigger and one action per Zap.

See the 4 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Metorik Zapier integration does for you

It lets your other apps write into Metorik, the email marketing and analytics platform for online stores, without exports and imports. You build a Zap (the automation itself: one trigger, then one or more actions that run every time the trigger event happens). Here the trigger always comes from another app, and Metorik receives the result.

Three results worth building. Profiles that arrive on their own: a sign-up form elsewhere runs Create/Update Profile, so the person exists in Metorik before your next campaign. Opt-outs that travel: when someone asks to stop receiving emails in another tool, Create/Update Unsubscribe records it in Metorik too. Clean-up on request: a deletion request logged in a spreadsheet feeds Delete Profile, so nobody has to hunt for the record by hand.

Now the limits. Metorik has no trigger on Zapier: nothing that happens inside Metorik can start a Zap, so it cannot send its own data to another app this way. It has no search either, so a Zap cannot look up an existing profile before acting. The four actions cover profiles and unsubscribes, and that is the whole list. Each one is keyed on an email address, the only field they all require.

If those limits matter for your setup, open our n8n vs Zapier comparison, and see our Zapier review before you commit.

Vocabulary

Zapier words, in plain English

Six words come back all over this page. Here they are once, in everyday language.

Trigger
The event in an app that starts the Zap. For Metorik it always lives in another app, which Zapier waits on.
Action
What the Zap does once it has started: here, the step that writes a profile or an unsubscribe into Metorik.
Task
The unit Zapier bills: one action your Zap completes successfully. The number on your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer: it asks the app for new items and keeps only what it has not seen yet.
Instant trigger
A trigger the app reports itself, the moment the event happens, so nothing waits for the next check.
Filter
A step that lets the Zap carry 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.
Cost

What a Metorik Zap really costs

Zapier bills tasks, and only actions make tasks. The trigger in the other app costs nothing, however often Zapier checks it.

  • Trigger checksFree, whatever the interval
  • Free plan100 tasks a month, unlimited Zaps, two steps each
  • MetorikAvailable on the free plan
  • Failed actionNot counted

Each Metorik action that succeeds counts once; one that fails is not counted. The free plan gives 100 tasks a month and as many Zaps as you like, each limited to two steps. That fits a form feeding Create/Update Profile perfectly. Add a filter to keep only some sign-ups, and the Zap becomes multi-step, which needs a paid plan. Metorik has no trigger, so the interval grid below applies to the trigger of the app that starts your Zap when that trigger is a polling one, and not at all when it is instant.

Connect

Connect Metorik to Zapier

  1. 01

    Open your connections

    In Zapier, open the Apps page of your account and click + Add connection. A connection is your Metorik account linked once, then reused by every Zap step that writes into it.

  2. 02

    Find Metorik

    Search for Metorik in the dialog, pick it and click Add connection. You need an account on Metorik, plus read or write access on anything you do not own yourself and want the Zap to touch.

  3. 03

    Sign in and grant access

    Sign in to Metorik in the tab that opens, with the account whose store data the Zap should change, then grant Zapier access. Every Metorik action in your Zaps can then use this connection.

First Zap

Your first Zap: qualified sign-ups become Metorik profiles

GoalEach form submission that meets your condition creates or updates a profile in Metorik.

  1. 01

    Create the Zap

    Create a Zap and pick your form tool as the trigger app, with its new-submission event. Three steps make a multi-step Zap, so this one needs a paid plan.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent submissions from the connected account, so you set up the next steps on a real one, email included.

  3. 03

    Add the filter

    Click the plus in the editor and pick Filter. Fill the three boxes: the field to look at, the rule and the value. A text rule only works on text, so pick the type that matches the field.

  4. 04

    Add the Metorik step

    Pick Metorik and Create/Update Profile. Map the email from the form into the required email field, then add the other details you want the profile to carry.

  5. 05

    Test, then publish

    Test the Metorik step and check the profile in your account. When it looks right, publish the Zap to switch it on. Only submissions sent after that will reach Metorik.

Actions

Metorik actions on Zapier

Metorik gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create/Update Unsubscribe

Action

In Zapier“Creates or updates an unsubscribe.”

Records an unsubscribe for an email address in Metorik, or updates the one already there, from whatever app the request came through.

When to use it
a customer asks to stop receiving emails through a form in another app, and that request should reach Metorik without anyone copying it over.
Watch out
the email field is required, so the step before must carry one you can map.
2

Create/Update Profile

Action

In Zapier“Creates or updates a profile.”

Writes a profile into Metorik, creating it or updating an existing one, so a contact gathered elsewhere is ready for your segments.

When to use it
a newsletter sign-up on a landing page should become a Metorik profile without an export in between.
Watch out
email is the only required field. Check at test whether the run updated an existing profile or created a new one.
3

Delete Profile

Action

In Zapier“Deletes a profile.”

Removes a profile from Metorik, identified by the email address of the profile to delete.

When to use it
your team logs deletion requests in a shared spreadsheet, and each new row should take the matching profile out of Metorik.
Watch out
the required email must point to the profile you mean to remove, so check the mapping at test before you publish the Zap.
4

Delete Unsubscribe

Action

In Zapier“Deletes an unsubscribe.”

Takes an unsubscribe off an email address in Metorik, the reverse of the first action on this list.

When to use it
a customer who opted out later ticks a consent box again on a form, and the old opt-out should be lifted.
Watch out
the email field is required; make sure the email you map is the one that was unsubscribed, and check the result at test.
When it breaks

When a Metorik Zap breaks

Zapier attaches no help article to Metorik, and no limit specific to the app is on record. What goes wrong is the usual Zapier ground, seen from the receiving end.

Here are the general limits to know. If a Zap halts for no visible reason, see our Zapier troubleshooting guide.

  • Earlier sign-ups never reach Metorik

    A Zap only reacts to what happens after you switch it on. Contacts collected before that stay in the other app; moving that backlog is a separate job.

  • A Zap that keeps restarting

    As a general precaution, a Zap that writes into the place its own trigger watches can set itself off again and burn through your tasks.

  • A bulk import stalls

    When the starting app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold it back.

  • The same item does not run twice

    On a polling trigger, Zapier keeps track of what it has already seen, so the same item never starts the Zap a second time.
Need help

Need help automating Metorik with Zapier?

A person reads every message.

FAQ

Metorik and Zapier: common questions

01Is the Metorik Zapier integration free?
Yes, within the free plan's limits. Metorik is not one of the apps Zapier reserves for paid plans, so a free account can use its four actions. The free plan gives 100 tasks a month and an unlimited number of Zaps, each built from one trigger and one action. A form feeding Create/Update Profile fits inside that. Add a filter or a second action, and the Zap becomes multi-step, which requires a paid plan.
02How many tasks does a Metorik Zap use?
One task each time a Metorik action completes. The trigger in the other app costs nothing, and neither do the checks Zapier makes to find new items. A two-step Zap that creates a profile uses one task per run; a Zap that also records an unsubscribe in a second action uses two. A Metorik action that fails is not counted against your plan. Note also that a few apps and a few actions take more than one task when they complete, so read the count after your first runs.
03Does Metorik work in real time with Zapier?
That depends on the app that starts the Zap, because Metorik has no trigger of its own. If the starting trigger is a polling one, Zapier checks it at your plan's interval: 15 minutes on Free, 2 minutes on Professional, 1 minute on Team and Enterprise. If it is an instant trigger, it fires straight away whatever the plan, and the editor marks it with a lightning bolt. Check which kind your starting app offers.
04What is needed to connect Metorik to Zapier?
An account on Metorik, plus read or write access on anything you do not own yourself and want the Zap to touch. From the Apps page of Zapier, click + Add connection, search for Metorik, pick it and click Add connection. Sign in to Metorik in the tab that opens and grant access. The connection is then reused by every Metorik step, so you set it up once per account and every later Zap can pick it.
05Can Metorik start a Zap or look up a profile?
No to both. Metorik has no trigger on Zapier, so nothing happening inside Metorik can kick off a Zap, and it has no search, so a Zap cannot check whether a profile exists before acting. What it offers is four actions on profiles and unsubscribes, each keyed on an email. If you need Metorik data to flow out to another tool, this integration does not cover that direction, whatever plan you are on.
06What if the Metorik action you need is not available?
Look at the Metorik page on Zapier, which shows the current list of actions. Today it holds four: create or update a profile, delete a profile, create or update an unsubscribe and delete an unsubscribe. Nothing else is offered, not even an advanced request action. If your need sits outside those four, Zapier alone will not cover it with this app, and the next step is to look at other tools.
07Zapier, Make or n8n for Metorik?
Compare them on criteria, not on a ranking. Direction: on Zapier, Metorik only receives data, through four actions, and never sends any. Starting point: your Zap begins in another app, so check that this app is on the tool you pick and what kind of trigger it has. Cost: Zapier bills completed actions as tasks, and the free plan stops at two steps. Weigh those three against what you actually need to automate.
Same platform

Other docs you might need on this stack.

Browse all integrations