Sending leads to Zapier
Connect Marketli to Zapier so leads flow into the tools you already use, such as Connective Mercury. Send every new lead as it arrives, or only the ones your team chooses with an automation.
Marketli can hand a lead to Zapier. From there a Zap can create the person in your CRM, post to a channel, add a row to a sheet, or anything else Zapier can reach. The most common use is pushing leads into Connective Mercury, whose Zapier app can find or create a person and open an opportunity.
There are two ways to send, and each has its own trigger in Zapier:
| In Zapier, choose | What it sends |
|---|---|
| New Lead | Every new lead, the moment it arrives. Nothing to set up in Marketli beyond the key. |
| Lead Sent by an Automation | Only the leads a team member sends, by running an automation from the lead. |
Only company owners and admins can set this up. It is included for every business on Marketli, whatever you pay for.
1. Generate an API key
- Go to Company → Integrations.
- Click New key, give it a label such as Zapier, and click Generate key.
- Copy the key straight away. It starts with
mk_live_and is shown once only.
A key belongs to your company, not to a person. Revoking it turns off every Zap that was connected with it.
2. Connect Marketli in Zapier
- In Zapier, create a new Zap and choose Marketli as the trigger app. Until the app is listed publicly, use the invite link shown on the Integrations tab.
- Pick the trigger: New Lead for every lead, or Lead Sent by an Automation for the ones your team sends by hand (see below).
- When Zapier asks you to connect an account, paste the API key. The connection is named after your company and the key's label.
- Decide whether to Include notes. Notes carry the enquiry message and anything your team typed, which can include personal details, so this is off unless you turn it on.
- Click Test trigger. Zapier pulls your three most recent leads as samples, in exactly the shape a live lead arrives.
3. Map the lead into Mercury
Add a Mercury Connect action. The fields Marketli sends line up with what Mercury asks for:
| Marketli field | Use it for |
|---|---|
| First name, Last name | Mercury's person name. A one-word name arrives as a first name with an empty last name. |
| Mercury requires an email to create a person. Add a Zapier filter for Email exists so a lead without one does not stop the Zap. | |
| Phone (E.164) | Australian numbers arrive as +61. |
| Lead source, Status | The source and stage names you use in Marketli. |
| Contact is new | True when this lead created a new contact, false when the person was already in your contacts. Useful for choosing Find or create person over Create person. |
| Lead URL | A link back to the lead in Marketli, handy in an opportunity note. |
Use Mercury's Find or create person rather than Create person. If a lead is ever delivered twice, the person is matched rather than duplicated.
Sending only the leads you choose
Use this when you do not want every enquiry in your CRM, only the ones worth pursuing.
- Go to Leads → Automations and click New automation.
- Name it, for example Send to Mercury, and pick the trigger Started from a lead.
- Add one step: Send to Zapier. There is nothing to configure. Save, then switch the automation on.
- In Zapier, build the Zap with the trigger Lead Sent by an Automation.
- Open any lead, click Run automation, and choose it.
The lead is queued for Zapier straight away, and Marketli says Queued for Zapier. Queued means Marketli has it safely in line; whether Zapier accepted it shows in the delivery log on the Integrations tab. If no Zap is connected, Marketli tells you instead of queuing anything.
A few things to know:
- Sending the same lead again sends it again. Marketli asks first, because your CRM will usually create a second opportunity.
- Do not run both triggers into the same CRM unless you want leads twice. A lead that a New Lead Zap already sent will arrive again when someone sends it by hand.
- More than one automation? Every Zap using this trigger receives every automation's leads. Add a Zapier Filter step on Automation name to keep them apart.
- An automation can have one Send to Zapier step, and the step is available on automations started from a lead.
- A lead whose contact is archived is not sent.
What arrives, and when
With New Lead, each new lead is delivered once, within a couple of minutes of being created. With Lead Sent by an Automation, the lead is delivered within a couple of minutes of someone running the automation, and it also carries the automation's name. The name, email and phone are the contact on file: if an enquiry comes in from someone already in your contacts, Marketli keeps the details you hold and records what they typed in the lead's notes.
Leads created while lead automations are paused for a flood of submissions are not sent.
The delivery log
The Integrations tab lists every connected Zap and the recent deliveries to it: when, whether it was accepted, the response code, and how many attempts it took. A delivery that Zapier could not accept is retried for a few hours and then marked as failed. If Zapier reports that a Zap no longer exists, the connection is turned off and shown as such.
Turning it off
Switch the Zap off in Zapier, or revoke the key in Marketli. Either stops deliveries. Revoking the key also disconnects every other Zap made with it.
Still stuck? Email help@marketli.app.