Integrations

Connecting Zapier

Every trigger, every action, and exactly what fires each one.

Connecting

Go to Master Account Settings → Integrations. Not Equipt Settings or Landscapt Settings — the connection is account-wide and works whether or not your plan includes Equipt.
Click Generate Key. Copy the key shown — it's displayed once, in full, and never again.
In Zapier, when connecting the Equipt/Landscapt app, paste that key into the API Key field.
Clicking Regenerate at any time invalidates the old key immediately — any Zaps still using it will need to be reconnected with the new one.

Whose data does a Zap see? The key is tied to your organization, not an individual user. Anything a Zap does happens as your org, scoped only to your org's own records. While the organization's subscription is canceled the key stops working, so Zaps can't create or change records in a read-only account; it works again after you resubscribe. On Create Work Order, Priority must be low, medium, high or critical, Type must be reactive or preventive and Due Date must be YYYY-MM-DD (letter case doesn't matter, and a field the Zap leaves unmapped is simply ignored); anything else is rejected with a message saying which field is wrong.

How triggers work

Two delivery methods. You don't choose — Zapier handles it automatically.

Instant	The moment the event happens inside Equipt or Landscapt, we push it straight to Zapier's webhook URL. Most triggers work this way.
Polling	Zapier calls our API every few minutes to check for new matching records. This also powers the "Test" step when setting up any Zap, and is the only method for a few triggers with no natural "moment it happened" to hook into.

Landscapt (CRM) triggers

All instant — these piggyback on the same internal event dispatch that runs Landscapt's own automations feature, so a Zap fires at the same moment an internal automation would.

Trigger	Fires when…
New Client	A client record is created.
New Lead	A client is created with status “lead” (before they’ve converted).
Lead Converted to Client	A lead’s status changes to “active.”
Client Cancelled	A client’s status changes to “cancelled.”
New Estimate	An estimate is created.
Estimate Won	An estimate’s stage changes to “won.”
Estimate Lost	An estimate’s stage changes to “lost.”
New Job	A job (recurring, one-time, snow, project, etc.) is created.
New Ticket	A support/service ticket is created.
Ticket Closed	A ticket’s status changes to “closed.”
New Invoice	An invoice is created.
Invoice Paid	An invoice’s status changes to “paid.”
Contract Signed	A contract’s signed-date is set.
New Damage Case	A damage case is logged.
Visit Dispatched	A scheduled job visit is dispatched to a crew.

Equipt triggers

Equipt has no single internal "event happened" dispatcher the way Landscapt does — most Equipt mutations write straight to the database from the browser. So most of this list is polling-only, and two get instant delivery because they already round-trip through a server route for an unrelated reason: Equipt's own internal automations feature.

Trigger	Fires when…	Delivery
New Asset	An asset (vehicle, equipment) is added.	Polling
New Work Order	A work order is created.	Polling
Work Order Completed	A work order’s status changes to “done.”	Instant
New Requisition	A purchase requisition is created.	Polling
New Purchase Order	A PO is created.	Polling
PO Approved	A PO’s status changes to “approved.”	Instant
PM Schedule Due	A preventive-maintenance schedule’s next-due date has passed, and it’s still active.	Polling
Part Low Stock	A part’s quantity on hand drops to or below its minimum stock level.	Polling
New Vendor	A vendor is added.	Polling
Meter Threshold	A tracked meter crosses a value you choose — see below.	Polling

Polling just means the Zap checks in every few minutes instead of firing the instant the event happens — for low stock, PM due, or a new vendor, that gap rarely matters. If instant delivery for more of these matters for your workflow, ask — most just need a small addition on our end.

Meter Threshold, in detail

Equipt tracks "meters" per asset — engine hours on a mower, odometer miles on a truck, whatever a piece of equipment accrues over time. This trigger lets a Zap fire when one of those values crosses a number you pick. You set three things when you build the Zap:

Which meter — pick a specific meter, or leave it blank to check every meter in your org.
Threshold — the number to compare against.
Direction — "at least" (the default) or "at most."

Example. "Truck #4's odometer reaches 50,000 miles" → meter = Truck #4 — Odometer, threshold = 50000, direction = at least. Every poll, Zapier checks the meter's current value against that line; the moment it crosses, the Zap fires.

This is separate from any meter-threshold automations already configured inside Equipt itself — those run their own actions (create a work order, send a notification) and aren't affected by anything set up in Zapier. Leaving the threshold off entirely just lists current meter values — that's what powers Zapier's "test this trigger" step before you've picked a number.

Actions

What a Zap can create in Equipt or Landscapt. Every field an ID points at — client, vendor, work order, asset — is checked against your org before anything is written.

Action	Creates	Required	Optional
Create Client	A new client (Landscapt)	Display Name	First/Last Name, Email, Phone, Account Type, Source, Service Address/City/State/Zip
Create Job	A scheduled job (Landscapt)	Client	Job Type, Scheduled Date, Notes
Create Ticket	A support ticket, attached to a client	Client, Subject	Body, Priority, Category, Type, Due Date
Add Note to Client	An entry on a client’s activity timeline	Client, Note text	Subject
Create Work Order	An Equipt work order	Title	Asset, Description, Priority, Type, Due Date
Create Requisition	An Equipt purchase requisition (starts as a draft)	Title	Vendor, linked Work Order, Notes

Zap-created records behave like ones made in the app: a client created by Create Client is a new lead that enrolls in your “Lead created” automations, and a job from Create Job enrolls in “Job was created” automations. Actions ignore clients, vendors, work orders and products that have been deleted. Each company can keep up to 100 active Zapier webhook subscriptions.

Not yet supported

Custom fields — actions only accept the fields listed above. Need something else set when a Zap creates a record — a custom field, a specific GL code? Ask and it can be added.
Update actions — Zaps can only create new records today, not update existing ones (e.g. "update ticket status from a Zap").
More instant triggers — a few of the Equipt polling triggers could become instant with a small change, if the delay matters for a particular workflow.