Lumeer Zapier integrationAutomate Lumeer with Zapier.
The Lumeer Zapier integration links the records of your Lumeer tables to your other tools. It gives you 2 triggers and 3 actions: what each one does, what it costs in tasks, how to connect your account and where a Lumeer Zap can break.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lumeer Zapier integration actually does
Lumeer organises projects in tables made of records, one record per item you track. The integration connects those tables to Zapier: a record created or changed in Lumeer starts a step in another app, and an event elsewhere can add, find or update a record in Lumeer. Nobody retypes anything.
Three results you can build. First, form answers that land in a table: each answer collected in another tool goes through Create Record in a Table and becomes a record your team can work on right away. Second, a team that hears about new items: Record Created in a Table sends a message to the channel where people actually read things, so a new entry does not sit unnoticed. Third, a copy kept in step: Record Updated in a Table passes each change on to the spreadsheet or tool that holds a copy of the same list.
What Zapier does not do for Lumeer: it cannot delete a record, and it only works at record level, inside a table you pick, never on the organisation or the project themselves. The good news is speed: both triggers are instant, so the Zap starts as soon as the record changes, even on the free plan, and the interval grid never applies.
Still comparing platforms? Read the Make vs Zapier comparison before you build.
Zapier vocabulary in one minute
Seven words come back all over this page. Each one is explained once here, in plain words.
- 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 switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that creates, finds or updates something in an app for you.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The allowance on your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant one is reported by the app the moment it happens. Lumeer has instant only.
- Filter
- A step that lets the Zap go on only when what arrived meets a condition you set, and stops it quietly otherwise.
- Connection
- Your Lumeer account linked to Zapier once, then reused by every step of every Zap that works with Lumeer.
What a Lumeer Zap really costs
Lumeer is not a premium app, so it runs on the free plan. Triggers never cost a task, and since both Lumeer triggers are instant, they fire straight away on every plan, the free one included.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Lumeer triggersBoth instant, no waiting
Only a successful action is billed. A Zap that posts a message for each new record costs one task per message; a step that fails costs nothing. Each Lumeer action that goes through, Find Record in a Table included, counts on its own. The free plan stops at two steps, one trigger and one action, and a filter or a second action makes the Zap multi-step, which needs a paid plan. The interval grid below is Zapier's general one: it does not apply to the instant triggers of Lumeer.
Connect Lumeer to Zapier in three steps
- 01
Open your connections
In Zapier, go to the Apps page of your account and click + Add connection. A connection is your Lumeer account linked to Zapier once, then reused by every step that needs it.
- 02
Pick Lumeer
Type Lumeer in the search box of the dialog, select it, then click Add connection. A new tab opens on the Lumeer side to finish the link with your login.
- 03
Sign in and grant access
Log in to Lumeer in that tab and grant Zapier access to your account. You need a Lumeer account, plus read or write access to any project or table you do not own and want the Zap to touch.
Your first Zap: hear about the changes that matter
GoalWhen a record is updated in a chosen Lumeer table and the change matches your rule, send a message to your team.
- 01
Create the Zap and set the trigger
Start a new Zap, pick Lumeer as the app that starts it and
Record Updated in a Tableas the event. Choose your connection, then the Organisation, the Project and the Table. - 02
Test the trigger
Run the test. Zapier brings back the three most recent records of that table, so you set up the next steps on a real one rather than an empty sample.
- 03
Add the filter
Click the plus icon and pick Filter. Fill the three boxes: the field to look at, the rule and the value. A text rule only works on text.
- 04
Add the message
Add your messaging tool as the action, with its send step, and place the record details that came from the trigger into the message.
- 05
Test, then publish
Test each step, then click Publish. The filter makes this a multi-step Zap on a paid plan; only the messages actually sent cost a task.
The 2 Lumeer triggers
2 events start a Zap when something happens in Lumeer, and 2 of them are instant: the app calls Zapier straight away, whatever your plan.
Record Created in a Table
Instant triggerIn Zapier“Triggers when a new Record in the given Table is created.”
Starts the Zap each time a new record appears in the table you choose. Whatever was just added in Lumeer, a new item to track or a new entry in a list, can then be announced, copied or used to start work in another tool.
Record Updated in a Table
Instant triggerIn Zapier“Triggers when a Record in the given Table gets updated.”
Fires when an existing record in the chosen table is changed. It is the trigger for following what moves in Lumeer, not just what gets added, so another tool can stay in line with the latest values.
The 3 Lumeer actions
Lumeer gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Record in a Table
ActionIn Zapier“Creates a new Record with specified Attributes and values in the given Table”
Adds a new record to the table you pick, with the values you map into its attributes.
Find Record in a Table
ActionIn Zapier“Finds an existing new Record(s) matching the specified criteria in the given Table”
Looks for records that match the criteria you set in a given table and hands what it found to the next steps.
Update Record in a Table
ActionIn Zapier“Updates an existing Record in the given Table”
Changes an existing record in the chosen table, matched through its Index Attribute.
When a Lumeer Zap breaks
Zapier links no help article to Lumeer and documents no limit specific to the app. The cases below come from the fields its operations require and from how Zapier itself behaves.
Four cases worth knowing before you publish, because none of them shows while you build. If one hits you, the Zapier troubleshooting page is a good place to start.
The Zap that feeds itself
Record Updated in a Table answered by Update Record in a Table on the same table writes where the trigger watches: each update sets the Zap off again and eats tasks.No access to the table
Triggers require an Organisation, a Project and a Table. If your Lumeer login has no access to them, the trigger cannot be set and the Zap never starts.Old records are not picked up
A Zap only reacts to what happens after you switch it on. Records that already existed stay out; moving that backlog into another tool is a separate job.A sudden flood of records
When a trigger suddenly returns a huge batch, after a bulk import into a table for example, Zapier's flood protection can hold those records back.
Need help automating Lumeer with Zapier?
A person reads every message.
