Resources · Zapier integration

MyZenTeam Zapier integrationAutomate MyZenTeam with Zapier.

MyZenTeam Zapier integration: 2 triggers, 0 actions, 0 searches. MyZenTeam can start a Zap when an application is created or when it moves to another stage. Both triggers are instant, even on the free plan, but no Zap can write back into MyZenTeam.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the MyZenTeam Zapier integration does for you

The MyZenTeam Zapier integration turns two moments of your hiring process into the start of an automation. MyZenTeam is a hiring tool built to make that process shorter and more inclusive; Zapier listens for new applications and for stage changes, then hands the details to the tools that come next.

Three results come out of it. A live record of incoming applications: Application Created starts the Zap for each new one, and the next step can add it as a row in a shared sheet. A team that hears about progress: Application Stage Updated fires when an application changes stage, so a message can go out in your team chat. A follow-up list that fills itself: the same stage trigger can create a task in your task tool, so nothing waits on someone remembering.

What Zapier does not do here: MyZenTeam has no action and no search on Zapier. A Zap cannot create an application, move it to a new stage or look one up inside MyZenTeam. Data flows out of the app, never into it. To weigh that against other tools, see our Make vs Zapier comparison.

The good news sits in how the triggers work. Both are instant: MyZenTeam tells Zapier when the event happens, so your Zap starts right away whatever your plan, and the free-plan check interval never slows it down.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

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 on, Zapier waits for it. Both MyZenTeam operations are triggers.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, here always in another app.
Task
The unit Zapier bills: one action your Zap completes successfully. The number attached to your plan is a count of those.
Polling trigger
A trigger Zapier checks on a timer, at a fixed interval set by your plan. Neither MyZenTeam trigger works this way.
Instant trigger
A trigger the app reports by itself: it calls Zapier the moment the event happens, so nothing waits for a check.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it there otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter turns a Zap into one, and it then needs a paid plan.
Cost

What a MyZenTeam Zap really costs

Zapier bills actions, not triggers. MyZenTeam only ever starts Zaps, so the bill depends entirely on what happens in the steps after it.

  • Premium appNo, it works on the free plan
  • Free plan100 tasks a month, Zaps of two steps
  • Cost of a trigger0 tasks

A task is counted each time your Zap carries out an action and it works. The trigger never costs one. An action that fails is not counted either. In a Zap with three actions, each success counts on its own, so it eats three times more than a one-action Zap. The free plan gives 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. Add a filter or a second action and you need a paid plan. Zapier publishes the interval grid below for polling triggers; it does not apply to the two instant triggers of MyZenTeam.

Connect

Connect MyZenTeam to Zapier in 3 steps

  1. 01

    Open the Apps page

    In your Zapier account, open the Apps page. A connection is your MyZenTeam account linked to Zapier once, then reused by every step that needs it. 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.

  2. 02

    Add the connection

    Click + Add connection, type MyZenTeam in the search box of the dialog and pick it from the results. Then click Add connection to open the MyZenTeam sign-in in a new tab.

  3. 03

    Sign in and grant access

    In that tab, sign in to MyZenTeam with the account that holds the applications you want to follow, then grant Zapier access to it. Back in the editor, the connection can be picked in any Zap that starts from MyZenTeam.

First Zap

Your first Zap: new applications in a shared sheet

GoalEvery new application that matches your condition lands as a row in the spreadsheet your team works from.

  1. 01

    Create the Zap and pick the trigger

    Build a new Zap, choose MyZenTeam as the app that starts it and Application Created as the event. Select the MyZenTeam connection you set up earlier.

  2. 02

    Test the trigger

    Run the trigger test. Zapier brings back the three most recent items of the connected account, so the rest of the Zap is mapped on a real application, not on a guess.

  3. 03

    Add the filter

    From the plus icon, add a Filter step and set its three boxes: the field to look at, the rule, the value. A filter makes this a multi-step Zap, which needs a paid plan.

  4. 04

    Add the spreadsheet action

    Add the action in your spreadsheet tool, pick the event that adds a row, and map the values the trigger returned into the columns. Test this step too and read what came back.

  5. 05

    Publish

    Click Publish to switch the Zap on. It reacts to applications created from that moment; the ones already in MyZenTeam stay out of the sheet.

Triggers

MyZenTeam triggers on Zapier

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

1

Application Created

Instant trigger

In Zapier“Triggers when an application is created.”

A new application appears in MyZenTeam and your Zap starts with it, carrying its details to the steps that follow so they can file or announce it.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
keep a sheet of every incoming application that people outside MyZenTeam can read, or open a task for each one in your task tool.
Watch out
no required field here, so the test is your main check; read the fields it returns before you map anything.
2

Application Stage Updated

Instant trigger

In Zapier“Triggers when the stage of an application is updated.”

Moving an application to another stage in MyZenTeam launches the Zap, and what it carries can feed the next steps: the test shows which fields come back.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
tell the team in its usual chat when an application moves forward, or keep a running log of stage changes in a sheet.
Watch out
if only some stages matter to you, a filter can do the sorting on a field the test returns, and a filter needs a paid plan.
When it breaks

When a MyZenTeam Zap breaks

Zapier links no help article and no documented limit to MyZenTeam, so the cases below come from how Zapier itself works.

Three of them are worth knowing before you publish. If a Zap does not behave the way you planned, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Applications that already existed stay out, and moving that 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 burn through your task count. Check where each step writes.

  • Flood protection

    After a bulk import or a migration, a trigger may suddenly return a huge batch, and Zapier's flood protection can hold that batch back.
Need help

Need help automating MyZenTeam with Zapier?

A person reads every message.

FAQ

MyZenTeam and Zapier: your questions

01Is the MyZenTeam Zapier integration free?
Yes. MyZenTeam is not a premium app, so both of its triggers work on the free plan of Zapier. That plan gives you 100 tasks a month and as many Zaps as you like, with one condition: each Zap holds two steps, one trigger and one action. A MyZenTeam trigger followed by one action in another app fits exactly. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The trigger itself never uses a task.
02How many tasks does a MyZenTeam Zap use?
None for the trigger: a new application or a stage change costs nothing on its own. Each action that completes successfully counts as one task, so a Zap with one action spends one task per application or stage change it handles, and a Zap with three actions spends three. An action that fails is not counted against your plan. A few apps take more than one task for some actions, so keep an eye on the other app in your Zap.
03Does MyZenTeam start Zaps in real time?
Yes, both of its triggers are instant. When an application is created or changes stage, MyZenTeam tells Zapier itself and the Zap starts right away, whatever your plan. The interval grid Zapier publishes for its plans concerns polling triggers only, so it does not apply here, and a free plan is not slower than a paid one for these two events. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does connecting MyZenTeam to Zapier require?
An account on the app, plus read or write access on anything you do not own yourself and want the Zap to touch. The connection is made once, from the Apps page of your Zapier account, then reused by every Zap that starts from MyZenTeam. Neither trigger has a required field, so once the account is connected, testing the trigger is what tells you which fields you can use in the next steps.
05Can a Zap move an application to another stage in MyZenTeam?
No. MyZenTeam offers no action and no search on Zapier, only two triggers. The app can start a Zap, it can never be one of its later steps. So a Zap can announce a stage change, log it or turn it into a task elsewhere, but it cannot change the stage, create an application or find one inside MyZenTeam. Any flow that needs to write into the app cannot be built with this integration as it stands today.
06What if the MyZenTeam trigger you need is missing?
Then the editor cannot offer it. The MyZenTeam page on zapier.com shows the current list of operations, and only those can be picked when you build a Zap. Before giving up, test both triggers and read what each one returns: the information you are after may already travel with Application Created or Application Stage Updated, and a filter or a later step can then work with it. Only the test tells you for sure.
07Zapier, Make or n8n for MyZenTeam?
Decide on criteria rather than on a winner. Coverage first: on Zapier, MyZenTeam offers two triggers and no action, so compare what each tool offers for this app before you choose. Then the billing model: Zapier counts each successful action as a task and never bills the trigger. Then the shape of your flows: anything beyond one trigger and one action needs a paid plan on Zapier. Finally, speed: both triggers are instant, so the check interval of a plan does not apply to them.
Same platform

Other docs you might need on this stack.

Browse all integrations