Resources · Zapier integration

Markko Zapier integrationAutomate Markko with Zapier.

The Markko Zapier integration sends what happens on your marketplace to your other tools. Zapier offers 3 triggers, 0 actions and 0 searches for Markko: new customers, new vendors and new enquiries can each start a Zap, instantly.

See the 3 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Markko Zapier integration is for

Markko is a platform built for running marketplaces, with ready-made or custom storefronts on top. Linking it to Zapier lets three marketplace events reach the rest of your tools: a customer signs up, a vendor joins, an enquiry is created. The flow goes one way, out of Markko.

Three results you can build. An enquiry desk that never misses a request: Enquiry (Event) Created pushes each new enquiry to the place your team actually reads, a chat channel or a shared inbox. A vendor onboarding list: Vendor Created adds every new seller to a tracking sheet, so someone can check their profile and help them set up. A customer list that feeds your email tool: Customer Created passes each new buyer on, so the welcome sequence starts without an export.

All three triggers are instant. On a free plan, that matters: nothing waits for a timed check.

Now the limits. Zapier offers no action for Markko, so a Zap cannot create, update or delete anything on your marketplace. There is no search step either, so a Zap cannot look up an existing customer or vendor. Markko is a starting point, never a destination. Before choosing a tool, see our n8n vs Zapier comparison, and our Zapier training if you are new to building Zaps.

Vocabulary

The Zapier words behind this page

Seven terms in plain English. Each is explained once, then used as is.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run every time that trigger event happens.
Trigger
The event in an app that starts the Zap, such as a new vendor on Markko. 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. With Markko, the action is always in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The allowance of your plan counts those tasks.
Instant vs polling
An instant trigger is reported by the app the moment the event happens. A polling trigger is checked by Zapier on a timer.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Search step
A step that looks up something already stored in an app for the next steps. Markko has no search step on Zapier.
Cost

What a Markko Zap costs

Markko is not a premium app, so it works on the free Zapier plan. You pay in tasks, and a Markko trigger never creates one.

  • Free plan100 tasks a month, two-step Zaps
  • Premium appNo
  • Markko triggers3, all instant, never billed
  • BilledEach successful action in the next app

When a customer, a vendor or an enquiry fires a Zap, Zapier counts nothing. The task comes from the action in the other app: one per action that succeeds, none when it fails. The free plan gives 100 tasks a month and unlimited Zaps, each with two steps: one trigger, one action. Add a filter or a second action and the Zap becomes a multi-step Zap (any Zap beyond one trigger and one action), which needs a paid plan. The interval grid below does not apply to Markko: its three triggers are instant, so the Zap starts at once on every plan.

Connect

Connect Markko to Zapier in three steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page and click + Add connection. Have your Markko account ready: Zapier links to an account that already exists.

  2. 02

    Choose Markko

    Search for Markko in the dialog, pick it from the results, then click Add connection. A new browser tab then opens so you can sign in on the Markko side.

  3. 03

    Sign in and allow access

    Log in to Markko in that tab and grant Zapier access. The connection (your account linked once, then reused by every step) appears on the Apps page. If the marketplace is not yours, the account needs read access to it.

First Zap

Your first Zap: every enquiry posted to your team

GoalEach new enquiry created on your Markko marketplace becomes a message in your team chat, but only when a field you pick matches your rule.

  1. 01

    Pick the trigger

    Create a Zap, choose Markko as the trigger app and Enquiry (Event) Created as the event. It is instant: each enquiry reaches Zapier without a timed check.

  2. 02

    Test on a real enquiry

    Run the trigger test. Zapier brings back the three most recent enquiries of the connected account; pick one so the rest of the Zap is mapped on real data.

  3. 03

    Add the filter

    From the plus icon, add Filter and fill the field, the rule and the value. Use a text rule on a text field. The filter makes the Zap multi-step, so it needs a paid plan.

  4. 04

    Add the chat step

    Add your team chat with its send-message action and build the message from the enquiry fields. Check at test time which fields the enquiry actually carries.

  5. 05

    Test, then publish

    Test the chat step once and read the message it posted. When it looks right, click Publish: the Zap is on from that point.

Triggers

Markko triggers in Zapier

3 events start a Zap when something happens in Markko, and 3 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Customer Created

Instant trigger

In Zapier“Triggers when a new Customer is added to your Markko marketplace.”

Starts a Zap whenever a new customer is added to your Markko marketplace. Each new buyer can then be copied to your mailing tool, your CRM or a sheet, without anyone exporting a list.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
you want new customers to receive a welcome email from the tool your marketing team already uses.
Watch out
the source does not list the fields a customer carries, so check at test time what comes back before mapping an email address or a name.
2

Enquiry (Event) Created

Instant trigger

In Zapier“Triggers when a new Enquiry (Event) is created in your Markko marketplace.”

Fires when a new enquiry, which Markko also calls an event, is created on your marketplace. It is the trigger to use when a request should never sit unanswered in the back office.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
your team works from a chat tool or a helpdesk, and every new enquiry should show up there for someone to pick up.
Watch out
posting the enquiry to two tools at once means two actions, so a multi-step Zap and a paid plan.
3

Vendor Created

Instant trigger

In Zapier“Triggers when a new Vendor is added to your Markko marketplace.”

Reacts each time a new vendor is added to your Markko marketplace. That makes it the natural starting point for anything you do when a seller joins: a welcome message, a checklist row, a task for the team.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
someone on your side reviews new sellers, and you want each new vendor added to their tracking sheet the moment they register.
Watch out
only new vendors start the Zap; sellers who joined before you switched it on are never sent.
When it breaks

When a Markko Zap breaks

Zapier links no help article to Markko, and the source records no limit specific to the app. What can go wrong comes from how Zapier works in general.

Three cases are worth knowing before you publish. Each one has a plain workaround. If a Zap still misbehaves, our Zapier troubleshooting page is the next stop.

  • The backlog is not sent

    A Zap only reacts to what happens after you switch it on. Customers, vendors and enquiries created earlier stay in Markko; moving them is a separate job.

  • A bulk import gets held back

    When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those items back instead of passing them all on.

  • The next step fails

    Markko only starts the Zap; the work happens in the other app. If that action fails, for example on an empty required field, it costs no task, but nothing is written either.
Need help

Need help automating Markko with Zapier?

A person reads every message.

FAQ

Markko Zapier integration: what people ask

01Is the Markko Zapier integration free?
Yes. Markko is not a premium app, so it runs on the free Zapier plan. That plan gives 100 tasks a month and unlimited Zaps, each one limited to two steps: one trigger and one action. A Zap from Customer Created to a single row in a spreadsheet fits that model. If you add a filter or a second action, the Zap becomes multi-step, and multi-step Zaps need a paid plan, so plan the shape of the Zap before you start building.
02How many tasks does a Markko Zap use?
Markko itself uses none. Its three triggers are free: a new customer, vendor or enquiry starting a Zap is not billed. Tasks come from the actions that follow in other apps, one per action that succeeds, none when it fails. A Zap that turns each enquiry into a chat message uses one task per enquiry; one that also adds a spreadsheet row uses two. Count the actions after the trigger to know what a month of marketplace activity will cost.
03Does Markko send events to Zapier in real time?
Yes. Customer Created, Enquiry (Event) Created and Vendor Created are all instant triggers: Markko tells Zapier itself when the event happens, so the Zap does not wait for a timed check. The plan interval grid does not apply to them, even on the free plan. In the editor, an instant trigger carries a lightning bolt, which is the quickest way to confirm it. The speed of the next step depends on the other app, not on Markko.
04What does Zapier need to connect a Markko account?
A Markko account and a few clicks in Zapier. Open the Apps page, click + Add connection, search for Markko, then sign in to it in the tab that opens and grant access. If the marketplace belongs to someone else in your company, the account you connect needs read access to its customers, vendors and enquiries. Once linked, every Zap that starts from Markko reuses the same connection, so the setup is done only once.
05Can Zapier create customers or vendors in Markko?
No. Zapier offers no action for Markko, only three triggers. A Zap can react to a new customer, vendor or enquiry, but it cannot add one, change one or remove one on your marketplace. If the goal is to push data into Markko from a form or a CRM, this integration will not do it. Plan your Zaps with Markko as the first step and another app as the place where the work gets done.
06What if the Markko event you need is not in Zapier?
Then it is out of reach from Zapier for now. The editor lists Customer Created, Enquiry (Event) Created and Vendor Created, and no search step to look things up. The list follows the version of the app that Zapier publishes, and it can change, so check the Markko page on zapier.com before giving up on the idea. Until then, one of the three existing events is the only way in.
07Zapier, Make or n8n for Markko?
Choose on criteria, not on a ranking. Start with coverage: on Zapier, Markko offers three instant triggers and nothing else, so check whether the other tool has a Markko connection with the events you need. Then billing: Zapier never counts the trigger, only each successful action. Finally the free plan: two steps per Zap, so any filter means paying. How much each point weighs depends on how much activity your marketplace generates.
Same platform

Other docs you might need on this stack.

Browse all integrations