Integrations
Your systems stay. The work moves through them.
Finance systems where the money moves, the sources our Unified Context Engine learns your business from, and the operations tools where approved work lands. Here is what we know well, and how anything else gets scoped.
QuickBooksAccounting
SageAccounting
SAPERP
ToastPOS
DoorDashDelivery
PlaidBank data
Logos identify systems our workflows are configured around. They are not customers, partners, or endorsements.
01Finance
Where the money moves.
Grouped by the role each system plays in a finance workflow, so you can check your books, your sales, and your cash in one pass.
Finance catalog
Accounting & ERP
06Where entries post and the books close.
- NetSuite
- QuickBooks Online
- QuickBooks Desktop
- Oracle Cloud
- Sage
- SAP
POS & delivery
10Where sales, tips, fees, and payouts originate.
- Toast
- QuBeyond
- NCR
- Zenoti
- Meevo
- ABC Fitness
- Mindbody
- DoorDash
- Uber Eats
- Grubhub
Banks & cards
05Where cash actually lands and leaves.
- Chase
- American Express
- Wells Fargo
- Vantage
- Plaid
02Our Unified Context Engine
Where business context comes from.
Our UCE draws on the email, files, and conversations you authorize, so each workflow has the context, the evidence behind a decision, and the permissions that govern it.
Examples for workflow scoping
Example sources to scope for your workflow. Access and connection method are confirmed before deployment.
Email & attachments
02Bring relevant requests, correspondence, and attachments into our UCE.
- Gmail
- Microsoft Outlook
Files & knowledge
05Ground work in your contracts, policies, documents, and business records.
- Google Drive
- Microsoft SharePoint
- Microsoft OneDrive
- Notion
- Confluence
Messages & meetings
03Use authorized conversations and meeting records as business context.
- Slack
- Microsoft Teams
- Fireflies
03Operations
Where approved work lands.
Operations workflows carry out agreed CRM, scheduling, ticket, and dispatch updates, with your team’s permissions and approval points.
Examples for workflow scoping
Example systems to scope for your workflow. Available actions, access, and connection method are confirmed before deployment.
CRM & customer intake
03Scope intake, account updates, and follow-up around your customer records.
- Salesforce
- HubSpot
- Microsoft Dynamics 365
Calendars & scheduling
03Coordinate availability, appointments, and scheduling approvals.
- Google Calendar
- Microsoft Outlook Calendar
- Calendly
Work & service requests
04Route work, track handoffs, and prepare authorized task or ticket updates.
- Asana
- monday.com
- Jira
- Zendesk
Field service & logistics
03Scope dispatch, routing, and service-job updates around your operations.
- ServiceTitan
- Samsara
- Onfleet
Confirmed during scoping. Not assumed.
Finance catalog
Named finance systems
The accounting, POS, delivery, and bank systems in the finance directory. Finance workflows are shaped around them, and the connection for your account is confirmed in scope.
Custom connections
Scoped for your workflow
The UCE and operations examples, plus anything else your work runs on. We agree a connection path for each one before anything runs.
Custom connection paths
- Source files and exports
- APIs
- Webhooks
- Uploads
- 01
Connections
Which systems the workflow reads from and writes to, and how each one is reached.
- 02
Access
The minimum permissions the work needs, granted by the people who own those systems.
- 03
Workflow steps
What happens in each system, in what order, and where a person reviews before anything changes.
Questions
What people ask before a walkthrough.
Our system isn't listed. Is that a dead end?
No. Other finance and operations systems are discussed during scoping, where we agree a connection path such as source files, an API, a webhook, or an upload.
Are the UCE and operations names ready-made connectors?
No. They are examples of systems we scope workflows around. Whether and how each one connects for your account is confirmed during scoping, before deployment.
Does a finance listing mean it works out of the box for us?
A finance listing means the system is part of our finance catalog. Your account, edition, permissions, and setup still matter, so the connection is confirmed for your stack before deployment.
What does our UCE do with our email, files, and messages?
It uses only the sources and permissions agreed in scope as context and evidence for the workflow. Your team decides what it can read.
Are these logos customers or partners?
No. They identify systems our workflows are configured around. They are not customers, partners, or endorsements.
Tell us what your stack looks like.
We'll walk through your finance systems, your sources of context, and the operations tools where work lands, and confirm how each piece connects.