Resources · Zapier integration

Lexopulus Zapier integrationAutomate Lexopulus with Zapier.

The Lexopulus Zapier integration gives you 2 triggers, 2 actions and 2 searches. Published intake forms and approved submissions can start automations elsewhere, and other tools can send form submissions into Lexopulus for CA or US clients without retyping.

See the 6 operations

Verified Trustpilot reviews · AI, automation & growth agency

Overview

Why connect Lexopulus to Zapier

Lexopulus is a CRM built for legal aid and non-profit organizations, organized around intake forms. The Lexopulus Zapier integration connects those forms to the rest of your tools: an event in Lexopulus starts a workflow elsewhere, and answers collected elsewhere can be submitted into a Lexopulus form.

A running list of approved cases. Submitted Form Is Approved. hands each approved submission to Zapier as soon as it is approved. Send it to a spreadsheet and you get a log of approvals that nobody keeps by hand.

A heads-up when a form goes live. Intake Form Is Published. tells your team the moment a new intake form is out, so the people who share it with the public hear about it first.

Submissions from other tools. Form Submission CA and Form Submission US send answers into a Lexopulus form, while the two Get Form Structure searches show what that form expects before you map anything.

What Zapier does not do here. There is no action to approve, edit or delete a submission, and no trigger for a new submission before approval. The actions need the form's ID and the answers packaged as structured data, which takes more care than a plain field mapping. And submissions approved before your Zap is switched on are never picked up.

If those gaps 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 submission being approved. Once the Zap is on, Zapier waits for it.
Action
What the Zap does once it has started: the step that writes, sends or submits something for you in an app.
Task
The unit Zapier bills: one action your Zap completes successfully. Your plan counts them month after month.
Polling vs instant
A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app the moment 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 something already stored in an app, such as the layout of a form, for the steps after it.
Connection
Your Lexopulus account linked to Zapier once, then reused by every step of every Zap that works with Lexopulus.
Cost

What Lexopulus on Zapier really costs

Lexopulus 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
  • Instant triggers2 of 2
  • SearchesMake the Zap multi-step

Neither trigger ever costs a task. Each action that succeeds counts as one task, and a failed action is not counted. The free plan gives you 100 tasks a month and unlimited Zaps, each capped at two steps: one trigger, one action. Add a Get Form Structure search, a filter or a second action and the Zap turns multi-step, which needs a paid plan. Both Lexopulus triggers are instant, so the polling interval grid below never slows them down.

Connect

Connect your Lexopulus account

  1. 01

    Open the Apps page

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

  2. 02

    Pick Lexopulus

    Type Lexopulus 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 Lexopulus side.

  3. 03

    Sign in and grant access

    Log in to Lexopulus in that tab and allow Zapier to reach the account. Check that it can read or write the forms the Zap will use, then let the tab close.

First Zap

Your first Zap: log approved submissions in a spreadsheet

GoalEach submission approved in Lexopulus is checked, and the ones that meet your condition become a new row in your spreadsheet.

  1. 01

    Create the Zap

    Start a new Zap, choose Lexopulus as the app that starts it and Submitted Form Is Approved. as the event. Pick the connection you set up earlier.

  2. 02

    Test the trigger

    Run the test. Zapier brings back the three most recent approved submissions of the account, so you map the rest on a real one instead of a blank sample.

  3. 03

    Add the filter

    From the plus icon, add a Filter step: the field to read, the rule, 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 detail of the submission in its column. Test the step and look at the row it created before moving on.

  5. 05

    Publish

    Click Publish to switch the Zap on. Every approval from now on is checked and logged. Submissions approved before this point are not picked up.

Triggers

Lexopulus triggers

2 events start a Zap when something happens in Lexopulus, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.

1

Intake Form Is Published.

Instant trigger

In Zapier“Triggers when an Intake Form is published.”

Starts your Zap whenever an intake form is published in Lexopulus. The details of the new form become available to the steps that follow, ready to be announced or recorded.

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 the people who share forms with the public should know a new one is live without checking Lexopulus.
Watch out
only forms published after the Zap goes live start it; forms already out stay out of the Zap.
2

Submitted Form Is Approved.

Instant trigger

In Zapier“Triggers when a submitted form is approved.”

Fires each time someone approves a submitted form in Lexopulus. Approval is the point where a request becomes real work, so this is the event most Zaps will hang on.

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 an approved case should open a follow-up in another tool or land in a shared log.
Watch out
submissions that are never approved do not reach Zapier at all, since no trigger covers that earlier stage.
Actions

Lexopulus actions

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

1

Form Submission CA

Action

In Zapier“Form Submission for CA clients”

Sends a submission into a Lexopulus form on the CA side, as if the form had been filled in directly.

When to use it
when answers for CA clients are collected in another tool and should end up in Lexopulus.
Watch out
Form ID and Payload are required, and Payload expects the answers as structured data rather than one field per question.
2

Form Submission US

Action

In Zapier“Form Submission for US clients”

Does the same job for the US side: it pushes a set of answers into a Lexopulus form for US clients.

When to use it
when your organization works with US clients and gathers their answers outside Lexopulus.
Watch out
using the US action on a CA form, or the reverse, is an easy mistake; check the version before you test.
Searches

Lexopulus searches

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

A search step finds something that already exists in Lexopulus and passes it to the steps after it. The two Lexopulus searches sit at the bottom of the Action event list, under SEARCH, and both return the structure of a public form. Neither offers a find-or-create variant.

1

Get Form Structure CA

Search

In Zapier“Get Form Structure CA”

Reads how a CA-side public form is built, so the next steps know which answers it expects.

When to use it
right before Form Submission CA, to check the form's layout while you set up the mapping.
Watch out
Form ID is required and must be the ID of a Lexopulus public form.
2

Get Form Structure US

Search

In Zapier“Get Form Structure US”

Returns the layout of a public form on the US side, question by question.

When to use it
when you build a Zap around Form Submission US and want to see the form before sending anything.
Watch out
like its CA twin, it needs the Form ID of a public form, and it makes the Zap multi-step.

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 steps that relied on it are skipped. Switched on, the Zap carries on empty-handed.
  2. Create X if it doesn't exist yet?
    This box turns a search into a find-or-create on apps that support it. Neither Lexopulus search offers it.
  3. If multiple search results are found?
    Three ways out when several items match: keep the first one (the default), stop the Zap, or hand all of them on at once.
When it breaks

When a Lexopulus Zap breaks

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

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

  • Old approvals never show up

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

  • A submission action fails

    Form Submission CA and US both need a Form ID and a Payload. A missing ID, or answers that do not match the form, stop the action there.

  • The Zap feeds itself

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

  • A big batch gets held

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

Need help automating Lexopulus with Zapier?

A person reads every message.

FAQ

Lexopulus Zapier integration: questions

01Is the Lexopulus Zapier integration free?
Yes, on the free plan. Lexopulus 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. Logging every approved submission in a spreadsheet fits within that. Adding a Get Form Structure search, a filter or a second action makes the Zap multi-step, and multi-step Zaps need a paid plan.
02How many tasks does a Lexopulus Zap use?
One task per action that succeeds, and nothing for the trigger. A Zap that writes a spreadsheet row for each approved submission uses one task per approval. If it also posts a message to your team, that is two per approval. A failed action is not counted against the plan. Waiting for new events never costs anything, however many forms are published or approved over the month. Count the actions per run before you add a second one.
03Do Lexopulus triggers work in real time?
Yes, both of them. Intake Form Is Published. and Submitted Form Is Approved. are instant triggers: Lexopulus tells Zapier as soon as the event happens, and the Zap starts right away, whatever your plan. The interval grid, 15 minutes on Free down to 1 minute on Team and Enterprise, only applies to polling triggers. In the editor, a Zap built on either trigger shows a lightning bolt. There is nothing to tune on the timing side.
04What is required to connect a Lexopulus account?
An existing Lexopulus account and a Zapier account. From the Apps page in Zapier, click + Add connection, search for Lexopulus, click Add connection, sign in on the tab that opens and grant access. The account also needs read or write access to the forms the Zap will use. For the actions and searches, keep the Form ID of the public form you plan to work with close by. The connection is then shared by every Lexopulus Zap.
05Why does Form Submission CA or US fail?
Usually because of one of its two required fields. Form ID must point to an existing Lexopulus public form, and Payload must carry the answers as structured data that matches that form. Running a Get Form Structure search first shows what the form expects. Another frequent cause is picking the CA version for a US form, or the reverse. A failed action costs no task, but the submission does not reach Lexopulus.
06What if the Lexopulus operation you want is not listed?
Then Zapier does not offer it for Lexopulus today. The integration covers two events, a published intake form and an approved submission, plus form submissions and form structure lookups for CA and US clients. There is no step to approve, edit or delete a submission. Sometimes the other app can fill the gap by reacting to its own events. Otherwise, compare what other automation tools expose for Lexopulus before building around the missing step.
07Zapier, Make or n8n for Lexopulus?
It depends on your criteria, not on a ranking. Zapier offers a ready-made Lexopulus connection with two instant triggers, and simple two-step Zaps run on its free plan. The submission actions expect structured data, so weigh how comfortable each tool makes that kind of mapping. Also check whether the tool has a native Lexopulus connector at all, and how each one bills Zaps with several steps. The right pick depends on your team, not on the tool.
Same platform

Other docs you might need on this stack.

Browse all integrations