- Home
- Resources
- Integrations
- Mylance
Mylance Zapier integrationAutomate Mylance with Zapier.
The Mylance Zapier integration gives you 2 triggers, 0 actions and 0 searches. Both triggers are instant: when you export a contact or a company from Mylance, Zapier hears about it right away, even on the free plan. Here is what they do, what they cost and where they trip.
Verified Trustpilot reviews · AI, automation & growth agency
What the Mylance Zapier integration does for your pipeline
Mylance is a lead generation tool built for fractional businesses. On Zapier it works in one direction only: when you export a contact or a company from Mylance, Zapier receives it and your Zap passes it on to the tool where you actually work those prospects, such as your CRM, a spreadsheet or your team chat.
Contacts that reach your CRM without a CSV. Contact Exported hands each exported person to the next step of your Zap, so your CRM gets the record without a download and an upload in between. You decide what leaves Mylance by deciding what to export.
A company list that keeps itself. Lead Exported fires when a company is exported. Pointed at a spreadsheet, it builds the list of accounts you are targeting, one row per export, with the fields Mylance sends filled in.
A team that knows who is new. Either trigger can post in your team chat, so your team sees the new prospect without asking.
What Zapier does not do here: Mylance has no action and no search on Zapier. A Zap cannot create, update or look up anything inside Mylance; it can only react to your exports and carry them elsewhere. Exports made before the Zap is switched on are not sent either.
If you are weighing other tools for this, see our Make vs Zapier page.
Zapier words, in one minute
Seven terms come back on this page. Here they are once, in plain English.
- Zap
- The automation you build in Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts your Zap. Once the Zap is switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that writes, sends or creates something for you in an app.
- Task
- The unit Zapier bills you for: one action your Zap completes successfully. Your plan allowance is a count of those.
- Instant vs polling
- An instant trigger is reported by the app itself the moment the event happens. A polling trigger is checked by Zapier on a timer.
- Filter
- A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your Mylance account linked to Zapier once, then reused by every Zap that starts from a Mylance export.
What a Mylance Zap really costs
Mylance is not a premium app, so it works from the free plan. You pay in tasks, and only completed actions count, which here means actions in your other apps.
- Mylance triggerFree, never counted
- Each successful action1 task
- Free plan100 tasks a month, unlimited two-step Zaps
- Filter or second actionMulti-step Zap, paid plan
The Mylance trigger never costs a task, however many contacts you export. Each action that goes through in the next app is one task: a Zap that adds a CRM contact and posts in chat uses two per export. A failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. A second action or a filter makes it a multi-step Zap, which needs a paid plan.
The grid below is how often Zapier checks a polling trigger on each plan. Both Mylance triggers are instant, so it does not apply to them.
Connect your Mylance account to Zapier
- 01
Open Apps and add a connection
In your Zapier account, open the Apps page and click + Add connection. You need a Mylance account, plus read or write access on anything you do not own yourself and want the Zap to touch.
- 02
Find Mylance and confirm
Type Mylance in the search box of the dialog, pick it from the results, then click Add connection. A new browser tab opens on the Mylance side, where the setup finishes.
- 03
Sign in and grant access
Sign in to Mylance in that tab and grant Zapier access to the account. Every Zap that starts from a Mylance export, now or later, reuses that single connection.
Your first Mylance Zap: exported contacts into your CRM
GoalEach time you export a contact from Mylance, create it in your CRM and tell the team in chat who has just been added.
- 01
Create the Zap and pick the trigger
Create a new Zap, choose Mylance as the app and Contact Exported as the event, then select the Mylance connection you added earlier.
- 02
Test the trigger
Run the test: Zapier brings back the three most recent items from your Mylance account, so you map fields from a real exported contact, not a blank sample.
- 03
Add the CRM contact
Add an action with your CRM and its create contact event. Put each field from the Mylance step in the CRM field that matches it.
- 04
Add the chat message
Add a second action for your team chat. That makes it a multi-step Zap, which needs a paid plan. On the free plan, keep only the CRM step.
- 05
Test each step, then publish
Run each action once and check the new CRM record and the chat message. When both look right, click Publish to switch the Zap on.
Mylance triggers: two exports, both instant
2 events start a Zap when something happens in Mylance, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Contact Exported
Instant triggerIn Zapier“Triggers when a contact is exported from Mylance.”
Starts your Zap each time you export a contact, meaning a person, from Mylance. Your export becomes the signal, so nothing leaves Mylance unless you decide it should.
Lead Exported
Instant triggerIn Zapier“Triggers when a company is exported from Mylance.”
Fires when you export a company from Mylance. Despite the name, what comes through is an organisation, not a person, so it pairs with company records rather than contacts.
When a Mylance Zap breaks
Zapier attaches no help article to Mylance and lists no limit of its own for it. What can go wrong comes from how Zaps work in general, and from the one-way nature of this integration.
Three cases are worth knowing before you publish. For the rest, see our Zapier troubleshooting page.
Earlier exports never arrive
A Zap only reacts to what happens after it is switched on. Contacts and companies exported before that stay where they are; sending them is a separate job.A big batch held back
If a trigger suddenly sends a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.Nothing goes back into Mylance
Mylance has no action on Zapier. A Zap can carry exports out, but it cannot update, tag or create anything inside Mylance.
Need help automating Mylance with Zapier?
A person reads every message.



