Resources · Zapier integration

Model Match Zapier integrationAutomate Model Match with Zapier.

Model Match Zapier integration: 8 triggers, 5 actions and 0 searches. All 8 triggers are instant, so a reply, a tag or a finished to-do in Model Match starts your Zap right away. Here is how each step works, what it costs and what breaks.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the Model Match Zapier integration does for you

The Model Match Zapier integration links your Model Match account, where recruiting contacts, requisitions and sequences live, to the rest of your tools through Zapier. Every one of its 8 triggers is instant: Model Match tells Zapier itself when something happens, so even on the free plan nothing waits for a timer.

A reply that reaches the right person. Contact Responded to Sequence catches the answer to one of your sequences and can post it in your team chat while it is fresh. Contacts that arrive from elsewhere. A form or a spreadsheet row in another app becomes a contact inside a requisition with Add Contact to Requisition, or lands in a sequence with Add Contact to a Sequence. An alert when a contact changes hands. Contact Is Assigned tells a chat or an inbox who now owns that contact.

What Zapier does not do here: the integration has no search step, so a Zap cannot look a contact up by name before updating it, and no action deletes, untags or unassigns anyone. Only events that happen after the Zap is on are seen. The free plan covers each idea above as a two-step Zap; a third step means a paid plan. To weigh the tool itself, see our Zapier review, and to set it against another option, open our n8n vs Zapier comparison.

Vocabulary

Zapier words, in plain English

Eight terms come back all through this page. Here they are, one line each, before you open the editor.

Zap
The automation you build in 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, here a reply, a tag or a stage change.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, like adding a contact.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts those.
Instant vs polling
Instant: the app reports the event to Zapier itself. Polling: Zapier checks on a timer. All Model Match triggers are instant.
Filter
A step that lets the Zap go on only when what arrived meets a condition you set, and stops it there otherwise.
Connection
Your Model Match account linked to Zapier once, then reused by every Model Match step in every Zap you build.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action, a filter or a search makes one, and it then needs a paid plan.
Cost

What a Model Match Zap really costs

Zapier bills tasks, and a task is an action that worked. None of the 8 Model Match triggers costs one, however many replies or tags come through.

  • Trigger0 tasks
  • Successful actionCounted as a task
  • Free plan100 tasks a month, two-step Zaps
  • Model Match triggers8 of 8 instant

Each action that succeeds, say an Add a Contact, counts against your plan; a failed one does not. A three-action Zap eats three times what a one-action Zap does, and a few actions take more than one task. Model Match works on the free plan: 100 tasks a month, unlimited Zaps, two steps each. A filter or a second action makes the Zap multi-step and paid. The grid below is how often Zapier checks a polling trigger per plan; it does not apply to the instant triggers of Model Match.

Connect

Connect Model Match to Zapier in three steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. In the dialog that opens, type Model Match in the search box and pick it from the results.

  2. 02

    Sign in to Model Match

    Click Add connection. A new tab opens on Model Match: sign in with the account that holds the requisitions, sequences and contacts you want your Zaps to work on.

  3. 03

    Grant Zapier access

    Approve the access Zapier asks for. You need an account on Model Match, plus read or write access on anything you do not own yourself and want the Zap to touch. Every Model Match step then reuses this connection.

First Zap

Your first Model Match Zap, step by step

GoalWhen a contact replies to a sequence, post the reply in your team chat and add a follow-up task to your task list.

  1. 01

    Build the trigger

    Create a Zap, pick Model Match as the app that starts it and Contact Responded to Sequence as the event. Choose your connection, then the Sequence to watch, which is required.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent items of the connected account, so you map the next steps on a real reply. Look at what the reply carries before going on.

  3. 03

    Post the reply

    Add your team chat app and its send-message action. Map into the text the details of the reply that the test brought back, then test the step and read what came back.

  4. 04

    Add the follow-up task

    Add your task list app and its create-task action. This second action makes the Zap multi-step, so it needs a paid plan. Test it the same way before going on.

  5. 05

    Publish

    Click Publish to switch the Zap on. Replies that come in from then on start it; replies received before that moment are left alone.

Triggers

The 8 Model Match triggers

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

1

Contact Is Added to a Requisition

Instant trigger

In Zapier“Triggers when a contact is added to a requisition.”

Starts your Zap each time someone joins a requisition in Model Match, whichever requisition it 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
when a newcomer to a requisition should land in a shared sheet or a team channel without anyone copying names over.
Watch out
it reports every addition, whoever made it, so test on a real requisition and check at the test what the event carries.
2

Contact Is Assigned

Instant trigger

In Zapier“Triggers when a contact is assigned to a user.”

Reacts when a contact is handed to a given user, so the person who now owns that contact hears about it without opening Model Match.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when each new assignment should reach the owner by chat or e-mail with the contact's details.
Watch out
the User box is required, and the Zap only fires for contacts assigned to the user selected there.
3

Contact Is Marked as Touched

Instant trigger

In Zapier“Triggers when a contact is marked as touched.”

Picks up the moment a contact gets marked as touched in Model Match, so that status can travel to your other tools.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when every touch should be logged in another tool, such as a spreadsheet you keep for follow-up or reporting.
Watch out
test it on a real contact first, and check at the test which details the touch carries before you map them.
4

Contact Responded to Sequence

Instant trigger

In Zapier“Triggers when a contact responds to a sequence.”

Fires when a contact answers one of your sequences, so a response becomes something your other tools can act on.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a reply should move the contact forward or alert the person in charge while the conversation is still warm.
Watch out
the Sequence box is required, so the sequence has to exist in Model Match before you set the trigger up; check at the test which replies come through.
5

Contact Stage Is Updated

Instant trigger

In Zapier“Triggers when the contact stage has been updated.”

Starts the Zap whenever a contact's stage changes, in whichever requisition it sits.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a stage move has consequences elsewhere, like a row to update in a tracking sheet or a message to a manager.
Watch out
as with any trigger, a Zap that writes back into what it watches can set itself off again, so test before you publish.
6

Contact Updated

Instant trigger

In Zapier“Triggers when a contact is updated.”

Watches the contacts of one requisition and starts the Zap when any of them is edited in Model Match.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when another tool keeps a copy of your contacts and has to stay in step with the changes made in Model Match.
Watch out
the Requisition box is required, so pick the requisition to watch and check at the test which edits come through.
7

Requisition Contact Is Tagged

Instant trigger

In Zapier“Triggers when a requisition contact has been tagged.”

Turns a tag into a starting point: the Zap runs when a contact inside a requisition receives the tag you chose.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a tag means a next move, such as handing the contact to a colleague or adding them to a list in another app.
Watch out
the Tag box is required, so the tag has to exist in Model Match before you set the trigger up.
8

To-Do Completed

Instant trigger

In Zapier“Triggers when a To-Do is marked as complete.”

Catches every to-do that gets marked as complete in Model Match, so finished work can be reported elsewhere.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a manager wants finished to-dos to show up in a sheet or a channel instead of checking the app.
Watch out
only to-dos completed after the Zap is published come through; earlier ones are not picked up.
Actions

The 5 Model Match actions

Model Match gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Add a Contact

Action

In Zapier“Adds a new user contact”

Creates a plain contact in Model Match from data your Zap carries, with no requisition or sequence attached.

When to use it
when names collected elsewhere simply need to exist in Model Match before anyone sorts them.
Watch out
First Name and Last Name are both required, so map them from a step that always fills them.
2

Add Contact to a Sequence

Action

In Zapier“Creates a new contact and adds it to a sequence”

Creates a contact and enrolls it in one of your sequences at the same time, so outreach starts without a manual step.

When to use it
when a new lead from another app should go straight into an existing sequence.
Watch out
Phone Number and Sequence are required on top of the names, so the source step has to carry a phone number.
3

Add Contact to Requisition

Action

In Zapier“Creates a new contact and adds it to a specified requisition”

Builds a new contact and places it straight into the requisition you name, in one step.

When to use it
when people coming from a form or a sheet belong to one specific requisition from the start.
Watch out
Requisition, First Name and Last Name are required; the requisition must already exist in Model Match.
4

Assign a Contact to a User

Action

In Zapier“Creates a new contact and adds it to a specified requisition. Then assigns the contact to a user”

Creates a contact, adds it to a requisition, then hands it to a user, three moves in a single action.

When to use it
when the owner of a new contact is known at the moment it arrives, so nobody has to dispatch it later.
Watch out
it requires a Requisition Id and a User as well as both names; check at the test how it treats someone already in Model Match.
5

Update Contact Stage

Action

In Zapier“Updates a Contact to a stage”

Moves an existing contact to the stage you pick inside a requisition, the one action here that changes a contact rather than creating one.

When to use it
when an event, a reply or a tag, should push the contact forward without a click in Model Match.
Watch out
Requisition Id and Contact Id are required and no search can find them, so they have to come from an earlier step.
When it breaks

When a Model Match Zap breaks

Zapier attaches no help article to Model Match, so the cases below are the general limits that apply to any Zap built on it.

Three limits are worth knowing before you publish. If a Zap stops behaving, see our Zapier troubleshooting guide.

  • No catch-up on the past

    A Zap only reacts to what happens after you switch it on. Replies, tags and to-dos from before are never picked up; 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 set itself off again and again, and burn through your tasks fast.

  • A sudden flood held back

    If a trigger suddenly returns a huge batch, after a bulk import or a migration of contacts, Zapier's flood protection can hold it back.
Need help

Need help automating Model Match with Zapier?

A person reads every message.

FAQ

Model Match and Zapier: the questions people ask

01Is the Model Match Zapier integration free?
Yes. Model Match is not reserved for paid plans, so it works on Zapier's free plan. That plan gives you 100 tasks a month and an unlimited number of Zaps, each limited to two steps: one trigger, one action. A Zap that sends an alert when a contact is assigned fits that frame. Add a filter, a search or a second action and the Zap becomes multi-step, which needs a paid plan. The trigger never costs a task, and since all 8 Model Match triggers are instant, the free plan does not slow them down.
02How many tasks does a Model Match Zap use?
One per action that succeeds, and none for the trigger. When Add Contact to Requisition goes through, that is one task; when it fails, nothing is counted. In a Zap with several actions, every successful action counts on its own, so three actions eat three times what one does. Waiting for replies, tags or stage changes costs nothing at all. A few actions take more than one task when they complete, so keep an eye on your plan's count, which is 100 tasks a month on the free plan.
03Does Model Match start a Zap in real time?
Yes. All 8 Model Match triggers are instant: Model Match itself tells Zapier when a contact replies, gets tagged, changes stage or when a to-do is completed, so the Zap starts right away. The interval grid of Zapier's plans, which sets how often polling triggers are checked, does not apply here, even on the free plan. In the editor, a Zap built on an instant trigger shows a lightning bolt. The type is set by Model Match and cannot be switched from the editor.
04What does it take to connect Model Match to Zapier?
An account on Model Match, plus read or write access on anything you do not own yourself and want the Zap to touch. In Zapier, open Apps, click + Add connection, search Model Match, then click Add connection and sign in on the tab that opens. Grant access and the connection serves every later Model Match step. Before building, create the sequences, requisitions and tags you intend to use, because several triggers and actions make you pick one of them in a required box.
05Why does Update Contact Stage ask for a Contact Id?
Because it changes an existing contact, and Zapier has to know exactly which one. The action requires a Requisition Id, a Contact Id and a stage. The Model Match integration has no search step, so the Zap cannot look the contact up by name first: the ids have to come from an earlier step. Nothing documents which earlier step returns them, so run the test of that step and check whether a Requisition Id and a Contact Id are in what came back before you map them.
06What if the Model Match operation you want is not there?
Then Zapier cannot do it with Model Match today. The integration offers 8 triggers and 5 actions, and no search. The Model Match page on Zapier shows the current list, so check it before planning around a missing step. Deleting a contact, removing a tag or looking a contact up are examples of what no step does here. You can still work around it: keep the extra data in another app, and use the Model Match actions for what they do, creating contacts, assigning them and moving stages.
07Zapier, Make or n8n for Model Match?
It depends on your criteria, not on a winner. On Zapier, Model Match comes with 8 instant triggers and 5 actions, usable on the free plan in two-step Zaps. Because every trigger is instant, the check interval of a plan does not apply here, which matters a lot on the free tier. If your flows need filters or chains of actions, count the multi-step requirement and the tasks each run eats. With Make and n8n, check first whether they offer Model Match, then how they count runs and how much setup you are ready to own.
Same platform

Other docs you might need on this stack.

Browse all integrations