- Home
- Resources
- Integrations
- MDirector
MDirector Zapier integrationAutomate MDirector with Zapier.
The MDirector Zapier integration has 11 triggers, 5 actions and 1 search. Every trigger is instant: opens, clicks, bounces, unsubscribes, tags and new landing page leads reach Zapier right away. Below: costs, connection, a first Zap and what breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the MDirector Zapier integration does for you
The MDirector Zapier integration links MDirector, an email marketing and text messaging platform with its own landing page builder, to the rest of your tools. Zapier hears about what contacts do in MDirector, from opening a delivery to unsubscribing, and it can write back: create or update a contact, create a list, add or remove a tag, unsubscribe someone.
Three results worth setting up. Landing page leads where sales works. New Lead Added hands each sign-up to a spreadsheet or a chat message, without anyone exporting a file. One unsubscribe list everywhere. Contact Unsubscribed passes the opt-out to your other tools, and Unsubscribes Contact does the reverse when someone opts out elsewhere. Contacts kept current from your forms. A new form entry runs Create/Update Contact, so MDirector holds the latest details.
The good news first: all eleven triggers are instant. MDirector tells Zapier itself, so the plan interval never slows them down, even on the free plan. Now the limits. Zapier offers no operation to send a delivery, send a text message or touch Real Time Bidding: those stay inside MDirector. There is no find-or-create variant, and the tag actions need a list and a contact identifier you have to bring from an earlier step.
Still weighing platforms? Open our Make vs Zapier comparison.
Zapier vocabulary for this page
Eight terms, one line each, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run every time the trigger event happens.
- Trigger
- The event that starts a Zap. MDirector has eleven, from a tag added to a contact to a delivery that failed.
- Action
- What the Zap does once started: the step that writes, sends or moves something for you, such as Create/Update Contact.
- Task
- The unit Zapier bills: one action your Zap completes successfully. Your plan's count is a count of those.
- Instant vs polling
- Instant: the app tells Zapier the moment the event happens. Polling: Zapier checks on a timer. Every MDirector trigger is instant.
- 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 that already exists, so the next steps can use it. Find a Contact is the MDirector one.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter, a search or a second action makes it one, and it needs a paid plan.
What an MDirector Zap really costs
The eleven triggers cost nothing. You pay for the actions that go through.
- Triggers11, all instant
- Actions and searches5 actions, 1 search
- Free plan100 tasks a month, two-step Zaps
- Reserved to paid plansNo
A trigger never costs a task, and an action that fails is not counted. Each successful action counts one task, and in a Zap with several actions each success counts on its own. The free plan gives 100 tasks a month and unlimited two-step Zaps, and MDirector is not reserved to paid plans. A filter, a second action or Find a Contact makes the Zap multi-step, which needs a paid plan. The interval grid below does not apply to MDirector's triggers, which are all instant; it only matters when another app's polling trigger starts the Zap.
Connect MDirector to Zapier in 3 steps
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. You need an MDirector account with access to the lists, deliveries and landing pages your Zaps will use.
- 02
Pick MDirector
Search for MDirector in the dialog, pick it and click Add connection. A tab opens on the MDirector sign-in. The connection saved here is reused by every MDirector step afterwards.
- 03
Sign in and grant access
Sign in to MDirector in that tab and grant Zapier access to the account. For lists or deliveries someone else owns, get read or write access before you build.
Your first Zap: landing page leads in your team chat
GoalPost a chat message for each new lead from an MDirector landing page that matches your rule.
- 01
Build: pick New Lead Added
Start a new Zap, choose MDirector as the app that starts it and New Lead Added as the trigger. Pick the landing page to watch: the field is required.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent leads of that page, so pick a real one to map every next step on.
- 03
Add the filter
From the plus icon, add a Filter and fill its three boxes: the field to look at, the rule, the value. Pick a text rule for text, or the filter never passes.
- 04
Add the chat message
Add your team chat as the action app, choose its send-message event and place the lead details from MDirector into the message.
- 05
Test, then publish
Test the action and read the message it posted. If it looks right, click Publish. With the filter, this Zap is multi-step and needs a paid plan.
MDirector triggers
11 events start a Zap when something happens in MDirector, and 11 of them are instant: the app calls Zapier straight away, whatever your plan.
New Tag Added
Instant triggerIn Zapier“Triggers when a tag is added to a contact.”
Starts the Zap when a contact in MDirector receives a tag. The tag becomes a signal other tools can act on, whoever or whatever added it.
Tag Removed
Instant triggerIn Zapier“Triggers when a tag is removed from a contact.”
Reacts when a tag is taken off a contact. It is the mirror of New Tag Added and closes the loop when a status no longer applies.
Contact Delivery Failed
Instant triggerIn Zapier“Triggers when a contact delivery fails.”
Fires each time a delivery cannot reach a contact. It turns a failed send into an item someone can deal with outside MDirector.
Delivery Contact Sent
Instant triggerIn Zapier“Triggers when a delivery is sent to a contact.”
Goes off when a delivery is sent to a contact, for the deliveries you select. It gives other tools a record of who received what.
Contact Clicked an Email Link in a Delivery
Instant triggerIn Zapier“Triggers when a contact clicks in an email link of a delivery.”
A click on a given link, in an email from a delivery, is what sets this one off: it fires when a contact clicks that link. You choose both the delivery and the link it watches.
Contact Opened an Email in a Delivery
Instant triggerIn Zapier“Triggers when a contact opens an email from a delivery.”
Every open counts here: the Zap starts when a contact opens an email from one of the deliveries you choose. It tells you who engaged, not just who received.
New Lead Added
Instant triggerIn Zapier“Triggers when a new Lead registered at Landing Optimizer.”
Picks up each new lead registered on a landing page built in MDirector. It is one of the triggers Zapier highlights for this app.
New Contact Added
Instant triggerIn Zapier“Triggers when a contact is added to a list.”
Fires when a contact joins a list in MDirector. Think of it as the entry point for any welcome or onboarding flow outside the tool.
Contact Created or Updated
Instant triggerIn Zapier“Triggers when a contact is created or updated.”
Covers both cases at once: a new contact or a change to an existing one. Zapier highlights it as one of the app's main triggers.
Contact Updated
Instant triggerIn Zapier“Triggers when a contact is updated.”
Only reacts to changes on contacts that already exist, not to new ones. Use it when what matters is the edit, not the arrival.
Contact Unsubscribed
Instant triggerIn Zapier“Triggers when a contact is unsubscribed.”
An opt-out in MDirector is the event: this trigger fires when a contact unsubscribes in MDirector. Zapier highlights it, and it is the trigger that keeps consent consistent across tools.
MDirector actions
MDirector gives you 5 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Operations index
Add Tag to User
ActionIn Zapier“Add Tag to User.”
Puts a tag on a contact in a given list, with the list identifier, the contact identifier and the tag name all required.
Creates a List
ActionIn Zapier“Creates a new contact list.”
Opens a new contact list in MDirector from another app's event, ready to be filled by later steps.
Create/Update Contact
ActionIn Zapier“Creates a new contact, or updates an existing contact.”
Creates a contact in MDirector, or updates it when it already exists. Zapier highlights it as a main action.
Delete User Tag
ActionIn Zapier“Delete User Tag.”
Removes a named tag from a contact in a list, with the same three required fields as Add Tag to User.
Unsubscribes Contact
ActionIn Zapier“Unsubscribe a given existing contact.”
Unsubscribes a contact that already exists in MDirector. Zapier highlights it as a main action.
MDirector search
1 search step looks for data that already exists in MDirector, so a later step can use it.
Searches sit at the bottom of the Action event list, under SEARCH. Adding one makes the Zap multi-step, so it needs a paid plan. Three settings decide what happens when the answer is not the expected one.
Find a Contact
SearchIn Zapier“Search for contact by email.”
Looks up a contact by email address inside the contact list you pick, so the next steps can use what it finds.
The three settings every search exposes
- Successful if no search results are found?Left on its default, a search that finds nothing stops the Zap there and the steps that relied on it are skipped. Switched on, the Zap carries on empty-handed.
- Create X if it doesn't exist yet?Ticking this box turns a search into a find-or-create. MDirector offers no find-or-create variant, so Find a Contact only looks.
- If multiple search results are found?Three ways out when several items match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When an MDirector Zap breaks
Zapier attaches no help article to MDirector and no app-specific limit is on record. What breaks comes from required fields and from how Zapier works in general.
Six cases worth knowing before you publish. When one of them hits a live Zap, see our Zapier troubleshooting guide.
Empty dropdowns
Delivery, link, landing page and list fields are required on several steps. Check at test that the connected account can see the ones you need.Tag actions without identifiers
Add Tag to User and Delete User Tag require a list identifier and a contact identifier. Plan an earlier step that carries them, and check at test that they arrive.Mass imports
Three contact triggers ask whether mass imports count. If they do, a bulk import can return a huge batch that Zapier's flood protection may hold back.Loops
As a general precaution, a Zap that writes where its own trigger watches, such as Contact Created or Updated with Create/Update Contact, can set itself off again.No backlog
A Zap only reacts to what happens after it is switched on. Opens, clicks or unsubscribes that came before are not picked up; moving them is a separate job.A contact in another list
Find a Contact searches one contact list. If the address sits in a different list, the search finds nothing and, by default, the Zap stops there.
Need help automating MDirector with Zapier?
A person reads every message.



