Lunni Zapier integrationAutomate Lunni with Zapier.
The Lunni Zapier integration has 0 triggers, 2 actions and 0 searches. It lets another app hand Lunni the emails your contacts send and the Outlook events you create, in the same tool where you already track your devices.
Verified Trustpilot reviews · AI, automation & growth agency
What the Lunni Zapier integration does for you
The Lunni Zapier integration is a way in, not a way out. Lunni keeps track of your devices, their components and the rest of your property in one place. On Zapier it offers two actions, Save Email and Save Microsoft Outlook Event, so another app always starts the automation and Lunni receives what it sends.
Three results come out of those two actions. The first is an archive of contact emails: each message a contact sends lands in Lunni through Save Email, so the conversation is kept in the tool where you track that equipment, not in your inbox. The second is a record of what you scheduled: Save Microsoft Outlook Event copies each new Outlook Calendar event into Lunni, which spares you typing the same appointment twice. The third combines both, in two separate Zaps, so Lunni holds the messages and the meetings side by side.
Now the part the official listing does not spell out. Lunni has no trigger on Zapier, so nothing that changes inside Lunni can start an automation: a device you add or edit stays invisible to Zapier. There is no search step either, so a Zap cannot look up an item already stored in Lunni. And neither action edits or deletes anything; they only add. The event action is also tied to Microsoft Outlook by its very name.
If you need Lunni to talk back to other tools, read n8n vs Zapier and Make vs Zapier before you commit to one tool for this flow.
Zapier vocabulary, one line each
Seven words come back on this page. Here is each one, once, 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 that starts the Zap. Lunni offers none, so for this app the first step always belongs to another tool.
- Action
- What the Zap does once it has started. With Lunni, that means saving an email or an Outlook event into your account.
- Task
- The unit Zapier bills: one action that completes successfully. Your plan counts those, not the Zaps you build.
- Polling vs instant
- A polling trigger is checked by Zapier on a timer. An instant trigger is reported by its app as soon as the event happens.
- Filter
- A step that lets the Zap go on only when what arrived meets your condition, and stops it there otherwise.
- Connection
- Your Lunni account linked to Zapier once, then reused by every step that saves something into Lunni.
What a Lunni Zap really costs
Lunni is not a premium app, so both actions work on the free plan. What you pay for is simple: every email or event Lunni saves successfully counts as one Zapier task.
- Premium appNo, usable on the free plan
- Free plan100 tasks a month, two-step Zaps
- BilledOne task per successful save
- Not billedThe trigger, the checks, a failed save
The trigger in the other app never costs a task, and neither do the checks Zapier runs to find new items. A save that fails is not counted. The free plan gives 100 tasks a month and two-step Zaps only: one trigger, one action. Put a filter in front of Lunni, or a second action after it, and you have a multi-step Zap that needs a paid plan. The interval grid below concerns the starting app when its trigger is a polling one; Lunni has no trigger of its own, and an instant trigger is never held to this grid.
Connect Lunni to Zapier in three steps
- 01
Open your Apps page
In your Zapier account, open Apps and click + Add connection. A dialog with a search box appears. Before this, make sure you already have a Lunni account you can sign in to.
- 02
Find Lunni and add it
Type Lunni in the search box, select it, then click Add connection. A new tab opens on the Lunni side. Sign in with the account that should receive the emails and events.
- 03
Allow access
Grant Zapier access to that account. The connection then appears in your Apps list and both Lunni actions reuse it, so you only go through this once. If the Zap must touch items you do not own, you need write access to them.
Your first Lunni Zap
GoalEvery email a contact sends you is saved into Lunni, with no copy and paste.
- 01
Start the Zap
Create a new Zap and choose your email tool as the trigger app, with its new-email event. Lunni cannot start a Zap, so the opening step always comes from another app.
- 02
Test the trigger
Run the test. Zapier brings back the three most recent emails from the connected inbox, so you build the next step on a real message instead of an empty sample.
- 03
Add Save Email
Add an action, pick Lunni, then Save Email. Map what the email step brought back into the boxes the action shows, then test it and open Lunni to check where the message landed.
- 04
Optional: a heads-up
A third step that posts a message in your chat tool makes this a multi-step Zap, so a paid plan. On the free plan, stop after Save Email; the Zap works without it.
- 05
Publish
Once every step has been tested, click Publish to switch the Zap on. From then on, only emails that arrive after publishing are saved into Lunni.
The two Lunni actions
Lunni gives you 2 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Save Email
ActionIn Zapier“Save received emails from contacts into Lunni.”
Stores an email received from one of your contacts inside Lunni, so the message is kept in the tool where you manage your equipment. The email itself comes from an earlier step in another app.
Save Microsoft Outlook Event
ActionIn Zapier“Saves a newly created Outlook Calendar event into Lunni”
Copies a newly created Outlook Calendar event into Lunni. You schedule the appointment once in Outlook, and Lunni gets its own record of it without retyping.
When a Lunni Zap breaks
Zapier attaches no help article to Lunni and the app page lists no limit of its own. The problems you will meet are the general ones of Zapier, seen from an app that only receives.
Since the Zap always starts somewhere else, most surprises come from the trigger side. Four cases are worth knowing before you switch anything on. If a Zap still misbehaves, see our Zapier troubleshooting page.
Past emails stay where they are
A Zap reacts only to what happens after it is published. Messages and events that existed before will not be saved into Lunni unless you move them some other way.A sudden flood can be held back
If the starting app suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back instead of saving each one.The same item is not saved twice
On a polling trigger, Zapier remembers what it has already seen. An email or event it has handled once will not start the Zap a second time.Nothing comes back out of Lunni
There is no trigger and no search step for Lunni. A Zap cannot notice a change in Lunni or read a saved item, so any return trip has to happen by hand.
Need help automating Lunni with Zapier?
A person reads every message.
