Resources · Zapier integration

McGill CRM Zapier integrationAutomate McGill CRM with Zapier.

The McGill CRM Zapier integration has 0 triggers, 1 action and 0 searches. McGill CRM only receives data from a Zap, through Create Lead. This page covers what that single action does, what it costs on each plan, how to connect the account and where it breaks.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the McGill CRM Zapier integration does for you

The McGill CRM Zapier integration gets new leads into McGill CRM from another app, so nobody retypes them. McGill CRM is a sales and CRM tool built to coordinate the sale of new real estate. On Zapier it offers one action, Create Lead, and nothing that can start a Zap. Every Zap therefore begins in another app and ends in McGill CRM.

Three results you can build with that one action. A lead from every web form. A submission on your site's form becomes a lead through Create Lead, and your sales team stops copying names by hand. A lead from the shared sheet. When marketing adds a row to the spreadsheet it keeps, the same action files that row as a lead. A lead only when it qualifies. Put a filter between the source and Create Lead, and only the entries that match your rule reach the CRM.

What Zapier does not do for McGill CRM matters just as much. It cannot start a Zap from the app: there is no trigger, so a new lead or a signed contract inside McGill CRM never sets anything off. There is no search step either, so a Zap cannot check whether a lead already exists before it creates one. And Create Lead is the only operation in the editor, which means no update and no delete. The contract and e-signature side stays inside McGill CRM.

Weighing the other platforms for this flow? Open our Make vs Zapier comparison or our n8n vs Zapier comparison.

Vocabulary

Zapier vocabulary in one minute

Eight words you will meet in the editor, in plain English.

Zap
The automation you build on Zapier: one trigger, then one or more actions that run each time the trigger event happens.
Trigger
The event in an app that starts a Zap. McGill CRM has none, so the trigger always comes from another app in your flow.
Action
What the Zap does once it has started. Here, Create Lead is the action that writes a new lead into McGill CRM for you.
Task
The unit Zapier bills: one action completed successfully. Each lead that Create Lead adds counts as one task on your plan.
Polling vs instant
Polling: Zapier asks the source app for new items on a timer. Instant: the app reports the event to Zapier itself, with no wait.
Filter
A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
Multi-step Zap
Any Zap beyond one trigger and one action. A second action or a filter makes it one, and it then needs a paid plan.
Connection
Your McGill CRM account linked to Zapier once, then reused by every step of every Zap that uses the app.
Cost

What a McGill CRM Zap really costs

The short version: only Create Lead costs anything, one task per lead it creates.

  • Tasks per lead created1
  • Tasks for the trigger0
  • Free plan100 tasks a month, two-step Zaps
  • Reserved to paid plansNo

The trigger in the other app never costs a task, and neither does Zapier checking for new data. An action that fails is not counted. The free plan gives 100 tasks a month and unlimited Zaps of two steps each. McGill CRM is not reserved to paid plans, so a source-to-lead Zap runs there. Add a filter and the Zap becomes multi-step, which needs a paid plan. The grid below applies to the other app's trigger when it polls, never to an instant one.

Connect

Connect McGill CRM to Zapier in 3 steps

  1. 01

    Open Apps and add a connection

    In your Zapier account, open the Apps page and click + Add connection. Have your McGill CRM login at hand before you start: the connection links an existing account.

  2. 02

    Find McGill CRM in the dialog

    Type McGill CRM in the search box of the dialog, pick it, then click Add connection. A new tab opens on the McGill CRM sign-in. The connection you create here is reused by every Zap that touches the app.

  3. 03

    Sign in and grant access

    Sign in to McGill CRM in that tab and grant Zapier access to the account. If the Zap has to write into a space someone else owns, get write access to it first.

First Zap

Your first Zap: from a form to a McGill CRM lead

GoalTurn each qualifying form submission into a lead in McGill CRM.

  1. 01

    Build: pick the starting app

    Start a new Zap, choose your form tool as the app that starts it and its new-submission event as the trigger. Connect that account the same way you connected McGill CRM.

  2. 02

    Test the trigger

    Run the trigger test: Zapier brings back the three most recent submissions of the connected account. Pick a real one, so every later step is mapped on actual data.

  3. 03

    Add the filter

    Add a Filter step from the plus icon and fill its three boxes: the field to look at, the rule, the value to compare with. Use text rules for text, number rules for numbers. The filter makes this a multi-step Zap, so it runs on a paid plan.

  4. 04

    Add Create Lead and map it

    Add McGill CRM as the action app, choose Create Lead and map the submission fields into the lead. The editor shows which fields the action asks for; check them at test.

  5. 05

    Test, then publish

    Test the action once and open McGill CRM to look at the lead it created. If it reads right, click Publish to switch the Zap on.

Actions

The McGill CRM action on Zapier

McGill CRM gives you 1 action. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Lead

Action

In Zapier“Create Lead on McGillCRM”

Adds a new lead to McGill CRM from whatever the earlier step carried: a form entry, a sheet row, an email. Each lead it creates counts as one task.

When to use it
any source that captures prospects outside McGill CRM and that your sales team should follow up inside the CRM.
Watch out
with no search step for this app, the Zap cannot check for an existing lead first, so test with a known contact and look at the result.
When it breaks

When a McGill CRM Zap breaks

Zapier attaches no help article to McGill CRM and no app-specific limit is on record, so the failures to plan for are Zapier's general ones.

Each case below comes from how Zapier treats every app. When one of them hits a live Zap, see our Zapier troubleshooting guide.

  • No backlog import

    A Zap only reacts to what happens after you switch it on. Prospects captured before that stay where they are; moving them is a separate job.

  • Bulk imports can be held back

    If the source app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold that batch back.

  • Loops when you add steps

    As a general precaution: a Zap that writes into the place its own trigger watches can set itself off again and burn through tasks fast.

  • Duplicates are only filtered upstream

    On a polling trigger Zapier remembers what it has already seen, so one item never starts the Zap twice. Nothing checks McGill CRM itself for an existing lead.
Need help

Need help automating McGill CRM with Zapier?

A person reads every message.

FAQ

McGill CRM Zapier integration: FAQ

01Is the McGill CRM Zapier integration free?
Yes, it works on the free Zapier plan. McGill CRM is not one of the apps Zapier reserves to paid plans, and the free plan allows an unlimited number of Zaps, each limited to two steps: one trigger and one action. A Zap that starts in your form tool and runs Create Lead fits that shape exactly. You get 100 tasks a month on that plan. Add a filter or a second action and the Zap becomes multi-step, which moves it to a paid plan.
02How many tasks does Create Lead use?
One task per lead created. Zapier counts a task each time an action completes successfully, so a Zap that creates 40 leads in a month uses 40 tasks. The trigger in the other app costs nothing, and Zapier checking for new items costs nothing either, however often it checks. An action that fails is not counted. If you add a second action in another app, each success counts on its own, so the same flow uses twice as many tasks.
03Does McGill CRM get new leads in real time through Zapier?
It depends on the app that starts the Zap, since McGill CRM has no trigger of its own. If that app's trigger is instant, it reports the event to Zapier itself and Create Lead runs straight away, whatever your plan. If it is a polling trigger, Zapier checks it on a timer: every 15 minutes on Free, every 2 minutes on Professional, every minute on Team and Enterprise. In the editor, a Zap built on an instant trigger shows a lightning bolt.
04What does connecting McGill CRM to Zapier require?
An existing McGill CRM account and a Zapier account. On the Apps page of Zapier, click + Add connection, search for McGill CRM, click Add connection, sign in to McGill CRM in the tab that opens and grant Zapier access to the account. If the Zap must write into a space you do not own, you also need write access to it. The connection is saved once, and every later Zap that uses McGill CRM picks it up again.
05Can a Zap start from something that happens in McGill CRM?
No. McGill CRM offers no trigger on Zapier, so nothing that happens inside it, a new lead or a signed contract, can start a Zap. The app only receives data: Create Lead is its single action. Every Zap therefore begins in another app, such as a form, a sheet or an inbox, and ends with a lead in McGill CRM. Reacting to activity inside McGill CRM is not something the Zapier editor offers for this app.
06What if the McGill CRM operation you need is not listed?
Then Zapier does not offer it for McGill CRM. The app page lists one operation, Create Lead, read on version McGillCrmCLIAPI@1.0.2. Updating a lead, deleting it or looking one up is not part of that list, and no setting in the editor adds it. Check the McGill CRM page on Zapier before you design a flow, because the list can change between versions, and keep the remaining work inside McGill CRM itself.
07Zapier, Make or n8n for McGill CRM?
Choose by criteria rather than by brand. On Zapier, McGill CRM is available, it is not reserved to paid plans, and a two-step source-to-lead Zap runs on the free plan. Its limits are the single action and the absence of any trigger. For Make or n8n, the first check is whether McGill CRM has a module or a node there at all, which this page does not cover. After that, compare how each tool handles the other apps in your flow and the number of leads you expect to create.
Same platform

Other docs you might need on this stack.

Browse all integrations