Resources · Zapier integration

LEXZUR Zapier integrationAutomate LEXZUR with Zapier.

The LEXZUR Zapier integration gives you 1 trigger, 4 actions and 8 searches. New invoices can feed your other tools, and those tools can create clients, matters, practice areas and invoice payments in LEXZUR, with searches to find the records they point to.

See the 13 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why connect LEXZUR to Zapier

LEXZUR is a legal tech platform that brings clients, matters, invoices and payments into one place. The LEXZUR Zapier integration links it to the rest of your tools: a new LEXZUR invoice can start a workflow elsewhere, and data from other apps can create clients, matters and payments in LEXZUR without retyping.

An invoice log that fills itself. New Invoice passes each new invoice to Zapier. Write it to a spreadsheet and finance has a running list without exporting anything from LEXZUR.

Matters opened from wherever requests arrive. Create Matter opens a corporate matter from another tool, with Find Practice Area and Find Assigned Team in front of it to supply the values it requires.

Payments recorded where they are received. Create Invoice Payment books a payment against an invoice, so LEXZUR reflects what your bank or payment tool already knows. Find Invoice helps match the right one.

What Zapier does not do here. The only trigger is New Invoice, and it is a polling trigger, so it is not instant. There is no action to update or delete a record. Most useful Zaps chain a search before an action, which makes them multi-step. And invoices created before your Zap goes live are not picked up.

If those limits weigh on your choice, the n8n vs Zapier and Make vs Zapier comparisons lay out the criteria to look at.

Vocabulary

Zapier vocabulary in one minute

Eight Zapier words come up on 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, such as a new LEXZUR invoice. Once the Zap is on, Zapier watches for it.
Action
What the Zap does once it has started: the step that creates a client, a matter or a payment for you.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan is a monthly count of those.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app as soon as the event happens.
Filter
A step that lets the Zap carry on only when what arrived meets a condition you set, and stops it otherwise.
Search step
A step that looks up a record already in LEXZUR, such as a practice area or a user, so later steps can use it.
Connection
Your LEXZUR account linked to Zapier once, then reused by every step of every Zap that works with LEXZUR.
Cost

What LEXZUR on Zapier really costs

LEXZUR is not a premium app on Zapier, so the free plan is enough to start. You pay in tasks, and only for actions that work.

  • Premium appNo, free plan works
  • Free plan100 tasks a month, two-step Zaps
  • Trigger typePolling, interval set by plan
  • SearchesMake the Zap multi-step

The New Invoice trigger never costs a task, however often Zapier checks for new invoices. Each action that succeeds counts as one task, and a failed one is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each capped at two steps. Since Create Matter and Create Invoice Payment usually need a search in front of them, many LEXZUR Zaps turn multi-step, and a search or a filter means a paid plan. New Invoice is a polling trigger, so the interval grid below decides how fast it reacts.

Connect

Connect your LEXZUR account

  1. 01

    Open the Apps page

    In Zapier, go to Apps and click + Add connection. You need an existing LEXZUR account first: Zapier links an account you already have, it does not open one.

  2. 02

    Pick LEXZUR

    Type LEXZUR in the search box of the dialog that appears, select it from the list, then click Add connection. A new browser tab opens on the LEXZUR side.

  3. 03

    Sign in and grant access

    Log in to LEXZUR in that tab and allow Zapier to reach the account. Check that it can read invoices and write the clients, matters and payments your Zaps will create.

First Zap

Your first Zap: log new invoices in a spreadsheet

GoalEvery new LEXZUR invoice that passes your condition becomes a row in your finance spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap, choose LEXZUR as the app that starts it and New Invoice as the event. Pick your connection, then set the required Organization and Status.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent invoices that match, so you map the rest on a real invoice rather than a blank sample.

  3. 03

    Add the filter

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

  4. 04

    Add the spreadsheet row

    Add your spreadsheet as the action and place each invoice detail in its column. Test the step and check the row before going further.

  5. 05

    Publish

    Click Publish to switch the Zap on. New invoices are picked up at your plan's interval. Invoices created before this point are not.

Triggers

LEXZUR trigger

1 event starts a Zap when something happens in LEXZUR. Zapier checks for them at the interval your plan allows.

1

New Invoice

Polling trigger

In Zapier“Triggers when a new invoice is created.”

Starts your Zap when a new invoice is created in LEXZUR. You narrow it down to one organization and one invoice status when you set it up, so only the invoices you care about come through.

How it fires
Zapier goes and looks at regular intervals, and how often depends on your plan: every 15 minutes on the free one.
When to use it
when finance wants every new invoice copied into a report, a ledger or a reminder tool.
Watch out
Status and Organization are both required, so one Zap watches one organization and one status at a time.
Actions

LEXZUR actions

LEXZUR gives you 4 actions. For each one: what it does for you, when to reach for it, and what to watch out for.

1

Create Client

Action

In Zapier“Create Client if not exist.”

Adds a client to LEXZUR when it does not exist yet, from details another app collected.

When to use it
when new clients first appear in a form or a sales tool and should exist in LEXZUR before any matter is opened.
Watch out
Name and Client Type are required, so map both or the step fails.
2

Create Invoice Payment

Action

In Zapier“Creates an Invoice Payment”

Records a payment against an existing LEXZUR invoice.

When to use it
when payments show up first in your bank or payment tool and the payment should be on record against the LEXZUR invoice too.
Watch out
six fields are required, including Invoice Id, Deposit To and Payment Method; Find Invoice can supply the Invoice Id.
3

Create Matter

Action

In Zapier“Creates a new corporate matter.”

Opens a new corporate matter in LEXZUR.

When to use it
when requests come in through another tool and each one should become a matter without manual entry.
Watch out
Matter Name, Practice Area, Arrival Date, Priority and Assigned Team are all required; Find Practice Area and Find Assigned Team can supply two of them.
4

Create Practice Area

Action

In Zapier“Creates a Practice Area in Lexzur.”

Creates a new practice area in LEXZUR, the category matters are filed under.

When to use it
when your list of practice areas is kept in another tool and LEXZUR should follow it.
Watch out
Practice Area Name and Prefix are required; to avoid duplicates, the Find or Create Practice Area variant of the search may suit you better.
Searches

LEXZUR searches

8 search steps look for data that already exists in LEXZUR, so a later step can use it.

A search step finds a record that already exists in LEXZUR and hands it to the steps that follow. In the editor, the eight LEXZUR searches sit at the bottom of the Action event list under SEARCH. They matter here because the LEXZUR actions ask for values, such as a practice area or a team, that a search can supply. Two of them also come as find-or-create variants.

1

Find Practice Area

SearchFind or create

In Zapier“Find a Practice Area in Lexzur.”

Looks up a practice area by its case type name. In the editor it also appears as Find or Create Practice Area: the same search with the create box ticked, not a separate operation.

When to use it
just before Create Matter, which requires a practice area.
Watch out
Case Type Name is required.
2

Find Account

Search

In Zapier“Finds an Account by Id.”

Fetches an account from its ID.

When to use it
when an earlier step carries an account ID and the next one needs that account's details.
Watch out
Account Id is required, so this search confirms a known account rather than browsing by name.
3

Find Matter Contacts/Companies

SearchFind or create

In Zapier“Find a Matter Contact/company in Lexzur.”

Finds a contact or company linked to matters in LEXZUR. Its find-or-create twin, Find or Create Client, uses the same search with the create box ticked, so a missing client gets created on the spot.

When to use it
before opening a matter for someone who may or may not already be in LEXZUR.
Watch out
the two editor lines are one operation, counted once.
4

Find Invoice

Search

In Zapier“Finds an invoice”

Locates an existing invoice in LEXZUR.

When to use it
ahead of Create Invoice Payment, to get the Invoice Id the payment must point to.
Watch out
if several invoices match, the multiple-results setting decides which one the payment lands on, so check it before publishing.
5

Find Matter Container

Search

In Zapier“Find a Matter Container in Lexzur.”

Retrieves a matter container from LEXZUR so later steps can refer to it.

When to use it
when a Zap needs to place or reference work inside an existing container rather than create a new one.
Watch out
test it on a real container first and read what comes back before mapping anything from it.
6

Find Case Stage

Search

In Zapier“Find a Case Stage in Lexzur.”

Returns a case stage as LEXZUR defines it.

When to use it
when another tool names a stage and the Zap needs the matching LEXZUR value for a later step.
Watch out
if no stage matches and the no-result setting stays on its default, the Zap stops at this step.
7

Find Assigned Team

Search

In Zapier“Find an Assigned Team in Lexzur.”

Returns a team you can assign matters to.

When to use it
right before Create Matter, which requires an Assigned Team.
Watch out
if the team name coming from your other tool does not match LEXZUR, the search finds nothing and the matter is never created.
8

Find User

Search

In Zapier“Find a User in Lexzur.”

Finds a user of your LEXZUR account.

When to use it
when a later step should name or notify the person in charge, and you only have their name from another app.
Watch out
the user must exist in the connected LEXZUR account; people from outside it will not be found.

The three settings every search exposes

  1. Successful if no search results are found?
    Left on its default, a search that finds nothing stops the Zap there and the dependent steps are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    Ticking this box turns the search into a find-or-create: the setting above disappears and the step asks for what it needs to create the missing record.
  3. If multiple search results are found?
    Three ways out when several records match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a LEXZUR Zap breaks

Zapier links no help article and no documented limit to LEXZUR. What breaks is what breaks on any Zap, plus the many required fields of its actions.

Four cases cover most surprises. Read them before you publish, and turn to the Zapier troubleshooting guide if a run still fails.

  • A required field is empty

    Create Matter needs five fields and Create Invoice Payment six. One empty value, often a practice area or team the search did not find, stops the action.

  • Old invoices never arrive

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

  • The Zap feeds itself

    If a Zap writes into what its own trigger watches, it sets itself off again and again and burns through your tasks quickly.

  • A big batch gets held back

    When New Invoice suddenly returns a huge batch, after a bulk import for instance, Zapier's flood protection can hold the items back.
Need help

Need help automating LEXZUR with Zapier?

A person reads every message.

FAQ

LEXZUR Zapier integration: questions

01Is the LEXZUR Zapier integration free?
Yes, on the free plan. LEXZUR is not a premium app, so you can connect it and run Zaps without paying. The free plan gives you 100 tasks a month and unlimited Zaps, each limited to two steps: one trigger and one action. Copying every new invoice into a spreadsheet fits within that. Creating a matter usually needs a Find Practice Area or Find Assigned Team search first, and any search, filter or second action makes the Zap multi-step, which needs a paid plan.
02How many tasks does a LEXZUR Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that writes each new invoice to a spreadsheet uses one task per invoice. Zapier checking LEXZUR for new invoices costs nothing, however often it looks. A failed action is not counted against the plan. Keep in mind that a Zap with two actions after the trigger uses two tasks per run, so the count grows with every step you add.
03Does the LEXZUR trigger work in real time?
No. New Invoice is a polling trigger: Zapier asks LEXZUR for new invoices at a fixed interval, and that interval depends on your plan. It is 15 minutes on Free, 2 on Professional and 1 on Team and Enterprise. On paid plans the interval can be changed, and a check can also be run by hand from the editor. Zapier remembers the invoices it has already seen, so the same invoice never starts the Zap twice.
04What is required to connect a LEXZUR account?
An existing LEXZUR account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for LEXZUR, click Add connection, sign in on the tab that opens and grant access. The account also needs read or write access to what the Zap will touch. For New Invoice and Create Invoice Payment, it must see the organization you select, since both require one. The connection is then reused by every LEXZUR Zap you build.
05Why does Create Matter fail in LEXZUR?
Usually because one of its five required fields is empty. Matter Name, Practice Area, Arrival Date, Priority and Assigned Team must all be filled. Practice area and team often come from Find Practice Area and Find Assigned Team: if a name from your other tool does not match LEXZUR, the search finds nothing and the matter is skipped. Test each search on a real value and check its no-result setting before publishing.
06What if the LEXZUR operation you want is not listed?
Then Zapier does not offer it for LEXZUR today. The integration has one trigger for new invoices, four creation actions for clients, matters, practice areas and invoice payments, and eight searches. There is nothing to update or delete a record, and New Invoice is the only event that can start a Zap. A search step sometimes bridges the gap. Otherwise, compare what other automation tools expose for LEXZUR before building around the missing step.
07Zapier, Make or n8n for LEXZUR?
It depends on your criteria, not on a ranking. Zapier offers a ready-made LEXZUR connection with 13 visible operations, and simple two-step Zaps run on its free plan. Many LEXZUR Zaps need a search before the action, so compare how each tool bills runs with several steps. Check also whether the tool has a native LEXZUR connector at all, and how much setup your team is ready to handle for the rest.
Same platform

Other docs you might need on this stack.

Browse all integrations