Resources · Zapier integration

Matajer Zapier integrationAutomate Matajer with Zapier.

The Matajer Zapier integration offers 5 triggers, 4 actions and 0 searches. Zapier watches your Matajer store for new orders, customers and products, and can write back: create, update or delete a product, or move an order to its next status.

See the 9 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Matajer Zapier integration does

Matajer is a platform for building a complete online store. Connected to Zapier, it works in both directions: five triggers watch orders, customers and products, and four actions let a Zap create, change or delete a product, or set an order's status. Zapier checks the store at the interval of your plan.

Three results people build with it. An order log outside the store: New Order adds each order to a spreadsheet, so whoever packs parcels works from one list. A catalog fed from a sheet: Create Product turns a new row into a product in the store, with its SKU, price and image. A status that follows the work: Update Order Status moves an order to ready or delivering when another tool says it is done.

What Zapier does not do here: there is no search. A Zap cannot look up a product or an order by name; Update Product, Delete Product and Update Order Status all need the ID, which has to come from an earlier step. All five triggers are polling triggers, so nothing is instant: on the free plan, a new order reaches your other tool at the next check, every 15 minutes.

Two details to know before you start. Product names and descriptions are asked in Arabic, and both are required. And Matajer refuses to create a product once your package limit is reached. If you want a second pair of hands on a store flow like this, see our Zapier agency page.

Vocabulary

Zapier vocabulary in one minute

Eight words that come back throughout this page.

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, such as a new Matajer order. Once the Zap is on, Zapier waits for it.
Action
What the Zap does after it starts: the step that writes, sends or moves something, such as a product created in Matajer.
Task
The unit Zapier bills: one action the Zap completes successfully. Your plan's monthly count is a count of these.
Polling trigger
A trigger Zapier checks on a timer, asking the app for new items at a fixed interval. All five Matajer triggers are polled.
Instant trigger
A trigger the app reports itself, the moment the event happens. Matajer has none of these on Zapier.
Filter
A step that lets the Zap carry on only when what arrived 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 it one, and it then needs a paid plan.
Cost

What a Matajer Zap costs

Matajer is not a premium app, so it works on the free plan. Watching for new orders or products costs nothing, however often Zapier checks: only an action that succeeds is billed, whether it runs in Matajer or in another tool.

  • Free plan100 tasks a month, unlimited Zaps, two steps each
  • Premium appNo
  • Matajer triggers5, all polling
  • Matajer actions4, each one task when it succeeds

One order logged in a sheet is one task. A Create Product that fails, because your package limit is reached or a required field is empty, is not counted. On the free plan you get 100 tasks a month and Zaps of two steps; a filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below sets how fast a new order or customer reaches the Zap, from 15 minutes on Free down to 1 minute on Team and Enterprise.

Connect

Connect Matajer to Zapier

  1. 01

    Open your connections

    Go to the Apps page of your Zapier account and click + Add connection. You need a Matajer account, plus read or write access on anything in the store you do not own yourself and want the Zap to touch.

  2. 02

    Pick Matajer

    Search for Matajer in the dialog, select it, then click Add connection. A new browser tab opens on the Matajer side so you can finish linking the store.

  3. 03

    Sign in and grant access

    Log in to Matajer in that tab and allow Zapier to reach the store. The connection is saved once and reused by every Matajer trigger and action in your Zaps.

First Zap

Your first Zap: every new order in a spreadsheet

GoalEach time a new order arrives in your Matajer store, keep only the orders that meet one condition, then add a row to your spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap, pick Matajer as the app that starts it and New Order as the event, then select your Matajer connection.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent orders from the store, so you map the next steps on a real one. Check at the test which order details come through.

  3. 03

    Add a filter

    From the plus icon, add a Filter and set the field, the rule and the value. Rules are typed: a number rule only works on numbers. The filter makes this a multi-step Zap.

  4. 04

    Add the spreadsheet action

    Choose your spreadsheet app and its add-a-row action, then map the order details from the trigger into the columns you want filled. If the test shows an order ID, keep it: other Zaps will need it.

  5. 05

    Test, then publish

    Run each step once and read what came back. Then click Publish. New orders reach the sheet at each check, every 15 minutes on Free, and each one costs a task.

Triggers

The 5 Matajer triggers

5 events start a Zap when something happens in Matajer. Zapier checks for them at the interval your plan allows.

1

Deleted Product

Polling trigger

In Zapier“Triggers when an existed product is deleted from Matajer.”

Starts the Zap when a product that existed in your Matajer store is removed, which is the moment other places that list it go out of date.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
mark the product as gone in the spreadsheet you use as a catalog, so nobody quotes an item the store no longer sells.
Watch out
products deleted before the Zap was switched on are not picked up. Check at the test which product details are still returned once it is gone.
2

New Customer

Polling trigger

In Zapier“Triggers when a new customer is created.”

Picks up each customer account created in the store, a different moment from a first order.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
add every new customer to your email tool so the welcome message goes out without anyone exporting a list.
Watch out
Zapier remembers the customers it has already seen, so the same account does not start the Zap twice; earlier customers stay out.
3

New Order

Polling trigger

In Zapier“Triggers when a new order is created.”

Fires on each order placed in your Matajer store, the event a shop owner may want to see in other tools.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
log orders in a spreadsheet or post them in a team chat, so packing starts without opening the store's dashboard.
Watch out
on the free plan an order can wait up to one check before the Zap sees it. Check at the test whether the order ID comes through: Update Order Status needs it later.
4

New Product

Polling trigger

In Zapier“Triggers when a new product is created.”

Reacts when a product is created in the store, the point where your other lists should learn about it.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
keep a catalog sheet in step with the store, one row per product, keeping the product ID if the test shows one, for later updates.
Watch out
a Zap that creates products from a sheet and another that copies new products into the same sheet can feed each other. Keep the two in different places.
5

Updated Order

Polling trigger

In Zapier“Triggers when an existed order is updated in case you need to update order status.”

Runs when an existing order changes, the trigger Matajer points to when a status needs following.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one
When to use it
tell the customer or your team that an order moved on, by passing the new status to your email or chat tool.
Watch out
as a general precaution, a Zap that starts here and changes the order with Update Order Status writes where its own trigger watches, and can restart itself.
Actions

The 4 Matajer actions

Matajer 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 Product

Action

In Zapier“Create a new product in you store at Matajer, note that the process will fail if you have exceeded your package limits”

Adds a new product to your Matajer store from data another app holds, such as a row in a sheet or a form entry.

When to use it
build the catalog in a spreadsheet and let each new row become a product.
Watch out
SKU, Arabic name, Arabic description, price, main image link and the publish choice are all required, and the action fails once your package limit is reached.
2

Delete Product

Action

In Zapier“Used to delete product from Matajer, note that product will be deleted only if there is no related orders.”

Removes a product from the store, using its product ID.

When to use it
clear products you marked as discontinued in your catalog sheet, without opening the dashboard.
Watch out
Matajer only deletes a product that has no related orders. A product that has already sold stays in the store. Update Product with the publish choice set to FALSE may be a way to take it off sale: check that at the test.
3

Update Order Status

Action

In Zapier“updates order status from the list of available statuses.”

Moves an order, identified by its order ID, to one of Matajer's statuses: new, processing, ready, delivering, completed or rejected.

When to use it
mark an order as delivering when your shipping tool confirms the parcel left.
Watch out
the status must be one of those six values, written as listed; a word of your own is not on the list.
4

Update Product

Action

In Zapier“this action will be used in order to update existing product according to product identifier.”

Rewrites an existing product, found by its product ID, with the values you map in.

When to use it
push a new price or a corrected description from your catalog sheet to the live store.
Watch out
the SKU, Arabic name, Arabic description, price and publish choice are required again on every update, not only the field that changed.
When it breaks

When it breaks

Zapier links no help article to Matajer. The app's own action descriptions, plus how Zapier works, explain what goes wrong.

  • Package limit reached

    Create Product fails once your Matajer package limit is exceeded. The run errors, no product is created, and the failed action is not counted as a task.

  • Product with orders will not delete

    Delete Product only removes a product that has no related orders. One that has sold stays put. Setting the publish choice to FALSE with Update Product may take it off sale; check at the test.

  • Missing Arabic text

    Name and description in Arabic are required on Create Product and Update Product. A source with text only in another language leaves those fields empty.

  • Publish value not accepted

    Publish Product In Store expects TRUE or FALSE as text. A plain yes or no from your sheet is neither of those two values, so convert it before the step.

  • Old orders never arrive

    A Zap only reacts to what happens after it is switched on. Orders and customers from before stay out; moving that history is a separate job.

  • An order Zap that loops

    As a general precaution: a Zap that writes where its own trigger watches, such as Updated Order feeding Update Order Status, can restart itself and burn tasks.
Need help

Need help automating Matajer with Zapier?

A person reads every message.

FAQ

Matajer and Zapier: common questions

01Is the Matajer Zapier integration free?
Yes. Matajer is not a premium app, so its five triggers and four actions all work on Zapier's free plan. That plan gives 100 tasks a month and an unlimited number of Zaps, each with two steps: one trigger, one action. Logging every new order in a spreadsheet fits. As soon as you want a filter, to keep only some orders, or a second action in the same Zap, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a Matajer Zap use?
One per action that succeeds. The trigger is free, and so are Zapier's checks for new orders, however often they run. A Zap that logs each order in a sheet costs one task per order. One that also sets the order's status with Update Order Status costs two, since each successful action counts on its own. An action that fails is not counted: a Create Product blocked by your package limit does not use a task.
03Does Matajer send orders to Zapier in real time?
No. All five Matajer triggers are polling triggers: Zapier asks the store for new items at a fixed interval, and that interval depends on your plan. It is 15 minutes on Free, 2 on Professional, 1 on Team and Enterprise. On paid plans the interval can be changed, and a check can be run by hand from the editor. The trigger type is set by the app itself, so no setting in the editor turns it into an instant one.
04What does it take to connect Matajer?
A Matajer account, plus read or write access on anything in the store you do not own yourself and want your Zaps to touch. In Zapier, open the Apps page, click + Add connection, search for Matajer and click Add connection, then sign in in the tab that opens and grant access. On the action side, have the IDs at hand: Update Product, Delete Product and Update Order Status all need one, and there is no search to find it.
05Why does Create Product fail on Matajer?
Three causes to check. First, your Matajer package limit: the action fails once it is exceeded, whatever you send. Second, a required field left empty: SKU, product name in Arabic, description in Arabic, price, main image link and the publish choice must all be filled. Third, the publish field itself, which expects TRUE or FALSE written as text. Test the step once before publishing the Zap and read what Matajer returns.
06What if the Matajer operation you need is missing?
Then Zapier does not offer it for Matajer today. The five triggers and four actions on this page are all of it, with nothing hidden. Before giving up, check whether a nearby operation does the job: Update Product with the publish choice set to FALSE may take a product off the shelf without deleting it; check at the test. Then look at the Matajer page on zapier.com from time to time to see whether the list has changed.
07Zapier, Make or n8n for Matajer?
Compare on criteria, not on a winner. On Zapier, Matajer offers five polling triggers and four actions, and the free plan covers two-step Zaps with a check every 15 minutes. If order timing matters, the interval of your plan is the first criterion. The second is the missing search: any update needs an ID from an earlier step. Before choosing another tool, check whether it lists Matajer and whether its operations cover the same orders and products.
Same platform

Other docs you might need on this stack.

Browse all integrations