LumApps Zapier integrationAutomate LumApps with Zapier.
The LumApps Zapier integration gives you 3 triggers, 2 actions and 1 search. Enough to send intranet news, community posts and notifications to your other tools, or to post and notify inside LumApps from them. Here is what each one does, what it costs and where it breaks.
Verified Trustpilot reviews · AI, automation & growth agency
What the LumApps Zapier integration actually does
The integration links your LumApps intranet to Zapier, so that something happening on the intranet sets off a step in another app, or the other way round, without anyone copying text by hand. It can spot new content, new community posts and new notifications, post in a community, notify people, and find a community by its title.
Three results you can build with it. First, new intranet content echoed in the right community: New Published Content starts the Zap, Find a Community picks the community by title, and Create Community Post shares the news there. Second, an archive of community discussions: New Community Post sends each post to your spreadsheet tool, one row per post. Third, alerts pushed to the people concerned: when something happens in another app, Create Notification notifies chosen users inside LumApps, provided the connected account is an admin.
What Zapier does not do for LumApps: it cannot edit or delete content, posts or notifications, and it does not publish intranet content itself, only community posts. All three triggers work by polling, so nothing arrives the instant it happens; the cost section explains the interval.
If you are still picking a platform, read the n8n vs Zapier comparison before you build.
Zapier vocabulary in one minute
Seven words come back all over 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 switched on, Zapier waits for that event and nothing else.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something in an app on your behalf.
- Task
- The unit Zapier bills. One task is one action your Zap completes successfully, and your plan is a count of those.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by the app itself as soon as the event happens.
- Filter
- A step that lets the Zap continue only when the incoming data meets a condition you set, and stops it otherwise.
- Search step
- A step that looks up something already stored in an app, so the following steps can use what it found.
What a LumApps Zap really costs
LumApps is not a premium app, so it works on the free plan. Triggers never cost a task, and neither do the checks Zapier runs on LumApps to spot new items, however often it looks.
- Free plan100 tasks per month, unlimited Zaps
- Free plan Zap sizeTwo steps: one trigger, one action
- Premium appNo, works on the free plan
- Search stepMakes the Zap multi-step
Only a successful action is billed: each Create Community Post or Create Notification that goes through is one task, and one that fails costs nothing. The free plan stops at two steps, one trigger and one action. Add Find a Community, a filter or a second action, and the Zap becomes multi-step, which needs a paid plan. The grid below shows how often Zapier checks the three LumApps triggers, depending on your plan.
Connect LumApps 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 LumApps account linked once, then reused by every step that needs it.
- 02
Pick LumApps
Type LumApps in the search box of the dialog, select it from the results, then click Add connection. A new browser tab opens on the LumApps side to finish the link.
- 03
Sign in and allow access
Log in to LumApps in that tab and grant Zapier access to the account. You need a LumApps account, plus access to any community or content you do not own and want the Zap to touch.
Your first Zap: share new content in the right community
GoalEach time new content is published on the intranet, find the community by its title and post a short message there pointing to it.
- 01
Create the Zap
Start a new Zap, pick LumApps as the app that starts it and
New Published Contentas the trigger event, then choose your LumApps connection. - 02
Test the trigger
Run the test. Zapier brings back the three most recent published items of the account, so you map the next steps on real content.
- 03
Add the search
Add a step, choose LumApps and pick
Find a Communityunder the SEARCH heading. Type the community title to look for, exactly as it shows in LumApps. - 04
Add the post
Add LumApps again as the action with
Create Community Post, use the community found by the search, and write the post with the content title. - 05
Test, then publish
Test each step and check the post in LumApps. Then click Publish. With a search, this is a multi-step Zap that needs a paid plan; each post costs one task.
The 3 LumApps triggers
3 events start a Zap when something happens in LumApps. Zapier checks for them at the interval your plan allows.
New Community Post
Polling triggerIn Zapier“Triggers on a new community post.”
Starts your Zap when someone posts in a LumApps community. Discussions that would otherwise stay inside the intranet can then reach the tools where your team tracks topics, questions or decisions.
Create Community Post in the same community writes where it listens and can loop.New Notification
Polling triggerIn Zapier“Triggers on a new notification.”
Fires when a new notification shows up in LumApps. Alerts that would otherwise wait inside the intranet can then follow you into a tool you watch more closely.
New Published Content
Polling triggerIn Zapier“Triggers on a new published content.”
Kicks off a Zap whenever new content is published on your LumApps intranet. It follows published content rather than community posts, which have their own trigger.
The 2 LumApps actions
LumApps gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Community Post
ActionIn Zapier“Creates a post in a specified community.”
Publishes a post in the community you specify, with text built from earlier steps of the Zap. Something happening outside the intranet can then start a conversation where your colleagues already talk.
Find a Community just before this step.Create Notification
ActionIn Zapier“Creates a notification for specified users. Available with an admin account only.”
Sends a LumApps notification to the users you specify, so an alert lands in the intranet rather than in yet another inbox. This action is available with an admin account only.
The LumApps search
1 search step looks for data that already exists in LumApps, so a later step can use it.
A search step looks up something that already exists, here a community, and hands it to the following steps. LumApps searches sit at the bottom of the Action event list, under the SEARCH heading. Three settings decide what happens next.
Find a Community
SearchIn Zapier“Finds a community by title.”
Looks up a LumApps community by its title and passes it to the next step, so a post lands in the right place without you picking the community by hand each time.
Create Community Post, when the community name comes from an earlier step.The three settings every search exposes
- 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 goes on empty-handed.
- Create X if it doesn't exist yet?This box turns a search into a find-or-create. Find a Community offers no such variant on Zapier, so a missing community is never created.
- If multiple search results are found?Three ways out when several communities match: keep the first one, which is the default, stop the Zap, or hand all of them on at once.
When a LumApps Zap breaks
Zapier links one help article to LumApps, How to get started with LumApps on Zapier, and documents no limit specific to the app. The cases below come from how LumApps operations work and from Zapier itself.
Six cases are worth knowing before you publish, because none of them shows while you build. When one of them hits, the Zapier troubleshooting page is the place to start.
Notifications refused
Create Notification needs an admin account. Connect LumApps with a regular user and this step cannot run, so every Zap that relies on it stops at that point.The community is not found
If Find a Community finds nothing and the setting is left on its default, the Zap stops there and the post that depended on it is skipped.The Zap that feeds itself
Starting on New Community Post and answering with Create Community Post in the same community writes where the trigger listens, and the Zap sets itself off again and again.Old content is never picked up
A Zap only reacts to what happens after you switch it on. Content and posts that already existed stay out, and moving that backlog is a separate job.A sudden flood of items
When a trigger suddenly returns a huge batch, after a bulk import for example, Zapier's flood protection can hold those items back instead of running them all.Duplicates are filtered out
Zapier keeps track of what it has already seen on a polling trigger, so the same post, notification or content never starts the Zap twice.
Need help automating LumApps with Zapier?
A person reads every message.
