Connect Ormi to the tools you already use

Stripe

Payment processing

Available now

Accept cards, collect deposits on estimates, and receive payouts to your bank. Stripe is fully embedded into Ormi — no separate dashboard needed.

• Online & on-site card payments
• Deposits collected on estimates
• Instant payouts to your bank
• Saved customer payment methods

Appointment reminders, job updates and follow-ups by text, already built in with nothing to connect. 1,000 messages per technician a month, with no per-message charge.

• Automated appointment reminders
• Job status updates via text
• Two-way customer conversations
• SMS templates for common messages

Technicians get turn-by-turn directions from the mobile app. Dispatchers see live job locations on an interactive map view.

• In-app navigation for techs
• Dispatcher live map view
• Customer address validation
• Multi-stop route planning

Invoices, payments, bills and customers post to QuickBooks Online on their own, mapped to your accounts, items and tax codes. Payments recorded in QuickBooks come back and mark the Ormi invoice paid.

• Invoices, payments, estimates & credit memos
• Bills, vendors & purchase orders
• Stripe payouts posted as bank deposits
• Payments recorded in QuickBooks flow back

Invoices, payments, bills and contacts post to Xero on their own, coded to your accounts, tax rates and tracking categories. Payments recorded in Xero come back and mark the Ormi invoice paid.

• Invoices, payments & credit notes
• Bills, suppliers & purchase orders
• Tracking categories & tax rates
• Payments recorded in Xero flow back

Export a week of approved hours in Gusto's Smart Import format, then upload it to your Gusto payroll in about a minute. Regular, overtime and double time for every technician, without retyping a single hour.

• Gusto Smart Import format, ready to upload
• Regular, overtime and double time per workweek
• Matched to your team by name and email
• Approved weeks only, at the approved hours

Built for small contractors and solo operators. Push invoices, track expenses, and keep finances organized without an accountant.

• Invoice sync & tracking
• Expense categorization
• Client portal access
• Time tracking

Planned for shops that already own Square terminals. Card processing in Ormi runs through Stripe today, on-site swipes included, and nothing in Ormi reads or writes a Square account yet.

• Planned: take payments on Square hardware you already own
• Planned: Square transactions posted back against the Ormi invoice
• Planned: your Square dashboard left exactly as it is
• Today: Stripe covers swipes, payment links, ACH and recurring billing

Estimates and invoices leave from your own verified domain, and the reply comes back onto the customer and the job rather than into somebody's personal inbox. No Google or Microsoft account to connect: it works the same wherever your crew reads mail.

• Send from your own domain, with the DNS records shown to you
• Verification state in the mail provider's own words, so a failure names the record
• Customer replies threaded onto the customer by message headers
• Email beside SMS in one communication log, not a second inbox

Every technician gets a private calendar URL their own phone can subscribe to, and their Ormi schedule appears in it. Google Calendar, Apple Calendar and Outlook all read the same feed, and the owner decides what detail it carries.

• A per-technician subscribe URL: their jobs, nobody else's
• Google, Apple and Outlook from the same URL, no app to install
• The company chooses whether address, customer phone and job value travel
• Revoking a feed stops the old URL serving immediately

Slack

Team notifications & alerts

Coming soon

Planned as a fifth notification channel beside email, SMS, push and in-app, so the routing you already set in Ormi decides what reaches a channel. There is no Ormi app in the Slack directory yet.

• Planned: Slack as a channel in the notification settings you already use
• Planned: per-event routing, so dispatch and big invoices go to different channels
• Planned: one install per workspace, revocable from Slack
• Today: the same events reach your crew by email, SMS, push and in-app

Microsoft

Send email from Outlook

Available now

Register one app in your own Microsoft directory and Ormi sends estimates and invoices from your Outlook mailbox — they land in its Sent folder and replies come back to you. The same registration powers OneDrive backup. Signing in to Ormi with a Microsoft account is separate and not switched on yet.

• Estimates and invoices sent through your own Outlook mailbox
• Replies come back to your mailbox, because the mail came from it
• Mail.Send only: Ormi sends as the mailbox and reads nothing
• One registration also connects OneDrive backup

A backup destination: when a job is completed or an invoice is paid, its photos and signed documents are copied one way into a dated folder in your own Drive, with Ormi staying the system of record.

• Photos and signed documents copied into your own Drive, one way
• A dated folder per job under one Ormi root folder you pick
• Last push and last error on the connection, so silence is visible
• The drive.file scope only: Ormi sees nothing it did not create

Dropbox

Automatic file backup

Available now

The same backup as Google Drive, into a dedicated Ormi app folder in your Dropbox. One way, with Ormi staying the system of record and the Dropbox app registered in your own account.

• Photos and signed documents copied into your own Dropbox, one way
• A dated folder per job inside one app folder Ormi cannot see out of
• Last push and last error on the connection, so silence is visible
• Your Dropbox app and your storage: no Ormi key, no shared quota

The third file destination, working exactly like Drive and Dropbox: photos and signed documents copied one way into a dedicated Ormi folder in your Microsoft 365 OneDrive. The Entra app is yours, so the storage and the Graph quota are too.

• Photos and signed documents copied into your own OneDrive, one way
• A dated folder per job inside an app folder Ormi cannot see out of
• Files.ReadWrite.AppFolder only: one folder, and it never deletes
• The same Entra registration also sends your email from Outlook

There is no Ormi app in the Zapier directory yet. What does exist is what it would be built on: a documented REST API with scoped keys you issue yourself, and ten webhook events Ormi posts to any endpoint you own.

• Today: scoped API keys you issue, name and revoke yourself
• Today: ten webhook events across customers, jobs, estimates and invoices
• Today: an OpenAPI spec and interactive docs
• Planned: those ten events as Zapier triggers, plus three actions