Resources · Zapier integration

LEX Reception Zapier integrationAutomate LEX Reception with Zapier.

The LEX Reception Zapier integration gives you 1 trigger, 1 action and 0 searches. Every message your legal reception takes can start an automation as soon as it lands, and any app you already use can push a new contact back into LEX Reception.

See the 2 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why plug LEX Reception into Zapier

LEX Reception is a legal reception service, open 24/7, that takes messages for lawyers. The LEX Reception Zapier integration links it to the other apps of your practice: a message taken by the reception starts a workflow elsewhere, and a person captured elsewhere can become a contact in LEX Reception, with no copy and paste in between.

A message that reaches the right lawyer. The New Message trigger hands each message to Zapier as soon as the reception takes it. Pair it with a chat or email step and the lawyer on duty reads it without opening another dashboard.

A call log nobody types. The same trigger can write every message as a row in a spreadsheet. You can see who calls, and when, without anyone keeping the log by hand.

Contacts that already exist when they call back. The Create Contact action adds a person to LEX Reception from another app, so the name is already in your LEX Reception contacts instead of being typed twice.

What Zapier does not do here. There is no search step for LEX Reception, so a Zap cannot check whether a contact is already there before creating it. There is no action to update or delete a contact either, and no trigger other than new messages. Messages taken before your Zap was switched on stay where they are.

If those gaps matter, the n8n vs Zapier and Make vs Zapier comparisons lay out the criteria to weigh before you pick a tool.

Vocabulary

Zapier vocabulary in one minute

Seven words come back on every line of this page. Here they are 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 the Zap. Once the Zap is on, Zapier sits and waits for that event to happen.
Action
What the Zap does once it has started: the step that writes, sends or creates something for you in another app.
Task
The unit Zapier bills. One task is one action your Zap completes successfully, and your plan counts them every month.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself the moment the event happens.
Filter
A step that lets the Zap continue only when what arrived meets a condition you set, and quietly stops it otherwise.
Search step
A step that looks up something already stored in an app so later steps can reuse it. LEX Reception does not offer one.
Connection
Your LEX Reception account linked to Zapier once, then reused by every step of every Zap that touches the app.
Cost

What LEX Reception on Zapier really costs

LEX Reception is not a premium app on Zapier, so it works on the free plan. What you pay for is tasks, not triggers.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger cost0 tasks
  • Action cost1 task per successful action

The New Message trigger never costs a task, however many messages come in. Each action that succeeds counts as one task, and an action that fails is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, but each Zap stops at two steps: one trigger, one action. Add a filter or a second action and the Zap becomes a multi-step Zap, which needs a paid plan. The polling interval grid does not apply here: this trigger is instant.

Connect

Connect your LEX Reception account

  1. 01

    Open the Apps page

    In your Zapier account, go to Apps and click + Add connection. You need an existing LEX Reception account first, since Zapier only links accounts, it does not create them.

  2. 02

    Find LEX Reception

    Type LEX Reception in the search box of the dialog, pick it from the list, then click Add connection. A new browser tab opens on the LEX Reception side.

  3. 03

    Sign in and grant access

    Log in to LEX Reception in that tab and allow Zapier to reach the account. Once the tab closes, the connection shows up in your Apps list and every future Zap can reuse it.

First Zap

Your first Zap: route urgent messages to the team chat

GoalEach message LEX Reception takes is checked, and only the ones that match your condition land in your team chat.

  1. 01

    Create the Zap

    Start a new Zap and pick LEX Reception as the app that starts it, with New Message as the event. Choose the connection you set up earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent messages of the account, so you build the rest of the Zap on a real one rather than a blank.

  3. 03

    Add the filter

    From the plus icon, add a Filter step. Pick the field to read, the rule, and the value to compare with. A filter makes this a multi-step Zap, so it needs a paid plan.

  4. 04

    Add the chat action

    Add your team chat as the action and map the message details from the trigger into the text. Test this step and read what came back before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. From now on, each new message is checked as it arrives. Messages taken before this moment are not picked up.

Triggers

LEX Reception trigger

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

1

New Message

Instant trigger

In Zapier“Triggers when a new message is taken.”

Starts your Zap every time the reception takes a new message for you. Its content then flows to the next steps: send it, log it, or turn it into a follow-up.

How it fires
the app tells Zapier the moment it happens, so the Zap starts right away, whatever your plan.
When to use it
when a lawyer should hear about a call while it still matters, not hours later in a recap.
Watch out
the Zap only sees messages taken after you publish it, so older ones never show up in it.
Actions

LEX Reception action

LEX Reception 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 Contact

Action

In Zapier“Create a new contact.”

Adds a new person to the contacts of your LEX Reception account, filled from whatever earlier step you map in.

When to use it
when a person first reaches you through another tool, such as a web form, and should also exist as a LEX Reception contact.
Watch out
First Name is required, and with no search step available the action cannot tell whether that person already exists.
When it breaks

When the LEX Reception Zap breaks

Zapier publishes no help article and no documented limit specific to LEX Reception. What breaks is what breaks on any Zap.

Four cases cover almost every surprise. Read them before you publish, then check the Zapier troubleshooting guide if a run still fails.

  • Old messages never arrive

    A Zap only reacts to what happens after it is switched on. Messages taken earlier are not picked up, and moving that backlog is a separate job.

  • The Zap keeps restarting itself

    If a Zap writes back into the very place its own trigger watches, it sets itself off again and again and burns through your tasks fast.

  • A big batch gets held back

    When a trigger suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the items back instead of running them all.

  • Contacts created twice

    With no search step for LEX Reception, Create Contact cannot check first whether the contact already exists. If the same person is sent twice, the action is asked to create them twice.
Need help

Need help automating LEX Reception with Zapier?

A person reads every message.

FAQ

LEX Reception Zapier integration: questions

01Is the LEX Reception Zapier integration free?
Yes, on the free plan. LEX Reception is not a premium app, so you can connect it without paying anything. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. That covers a simple Zap such as sending every new message to your team chat. As soon as you want a filter or a second action, for example to notify the team and log the call at the same time, the Zap becomes multi-step and needs a paid plan.
02How many tasks does a LEX Reception Zap use?
One task per action that succeeds, and nothing at all for the trigger. A Zap that sends each new message to your chat uses one task per message. A Zap that also writes a spreadsheet row uses two per message, because every successful action is counted on its own. An action that fails is not counted against your plan. Waiting for new messages never costs anything either, however busy the reception gets. Keep that in mind before you stack extra actions on a busy line.
03Does the New Message trigger work in real time?
Yes. New Message is an instant trigger: LEX Reception tells Zapier the moment a message is taken, and the Zap starts right away. The plan interval grid, from 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers, so it does not slow this one down, even on the free plan. In the editor, a Zap built on it shows a lightning bolt. The type comes from the app itself and cannot be switched from the editor, so there is nothing to tune.
04What is required to connect a LEX Reception account?
An existing LEX Reception account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for LEX Reception, click Add connection, sign in to LEX Reception in the tab that opens and grant access. You also need read or write access on anything you do not own yourself and want the Zap to touch. Once it is set up, the connection is reused by every Zap you build with LEX Reception, so you only go through these steps one time per account.
05Why does Create Contact fail on some records?
Most of the time because First Name is empty. It is the one required field of the action, so a record that reaches the step without it stops there and the Zap run fails. Check the app that feeds the Zap: an optional name field on a form is a common culprit. Map a fallback value or make the field mandatory at the source, then test the step again. A failed action is not billed, so the only cost of the problem is the missing contact on the reception side.
06What if the LEX Reception operation you want is not listed?
Then Zapier cannot do it for this app today. LEX Reception exposes one trigger, New Message, and one action, Create Contact, with no search and no update or delete. A workaround is sometimes possible on the other app's side, by reacting to its own events instead of waiting on LEX Reception. Otherwise, the gap is a fair reason to compare other automation tools against what the LEX Reception account itself allows, and to check whether the missing step is really required before you build around it.
07Zapier, Make or n8n for LEX Reception?
It depends on your criteria rather than on a ranking. Zapier offers a ready-made LEX Reception connection with an instant trigger and runs on its free plan for two-step Zaps, which suits a team that wants something working quickly. If you need more steps, judge each tool on how it bills runs, on whether it has a native LEX Reception connector, and on how much setup you are willing to do yourself for anything missing. The answer can differ from one practice to the next.
Same platform

Other docs you might need on this stack.

Browse all integrations