Leadcontact.pro Zapier integrationAutomate Leadcontact.pro with Zapier.
The Leadcontact.pro Zapier integration gives you 1 trigger, 2 actions and 0 searches. One instant trigger when a contact is created in the CRM, and two actions to add contacts and log their history from other tools. Here is what each does and what it costs.
Verified Trustpilot reviews · AI, automation & growth agency
What the Leadcontact.pro Zapier integration does
Leadcontact.pro is a CRM sold as an online service: professionals use it to manage their contacts and every sales action around them. The Zapier integration plugs it into your other tools, in both directions: a new contact can start a Zap, and other apps can create contacts or add to their history.
Three results you can build. First, a copy of your contact base kept current: CRM Contact Created fires for each new contact, and the Zap adds it to your spreadsheet. Second, contacts that arrive on their own: Create Contact adds a person to the CRM each time another app collects one, with only the name required. Third, a contact record that tells the whole story: Create Contact History logs an exchange on a contact, with its sender email, date, subject and content.
The trigger is instant: Leadcontact.pro warns Zapier itself, so the Zap starts at once, even on the free plan, and the editor marks such a Zap with a lightning bolt. Leadcontact.pro is not a premium app either.
What Zapier does not do here: there is no search, so a Zap cannot find an existing contact before writing to it, and nothing updates or deletes a contact. A new contact is the only event that can start a Zap. To weigh Zapier against other platforms, see our Make vs Zapier comparison.
Zapier vocabulary in one minute
Seven words come back all over this page. Here they are once, in plain English.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions 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. Here, CRM Contact Created.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you. Leadcontact.pro has two.
- Task
- The unit Zapier bills: one action that completes successfully. The number on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked on a timer for new items. An instant trigger is reported by the app the moment it happens.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Connection
- Your account on an app, linked to Zapier once and then reused by every step that touches that app.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A filter or a second action makes it one, and it then needs a paid plan.
What it really costs
Leadcontact.pro is not a premium app, so it runs on the free plan. You pay in tasks, and only actions spend them.
- Premium appNo, available on the free plan
- Free plan100 tasks a month, two-step Zaps only
- CRM Contact CreatedInstant, costs no task
- What spends a taskEach of the 2 actions, when it succeeds
CRM Contact Created never costs a task. Create Contact and Create Contact History each count as one task when they succeed, and nothing when they fail. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger, one action. Creating a contact and then logging its history in the same Zap takes two actions, so it is a multi-step Zap that needs a paid plan; so does adding a filter. The interval grid below applies to polling triggers only. The Leadcontact.pro trigger is instant and fires straight away whatever your plan.
Connect Leadcontact.pro to Zapier in 3 steps
- 01
Open your connections
In your Zapier account, open the Apps page and click + Add connection. In the dialog, search for Leadcontact.pro by name and pick it from the list of apps.
- 02
Sign in to Leadcontact.pro
Click Add connection. A tab opens on Leadcontact.pro: sign in with the account whose contacts the Zap should read or write. You need write access to any contact you do not own yourself.
- 03
Grant access
Allow Zapier to reach the account. The connection then shows on the Apps page, and every Leadcontact.pro step in your Zaps reuses it, so you only do this once per account.
Your first Leadcontact.pro Zap
GoalEach new Leadcontact.pro contact that passes a filter is added as a row in your spreadsheet.
- 01
Pick the trigger
Create a Zap, choose Leadcontact.pro as the starting app and CRM Contact Created as the event, then select your Leadcontact.pro connection.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent contacts from the account, so you map fields on a real contact rather than on an empty sample.
- 03
Add the filter
From the plus icon, add a Filter step and set its three boxes: the field to look at, the rule, the value to compare with. The Zap becomes multi-step, so it needs a paid plan.
- 04
Add the action
Add the action of your spreadsheet tool, pick its connection, then map each field of the contact into the matching column of the new row.
- 05
Test, then publish
Run each step once and read what came back before moving on. When the row looks right, click Publish to switch the Zap on.
The Leadcontact.pro trigger on Zapier
1 event starts a Zap when something happens in Leadcontact.pro, and one of them is instant: the app calls Zapier straight away, whatever your plan.
CRM Contact Created
Instant triggerIn Zapier“Triggers when a new CRM contact is created.”
Starts your Zap each time a contact is added to the Leadcontact.pro CRM, and passes that contact's details on to the following steps, ready to be copied, shared or logged in another tool.
Leadcontact.pro actions on Zapier
Leadcontact.pro gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Contact
ActionIn Zapier“Creates a Contact in CRM”
Adds a new contact to the Leadcontact.pro CRM using values from the earlier steps, so a person captured in another app does not have to be typed in again.
Create Contact History
ActionIn Zapier“Create Contact History”
Logs an entry in a contact's history: who sent it, when, the subject and the content. The record then shows that exchange next to the rest of the sales follow-up.
When it breaks
Zapier ties no help article to Leadcontact.pro and no rate limit specific to the app is documented. What breaks here is what breaks on any Zap, with one loop the app makes easy.
Four situations explain most surprises, and none shows a clear error. Know them before you publish. If a Zap still misbehaves, see our Zapier troubleshooting guide.
No catch-up on existing contacts
A Zap only reacts to contacts created after it is switched on. The ones already in the CRM are never sent; moving that base is a separate job.CRM Contact Created plus Create Contact
A Zap that writes into the very place its own trigger watches fires again and again. Creating contacts from CRM Contact Created does exactly that and eats tasks fast.A sudden flood 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.History with a missing field
Create Contact History needs four values. If the source leaves one empty for a given contact, that run stops and the exchange is never logged.
Need help automating Leadcontact.pro with Zapier?
A person reads every message.
