Mertzcrew Zapier integrationAutomate Mertzcrew with Zapier.
Mertzcrew Zapier integration: 2 triggers, 2 actions, 0 searches. Zapier can react when a project or an assignment is created or updated in Mertzcrew, and it can create or update either one from another app. Both triggers are checked on a timer, never instantly.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mertzcrew Zapier integration does for you
The Mertzcrew Zapier integration links the crew-booking side of your live events to the rest of your tools. Mertzcrew helps AV companies book event freelancers at custom rates and manage their crews. Zapier watches its projects and assignments, and can write new ones back into it.
Three results people get out of it. A team that hears about crew changes: New or Updated Assignments picks up assignment changes on a project you choose, and the next step posts them in your team chat. A project list kept outside Mertzcrew: New or Updated Projects feeds each new or changed project into a spreadsheet row. Projects set up from elsewhere: Create or Update Project takes a name, dates, location and the users' emails from another app, and Create or Update Assignment books a role on a project with its dates and daily rate.
What Zapier does not do here matters too. Neither trigger is instant: Zapier checks Mertzcrew on a timer set by your plan, so a change waits for the next check. There is no search step, so a Zap cannot look up an existing project or assignment by name. And contracts, insurance and payments, which Mertzcrew handles on its own, have no operation on Zapier.
Choosing between tools? See our Make vs Zapier comparison or our Zapier training page.
Zapier words in one minute
Eight words come back all over this page. Here is what each one means, in plain terms.
- Zap
- The automation you build on Zapier: one event that starts it, then one or more steps that run every time that event happens.
- Trigger
- The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. Mertzcrew has two: one for projects, one for assignments.
- Action
- What the Zap does once it has started: the step that writes, sends or changes something for you. Mertzcrew has two of them.
- Task
- The unit Zapier bills. One task is one action the Zap completed successfully, and your plan's number counts those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment it happens. Mertzcrew's are polling.
- Filter
- A step that lets the Zap go 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 so later steps can use it. Mertzcrew offers none on Zapier.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it then needs a paid plan.
What a Mertzcrew Zap really costs
Mertzcrew is not a premium app, so it works on the free plan. Zapier bills in tasks, and the trigger itself is always free.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps
- Mertzcrew triggers2, both polling
- Trigger checksFree, never counted
Zapier's checks of Mertzcrew for new or updated projects and assignments never cost a task, however often they run. Each action that goes through is one task, whether it writes into Mertzcrew or into another app, and a failed one is not counted. The free plan gives 100 tasks a month and unlimited Zaps capped at two steps each; a filter or a second action needs a paid plan. Both Mertzcrew triggers are polling, so the grid below sets how often Zapier looks.
Connect Mertzcrew to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Mertzcrew account linked once, then reused by every Mertzcrew step.
- 02
Pick Mertzcrew
Type Mertzcrew in the search box of the dialog, select it, then click Add connection. A new tab opens on the Mertzcrew side; keep it open until you are done.
- 03
Sign in and allow access
Log in to Mertzcrew in that tab and grant Zapier access. You need a Mertzcrew account, plus read or write access on anything you do not own yourself and want the Zap to touch.
Your first Mertzcrew Zap, step by step
GoalTell your team in chat when assignments on one project change, but only for the changes that pass a condition you choose.
- 01
Create the Zap and set the trigger
Start a new Zap, pick Mertzcrew and choose New or Updated Assignments. Select the Project to watch, since that field is required.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent items from the connected account, so you see real fields before mapping anything.
- 03
Add the filter
From the plus icon, add a Filter and fill its three boxes: the field to look at, the rule, and the value. Pick a text rule for text, a number rule for numbers.
- 04
Add the chat message
Add your team chat app and build the message from the fields the test brought back. With the filter, this is a multi-step Zap, so it needs a paid plan.
- 05
Test, then publish
Test each step and read what came back before going further. When it looks right, click Publish to switch the Zap on for good.
Mertzcrew triggers
2 events start a Zap when something happens in Mertzcrew. Zapier checks for them at the interval your plan allows.
New or Updated Assignments
Polling triggerIn Zapier“Triggers when an assignment is created or updated.”
Starts your Zap when an assignment on the project you pick is created or changed in Mertzcrew. It suits anything that should follow crew bookings: a message to the team, a line in a tracking sheet, a note in another tool. Since both new and changed assignments count, one Zap covers the booking and its later edits.
New or Updated Projects
Polling triggerIn Zapier“Triggers when a project is created or updated.”
Fires your Zap whenever a project is created or edited in Mertzcrew, across the account you connected. Use it to keep an outside list, a planning sheet or a shared calendar in step with what you set up in Mertzcrew, without retyping project details.
Mertzcrew actions
Mertzcrew gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create or Update Assignment
ActionIn Zapier“Creates or edits a project assignment.”
Adds a role to a Mertzcrew project, or edits that assignment, with its start date, end date and daily rate. This is where a crew booking gets written down.
Create or Update Project
ActionIn Zapier“Creates or edits a project.”
Builds a new project in Mertzcrew, or edits one, from data your trigger carried: name, classification, pay rule, country, city, start and end dates, and the users involved.
When a Mertzcrew Zap breaks
Zapier lists no help article for Mertzcrew, and no limit specific to the app has been recorded. What goes wrong comes from how Zaps behave in general.
Here are the general limits to keep in mind. They come from how Zaps behave in general, so check them first when a project or an assignment did not go where you expected.
Past projects are not picked up
A Zap only reacts to what happens after you switch it on. Projects and assignments that already existed are not sent; moving that backlog is a separate job.A Zap that triggers itself
As a general precaution, a Zap that writes into the very place its own trigger watches can set itself off again and again, and burn through your tasks.Bulk changes get 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.No duplicates from polling
Both Mertzcrew triggers are polling, and Zapier remembers what it has already seen, so the same item does not start the Zap twice.
Need help automating Mertzcrew with Zapier?
A person reads every message.
