Resources · Zapier integration

lemcal Zapier integrationAutomate lemcal with Zapier.

The lemcal Zapier integration gives you 1 trigger, 0 actions and 0 searches. Each time someone books a meeting through lemcal, Zapier hears about it on the spot and can pass the booking to the rest of your tools. It does not write anything back.

See the 1 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

What the lemcal Zapier integration actually does

lemcal is a meeting booking tool: people pick a slot, and lemcal handles the schedule and works to cut down on no-shows. On Zapier, it brings one event: a new meeting has just been booked. Everything you build starts there, the instant the booking happens, and carries it to another app.

Three results come out of that single trigger. A contact in your CRM for every person who books: New Meeting hands over the booking, and the next step creates or enriches the record, so nobody copies names from the calendar. A running log of every meeting booked: one spreadsheet row per booking, handy for seeing at a glance how many meetings come in. A heads-up to whoever takes the call: a message in the team chat as soon as the slot is taken.

What Zapier does not do for lemcal: there is no action and no search. Zapier cannot create a meeting, cancel one or look one up in lemcal. The one event reported is a new booking, nothing else. Every Zap therefore ends in another tool, and the free plan allows one such step behind the trigger. The upside is speed: since the trigger is instant, the plan you are on never delays it.

Weighing other platforms for this? Open our n8n vs Zapier comparison, or see our Zapier review.

Vocabulary

Zapier vocabulary in one minute

Six words come back throughout 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 the trigger event happens.
Trigger
The event in an app that starts the Zap. Once the Zap is on, Zapier waits for it. With lemcal: a meeting just booked.
Action
What the Zap does once it has started: the step that writes, sends or moves something for you, always in another app here.
Task
The unit Zapier bills: one action your Zap completes successfully. The figure on your plan counts those, nothing else.
Polling vs instant
Polling: Zapier checks the app on a timer. Instant: the app tells Zapier itself, the moment it happens. lemcal is instant.
Filter
A step that lets the Zap carry on only when what arrived meets the condition you set, and stops it otherwise.
Cost

What lemcal really costs you on Zapier

lemcal is not a premium app, so it runs from the free plan. What you spend is tasks, and only the actions in other apps produce them.

  • Premium appNo, available on the free plan
  • Free plan100 tasks a month, two-step Zaps only
  • TriggerNever counted, instant on every plan
  • Failed actionNot counted

The trigger never costs a task, however many meetings get booked. Each action that completes counts one task; a failed one does not. The free plan gives you 100 tasks a month and two-step Zaps only: one trigger, one action. A booking sent to your CRM fits. Add a filter or a second action and the Zap becomes multi-step, which needs a paid plan. The interval grid below does not apply: New Meeting is instant on every plan.

Connect

Connect your lemcal account in three steps

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. A connection is your lemcal account linked to Zapier once, then reused by every lemcal step you build.

  2. 02

    Pick lemcal in the dialog

    Search for lemcal in the dialog, select it and click Add connection. You need a lemcal account, plus access to any booking pages you do not own but want the Zap to follow.

  3. 03

    Sign in and grant access

    A new tab opens on lemcal. Sign in, then grant Zapier access to the account. Back in Zapier, the connection appears in the list, ready for the New Meeting trigger.

First Zap

Your first Zap: add every lemcal booker to your CRM

GoalEach meeting booked through lemcal creates a contact in your CRM, filtered so only the bookings that matter to sales get through.

  1. 01

    Create the Zap and pick the trigger

    Start a new Zap, choose lemcal and New Meeting, then select your connection. Tick Any Meeting Type if every kind of booking should count.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent meetings of the account, so pick a real booking to map the next steps. The lightning bolt confirms it is instant.

  3. 03

    Add the filter

    Click the plus icon and choose Filter. Fill the three boxes: the booking field to look at, the rule, and the value to compare with. Use a text rule on text.

  4. 04

    Add the CRM action

    Add your CRM with a new-contact action and map the booker's details from the meeting. This is the step that costs a task, one per contact created.

  5. 05

    Test and publish

    Test each step and read what came back, then click Publish. With the filter it is a multi-step Zap, so it needs a paid plan.

Triggers

The lemcal trigger

1 event starts a Zap when something happens in lemcal, and one of them is instant: the app calls Zapier straight away, whatever your plan.

1

New Meeting

Instant trigger

In Zapier“Triggers when a new meeting is booked.”

Starts the Zap whenever someone books a meeting through lemcal, and passes the booking to whatever step comes next. It is the only door between lemcal and the rest of your tools on Zapier.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan
When to use it
every new booking should create a contact, post an alert or add a row somewhere, without anyone watching the calendar.
Watch out
check the Any Meeting Type box while you set it up; it is the option to tick when the Zap should fire on every meeting type.
When it breaks

When the lemcal Zap breaks

Zapier attaches no help article to lemcal, and no rate limit specific to the app is documented. The usual failures come from how Zapier itself works.

These three cases cover what goes wrong most on a Zap that starts with a booking and writes elsewhere. When a Zap stops and you cannot see why, open our Zapier troubleshooting guide.

  • Past bookings never arrive

    A Zap only reacts to what happens after it is switched on. Meetings booked before that stay in lemcal; sending them on is a separate job.

  • A wave of bookings gets held back

    When a trigger suddenly sends a huge batch, after an import for instance, Zapier's flood protection can hold the run back instead of firing on all of it.

  • The filter never lets anything through

    Filter rules are typed: a text rule only works on text, a number rule only on numbers. Picking the wrong type is the usual reason a filter stays shut.
Need help

Need help automating lemcal with Zapier?

A person reads every message.

FAQ

lemcal Zapier integration: frequent questions

01Is the lemcal Zapier integration free?
Yes, as long as each Zap stays at two steps. lemcal is not a premium app, so the free plan accepts it, with 100 tasks a month. Sending each new booking to your CRM is two steps and costs nothing. Adding a filter so only some meeting types reach the CRM, or a second action such as a chat alert, makes the Zap multi-step, and that needs a paid plan. Count the steps before you build.
02How many tasks does a lemcal Zap use?
One per action that succeeds, nothing for the trigger. A Zap that creates a CRM contact and also adds a spreadsheet row spends two tasks per meeting booked. A failed action is not counted. Since lemcal has no action of its own, every task you spend is in another app, which makes the bill easy to predict: number of bookings times number of actions in the Zap, nothing hidden on the lemcal side.
03Does lemcal trigger Zapier in real time?
Yes. New Meeting is an instant trigger: lemcal tells Zapier the moment a meeting is booked, and the Zap starts straight away. That holds on every plan, the free one included, so the interval grid of the plans does not apply. The editor marks the trigger with a lightning bolt. The type is decided by the app itself and cannot be changed from the editor, so there is nothing to tune on your side.
04What does it take to connect lemcal to Zapier?
A lemcal account, and access to any booking pages you do not own but want the Zap to follow. Open the Apps page in Zapier, click + Add connection, pick lemcal, click Add connection, then sign in to lemcal in the tab that opens and grant access. The connection is saved once, and every lemcal step in every Zap reuses it, with nothing to redo for the next Zap on the same account.
05Why are some lemcal bookings missing from the Zap?
Start with two checks. First, the trigger setting: New Meeting offers an Any Meeting Type option, the one to tick when every type of meeting should start the Zap, so make sure it matches what you expect. Second, timing: a Zap only sees bookings made after it was published, so meetings booked before that will never show up, whatever the trigger settings. If a filter sits behind the trigger, check its rule type too, since a text rule on a number never passes.
06What if the lemcal operation you need is not listed?
Then Zapier cannot do it for lemcal today, and no setting will unlock it. New Meeting is the only operation the editor shows: no action, no search, nothing to create or cancel a meeting. A common route is to let lemcal report the booking and handle the follow-up in another app that has the actions you are missing. If that gap is a blocker, compare what other automation platforms offer for lemcal.
07Zapier, Make or n8n for lemcal?
It depends on your criteria, not on a ranking. Zapier connects quickly, its lemcal trigger is instant on every plan, and the free plan covers a two-step Zap such as sending each booking to a CRM. Its limits here are a single trigger and no action. Make and n8n work differently, and their lemcal coverage has to be checked app by app. Weigh setup time, cost per run and the number of steps each Zap needs.
Same platform

Other docs you might need on this stack.

Browse all integrations