LionO360 Zapier integrationAutomate LionO360 with Zapier.
The LionO360 Zapier integration gives you 3 triggers, 3 actions and 0 searches. Accounts, leads and tickets, each one in both directions: a new record in LionO360 can set off work elsewhere, and your other tools can create one in LionO360 without retyping it.
Verified Trustpilot reviews · AI, automation & growth agency
What the LionO360 Zapier integration does
LionO360 is a cloud platform that brings together CRM, field service and ERP, to give one view of customers, sales and field work. Zapier connects it to your other apps around three objects: accounts, leads and tickets. Each has a trigger when one is created, and an action to create one.
Three results come up most often.
A team that hears about tickets first. New Ticket spots each new ticket and the Zap posts it to your team chat, so support does not depend on someone refreshing LionO360.
Leads that enter on their own. When a form or a sheet collects a new prospect elsewhere, Create Lead adds it to LionO360 with just a lead name, and the sales cycle starts in the right place.
An onboarding step that never gets skipped. New Account fires when an account is created, and Create Ticket opens a follow-up ticket for it, so nothing waits on memory.
What Zapier does not do here: it cannot update, find or delete a record. There is no search step at all, so a Zap cannot look up an existing account or lead before acting. Every action creates something new, which means a Zap sent the same data twice creates it twice. And a Zap ignores everything that existed before you switched it on.
If you are still choosing a tool, the n8n vs Zapier comparison is the next read.
Zapier words, explained once
Zapier comes with its own vocabulary. Here it is in plain English, so the rest of the page needs no decoding.
- Zap
- The automation you build on Zapier: one trigger, then one or more actions that run each time that trigger event happens.
- Trigger
- The event in an app that starts the Zap, such as a new LionO360 ticket. Once the Zap is on, Zapier waits for it.
- Action
- What the Zap does once it has started: the step that writes, sends or moves something for you, like creating a lead.
- Task
- The unit Zapier bills: one action your Zap completes successfully. The count on your plan is a count of those.
- Polling vs instant
- Zapier checks a polling trigger on a timer; an instant trigger is reported by the app the moment it happens. All three LionO360 triggers poll.
- Filter
- A step that lets the Zap go on only when what arrived meets the condition you set, and stops it otherwise.
- Multi-step Zap
- Any Zap beyond one trigger and one action. A second action or a filter makes one, and it then needs a paid plan.
- Connection
- Your LionO360 account linked to Zapier once, then reused by every step and every Zap that touches LionO360.
What a LionO360 Zap really costs
LionO360 is not a premium app: it runs on the free plan. Triggers cost nothing, only the actions that go through are billed.
- Premium appNo, works on the free plan
- Tasks on the free plan100 per month
- Steps per Zap on the free planTwo: one trigger, one action
- Cost of a trigger checkZero tasks
Zapier checking LionO360 for new accounts, leads or tickets costs zero tasks, however often it looks. Each action that succeeds costs one task, and one that fails costs nothing. A Zap that creates a ticket and then posts a message uses two tasks per run. The free plan builds two-step Zaps only, one trigger and one action; a filter or a second action makes it multi-step, which needs a paid plan. The grid below is how long a new record can wait before Zapier sees it.
Connect LionO360 to Zapier
- 01
Add the connection
Go to Apps in your Zapier account, click + Add connection, search for LionO360 in the dialog and pick it. You need a LionO360 account, with access to the accounts, leads and tickets the Zap will touch.
- 02
Sign in to LionO360
Click Add connection. A tab opens on LionO360: sign in with the account whose records you want to watch or create. Every Zap reuses this connection, so choose that account with care.
- 03
Grant access
Accept Zapier's access request in that tab. It closes and LionO360 is now listed on your Apps page, ready to be used as a trigger or an action in any Zap.
Your first Zap: new tickets posted to your team
GoalEach new LionO360 ticket that matches your condition is posted as a message in your team chat.
- 01
Set the trigger
Create a Zap, pick LionO360 and the New Ticket event, then your LionO360 connection. Run the test: Zapier brings back the three most recent tickets so you work on a real one.
- 02
Add a filter
Click the plus icon and add Filter. Set the field to check, the rule and the value. Use a text rule for text and a number rule for numbers, or nothing ever passes.
- 03
Add the message
Add your team chat as the action and choose the step that sends a message. Place the ticket's subject and description in the message so people can act on it straight from there.
- 04
Test the action
Test the step and read what came back. Check the message actually landed in the right place, with the ticket details filled in, before going further.
- 05
Publish
Publish the Zap to switch it on. With the filter it is a multi-step Zap and needs a paid plan; without it, the Zap fits the free plan.
LionO360 triggers
3 events start a Zap when something happens in LionO360. Zapier checks for them at the interval your plan allows.
New Account
Polling triggerIn Zapier“Triggers when a new account is created.”
Starts your Zap each time an account is created in LionO360 and hands its details to the next steps. It is the natural starting point for anything that should follow a new customer record.
New Lead
Polling triggerIn Zapier“Triggers when a new lead is created.”
Fires when a lead appears in LionO360, whoever or whatever created it, and passes it along to the rest of the Zap. Use it to make sure no prospect sits unseen in the CRM.
New Ticket
Polling triggerIn Zapier“Triggers when a new ticket is created.”
Kicks off your Zap whenever a ticket is opened in LionO360 and carries it to the steps you added after it. It turns LionO360 tickets into alerts or records in the tools your team already watches.
LionO360 actions
LionO360 gives you 3 actions. For each one: what it does for you, when to reach for it, and what to watch out for.
Create Account
ActionIn Zapier“Creates an Account in the system”
Opens a new account in LionO360, with its name and the first name of its contact, both required.
Create Lead
ActionIn Zapier“Create a Lead in the system”
Adds a new lead to LionO360 from data collected in another app. The only field it insists on is the lead name.
Create Ticket
ActionIn Zapier“Create ticket in the system”
Raises a ticket in LionO360 from something that happened elsewhere, with a subject and a description, both mandatory.
When a LionO360 Zap breaks
Zapier attaches no help article of its own to LionO360. What goes wrong comes from how Zapier treats every app, and from the fact that every LionO360 action creates something.
Most of these are not bugs: the Zap does what Zapier promises, not what you pictured. If a run really fails, the Zapier troubleshooting page is where to go next.
The Zap feeds itself
A Zap that creates tickets while New Ticket watches the same account, or accounts while New Account does, sets itself off again and again and burns tasks fast.Old records never arrive
A Zap only reacts to what happens after it is switched on. Accounts, leads or tickets that already existed are never picked up; moving them is a separate job.A bulk import stalls
When a trigger suddenly returns a huge batch, after a bulk import or a migration, Zapier's flood protection can hold those runs back.A record runs only once
Zapier remembers what it has already seen on a polling trigger, so the same ticket or lead never starts the Zap twice. That is by design.
Need help automating LionO360 with Zapier?
A person reads every message.
