Resources · Zapier integration

Maqqie Zapier integrationAutomate Maqqie with Zapier.

Maqqie Zapier integration: 1 trigger, 1 action, no search. Maqqie handles contracts and payouts for employees and freelancers. Zapier links it to your other tools through a Zap, an automation that waits for one event and then does the work for you.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Maqqie Zapier integration actually does

The Maqqie Zapier integration is a short bridge with two ends. One end tells Zapier when a label lands on an employee or a candidate in Maqqie. The other end creates an employee, regular or freelance, in Maqqie from details another app already holds. Everything else (contracts, schedules, payouts) stays inside Maqqie.

Three results people build with it. A labeled candidate that reaches the rest of the team: Label Added to Candidate starts a Zap when a label you name is added, and the next step can post it to a spreadsheet or a chat tool. A new hire that nobody retypes: a form or sheet collects the person once, and Create Employee adds them to Maqqie as a regular or freelance employee. A running log of hiring decisions: every time your team tags someone, a row appears in a shared sheet, which gives you a history outside Maqqie.

What Zapier does not do for Maqqie matters just as much. There is no search step for this app, so a Zap cannot check whether a person already exists before Create Employee runs. There is no action to update or remove an employee. And only one event starts a Zap: a label being added. A contract signed or a payout sent does not show up as a trigger.

The good news is about speed. The only Maqqie trigger is instant, so the timer that slows polling triggers on the free plan never applies to it. If you are still deciding whether Zapier is the right tool at all, see our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Eight words carry this whole page. Here they are in plain English, each once.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is switched on, Zapier sits and waits for it.
Action
What the Zap does after it starts: the step that writes, sends or creates something for you in an app.
Task
The unit Zapier bills. One task is one action your Zap finished successfully, and your plan counts those.
Polling vs instant
A polling trigger is checked on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap carry on only when the incoming data meets a condition you set, and stops it otherwise.
Connection
Your Maqqie account linked to Zapier once, then reused by every step in every Zap that touches Maqqie.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes one, and it needs a paid plan.
Cost

What a Maqqie Zap really costs

The trigger never costs anything. Zapier only bills an action that went through, and an action that fails is not counted against your plan.

  • Label Added to Candidate0 tasks, triggers are free
  • Each successful Create Employee1 task
  • Free plan100 tasks a month, two-step Zaps
  • Maqqie on the free planYes

Maqqie is not one of the apps Zapier keeps for paid plans, so it works on the free plan: 100 tasks a month, unlimited Zaps, two steps each. That covers a label that writes one row, or a form entry that becomes one employee. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below is the one Zapier applies to polling triggers; it does not apply to Maqqie's instant trigger, which fires whatever your plan.

Connect

Connect your Maqqie account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need a Maqqie account first, plus access to any records you do not own yourself and want the Zap to touch.

  2. 02

    Find Maqqie and start the link

    Type Maqqie in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab opens on the Maqqie side, where the rest happens.

  3. 03

    Sign in and grant access

    Log in to Maqqie in that tab and allow Zapier to use your account. The connection then appears on the Apps page, ready for every Zap that has a Maqqie step.

First Zap

Your first Zap: a label that emails the right person

GoalWhen a label is added to a candidate in Maqqie, let only the cases that match your condition through and send an email about them.

  1. 01

    Set the trigger

    Build a new Zap, pick Maqqie as the starting app and Label Added to Candidate as the event. Choose your connection, then type the Label Name the Zap should wait for.

  2. 02

    Test it on real data

    Run the test. Zapier brings back the three most recent items from the connected account, so you map the next steps on a real candidate rather than on a guess.

  3. 03

    Add a filter

    Add a Filter step from the plus icon, then set the field to look at, the rule and the value. Pick a text rule for text and a number rule for numbers, or the filter never passes.

  4. 04

    Add the email

    Add the action of your email tool and build the message from what Maqqie sent at test. Unsure what a field holds? Check it in the test result before you map it.

  5. 05

    Test, then publish

    Test each step and read what came back, then click Publish. The filter makes this a multi-step Zap, so it runs on a paid plan. Our Zapier training is there if you want guided practice.

Triggers

The Maqqie trigger

1 event starts a Zap when something happens in Maqqie, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

Label Added to Candidate

Instant trigger

In Zapier“Triggers when a label is added to an employee or candidate.”

Your Zap starts when someone on your team puts a label on an employee or a candidate in Maqqie. The steps after it get whatever Maqqie sends about that event, and the test shows you exactly what that is.

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 recruiters tag a candidate as ready to hire, and that decision should land in a shared sheet or a team chat without anyone copying it over.
Watch out
the trigger asks for a Label Name, so type the label exactly as your team uses it and confirm at test that an item comes back.
Actions

The Maqqie action

Maqqie gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Employee

Action

In Zapier“Action can create a regular employee or freelance employee”

Adds a person to Maqqie as a regular employee or as a freelance employee, built from details an earlier step already gathered.

When to use it
new people sign up through a form, and nobody should enter them into Maqqie a second time by hand.
Watch out
first name, zipcode, phone number and email address are all required, so the source step has to carry each one.
When it breaks

When a Maqqie Zap breaks

Zapier links no help article to Maqqie, so the failures below are the ones every Zap can hit.

Most problems come from what a Zap was never built to do rather than from Maqqie itself. When a run goes wrong, read our Zapier troubleshooting guide.

  • Old labels are never picked up

    A Zap only reacts to what happens after you switch it on. Labels added before that stay where they are, and moving the backlog 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 eat your task count fast. Keep the two apart.

  • A sudden flood is held back

    When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold those runs back.

  • A filter on the free plan

    The free plan builds two-step Zaps only. Add a filter or a second action and the Zap is multi-step, which needs a paid plan to run.
Need help

Need help automating Maqqie with Zapier?

A person reads every message.

FAQ

Maqqie and Zapier: your questions

01Is the Maqqie Zapier integration free?
Yes, it runs on Zapier's free plan. Maqqie is not one of the apps Zapier keeps for paid plans, so you can connect it without paying. The free plan gives you 100 tasks a month and as many Zaps as you like, but each Zap stops at two steps: one trigger and one action. Label Added to Candidate followed by one step in another tool fits. So does a form entry followed by Create Employee. The moment you add a filter or a second action, the Zap becomes multi-step and moves to a paid plan.
02How many tasks does a Maqqie Zap use?
One task per action that succeeds, and nothing for the trigger. A label added in Maqqie that starts a Zap costs zero on its own. If that Zap then writes one row in a sheet, the run costs one task. Give it two actions and a full run costs two. Create Employee works the same way: each person added successfully counts once, and an attempt that fails is not counted. Zapier notes that a few apps and actions take more than one task when they complete, so read your usage after the first real runs.
03Does the Maqqie trigger work in real time?
It does. Label Added to Candidate is an instant trigger: Maqqie itself calls Zapier when a label is added, so the Zap starts without waiting for a check, whatever your plan. You will see a lightning bolt on it in the editor. The interval grid only matters when your Zap starts in another app with a polling trigger and ends on Create Employee. Then the speed depends on your plan: every 15 minutes on Free, every 2 on Professional, every minute on Team and Enterprise.
04What do you need to connect Maqqie to Zapier?
A Maqqie account, and access to any records you do not own yourself but want the Zap to touch. The rest happens in Zapier. Open the Apps page, click + Add connection, search for Maqqie and pick it, then click Add connection. A tab opens where you sign in to Maqqie and allow Zapier to use the account. From then on, that single connection is reused by every Maqqie step in every Zap you build, so you only do this once per account.
05Why does Create Employee ask for four required fields?
Because Maqqie needs a first name, a zipcode, a phone number and an email address before it adds anyone, whether a regular or a freelance employee. Zapier marks all four as required on the step. The practical consequence is upstream: the app that starts your Zap must collect those four details. A sign-up form that skips the phone number, for instance, leaves that box with nothing to map. Check the source before you build, then run the test and read what Maqqie sent back.
06What if the Maqqie operation you need is not listed?
Then Zapier does not offer it today. Its editor shows one trigger and one action for Maqqie, and nothing else: no search, no update, no way to remove an employee. Keep that part of the process inside Maqqie, and automate around it with the two operations that do exist: the label as a signal going out, Create Employee as a way in. Before you plan a new Zap, open the Maqqie page on Zapier: it shows the current list of operations, and that is the one to trust.
07Zapier, Make or n8n for Maqqie?
It depends on three criteria, not on a ranking. First, coverage: on Zapier, Maqqie offers one instant trigger and one action, so check whether the other platform lists the Maqqie operation your process needs. Second, billing: Zapier counts each successful action as a task, and the trigger is free, so estimate your monthly volume of labels and new hires. Third, length: Zapier's free plan stops at two steps, so a Zap that needs a filter means a paid plan. Weigh those three against each platform's own Maqqie listing.
Same platform

Other docs you might need on this stack.

Browse all integrations