Lecom Zapier integrationAutomate Lecom with Zapier.
The Lecom Zapier integration gives you 3 actions, 0 triggers and 0 searches. Everything runs one way: another app starts the Zap, and Zapier opens a process in Lecom, fills in its activity data, or approves or rejects an activity.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lecom Zapier integration actually does
Lecom is a process platform: work moves through processes, each made of activities with forms to fill and statuses to set. Zapier connects it to your other apps. When something happens elsewhere, Zapier pushes the matching move into Lecom, so a process starts or advances without anyone retyping it.
Three outcomes, each tied to a real operation. A process that starts on its own: Open Process launches a new process instance in Lecom each time your form receives an answer. Forms that fill themselves: Update Activity Data adds or changes values in the form fields of an activity in a running instance, with data the other app already holds. A decision recorded without a login: Approve or Reject Activity sets the status of an activity, so a yes or no given in another tool lands in the process.
What Zapier does not do here matters just as much. There is no Lecom trigger: nothing that happens inside Lecom, a finished activity or a new instance, can start a Zap. There is no search either, so a Zap cannot look up an instance by its content. You need the instance ID or a selection from the list, and the steps before must carry it. Everything flows into Lecom, never out of it.
To weigh Zapier against other platforms on criteria rather than hype, the Make vs Zapier comparison is a good start.
Zapier vocabulary in one minute
Seven words come back on every Zapier screen. Here they are once, in plain English.
- Zap
- The automation you build: 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. With Lecom it always comes from another app, since Lecom offers none.
- Action
- What the Zap does once started: the step that writes or sends something for you, like Open Process.
- Task
- The unit Zapier bills: one action that completed successfully. The count on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger calls Zapier itself as soon as the event happens.
- Filter
- A step that lets the Zap go on only when the incoming data meets a condition you set, and stops it otherwise.
- Connection
- Your Lecom account linked to Zapier once, then reused by every step that talks to Lecom in any of your Zaps.
What it really costs to run
Lecom is not a premium app, so it works on the free plan. You pay in tasks, and only the Lecom actions produce them.
- Premium appNo, works on the free plan
- Free plan100 tasks a month, two-step Zaps only
- CountedEach successful Lecom action
- Not countedThe trigger, failed actions
The trigger in the other app never costs a task, and Zapier checking for new data is free however often it looks. Each Lecom action that goes through counts as one task; a failed one is not counted. A Zap that opens a process and then updates its data spends two tasks per run. The free plan gives 100 tasks a month, unlimited Zaps and a 15-minute polling interval, but only two-step Zaps. A second action or a filter makes it a multi-step Zap, which needs a paid plan.
Connect your Lecom account in three steps
- 01
Open the connection dialog
Go to the Apps page of your Zapier account and click + Add connection. You need a Lecom account, plus access to any process you want the Zap to touch that you do not own.
- 02
Find Lecom
Search for Lecom by name in the dialog, select it, then click Add connection. Zapier then opens a new browser tab on the Lecom side to finish the job.
- 03
Sign in and grant access
Log in to Lecom in that tab and allow Zapier to use the account. The connection then appears on your Apps page, ready for every Lecom step you add to a Zap.
Your first Zap: a form answer opens a Lecom process
GoalEach complete form answer launches a new process instance in Lecom, and incomplete ones are stopped before they reach it.
- 01
Set the trigger
Create a Zap and pick your form tool with its new submission event. Lecom has no trigger, so the Zap always starts in another app.
- 02
Test on a real answer
Run the trigger test. Zapier brings back the three most recent submissions of the connected account, so the mapping uses genuine data.
- 03
Add a filter
From the plus icon, add a Filter and set its three boxes: the field to check, the rule, and the value. This makes the Zap multi-step, so it needs a paid plan.
- 04
Add Open Process
Choose Lecom as the action app, then Open Process. Two fields are required here: the Process to launch, picked from the list or given by ID, and the Language.
- 05
Test, then publish
Test the action and check that a new instance shows up in Lecom. Once it does, click Publish to switch the Zap on for real.
The 3 Lecom actions
Lecom gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Approve or Reject Activity
ActionIn Zapier“Sends a request to include or change values from a form field or to include, update or remove a line of values from the GRID inside the activity in a process instance.”
Sets the status of an activity inside a running process instance, so a decision taken elsewhere is written into Lecom.
Open Process
ActionIn Zapier“Sends a request for approval, rejection or completion of the activity within a given instantiated process.”
Starts a new instance of one of your Lecom processes, so the workflow begins without someone launching it by hand.
Update Activity Data
ActionIn Zapier“Adds or modifies the values of the form fields.”
Writes values into the form fields of an activity, adding new ones or changing what is already there, inside an existing process instance.
When the Lecom Zap breaks
Zapier attaches no help article and no documented limit to Lecom. The failures you will meet come from how Zapier works in general, and they hit this integration in four ways.
None of these is specific to Lecom. For a step-by-step method when a run fails, see the Zapier troubleshooting guide.
Older requests never arrive
A Zap only reacts to what happens after you publish it. Form answers received before that never open a process in Lecom; moving that backlog is a separate job.Two instances for one request
With no Lecom search, the Zap cannot check whether a process is already open for this request. A trigger that fires twice opens two instances.A bulk import held back
If the trigger app suddenly returns a huge batch, after an import or a migration, Zapier's flood protection can hold those runs back.A loop that drains tasks
A Zap that writes into the very place its own trigger watches sets itself off again and again, and burns through the monthly task count.
Need help automating Lecom with Zapier?
A person reads every message.
