Ormi has a Zapier app, with nine instant triggers (new customer, new request, new job, job completed, estimate sent, estimate approved, new invoice, invoice paid, payment received), plus four actions (create customer, create job, create draft invoice, add note) and a find-or-create customer search. It is not listed on Zapier yet, so a Zap cannot use it today. What works now is what it runs on: scoped API keys you issue yourself, and twelve webhook events Ormi posts to any https endpoint you own.
Searching Zapier for Ormi finds nothing until the app is published, and this page changes the day it is. Today, in Dashboard, then Developers, you can issue a scoped API key, send any of the twelve events to an https endpoint you own, and read the delivery log. If there is a Zap you are waiting for, tell us at /contact-us.
The reasons it is on the list. None of these work yet.
Yes. It is documented with an OpenAPI specification and interactive docs, and you authenticate with a scoped key you issue in Dashboard, then Developers. A key can never carry more access than the person who created it, and each key has its own request budget, separate from your own sign-in.
customer.created, booking_request.created, job.created, job.status_changed, job.completed, estimate.sent, estimate.approved, estimate.declined, invoice.created, invoice.sent, invoice.paid and payment.received. The list is short on purpose: every one of them is actually emitted.
When Zapier lists it. The app is built and tested on our side; what remains is publishing it and Zapier's own review, which we do not control, so we will not name a date. This page changes the day it is listed.
No. Keys, webhooks, the Zapier app and the documentation are part of the product. Zapier has its own pricing, from Zapier.
$25 per field technician, per month. Dispatchers, admins and owners are free. Your first 15 days are free, with unlimited jobs too.