Finance & ERP · Integration
Omie
Add Omie to your product for your customers, and give your AI agents governed access to it.
Embed an Omie integration so your product can work inside the ERP Brazilian small and mid-sized companies already run. Omie is a cloud ERP that carries the finance side properly: customer and supplier invoices, accounts payable and receivable, entries against the company's own chart of accounts, purchase orders, products, services and the customer and supplier records behind them. Each company connects their own Omie account with their own app key and secret, so reads and writes are scoped to that tenant and logged. Writes are idempotent, which matters here more than anywhere else, because a duplicated financial document is something an accountant has to unpick. fastn owns the credentials, retries, rate limits and API upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let each company connect their own Omie account so invoices, receivables and orders are reachable inside your product with no per-customer code.
Create invoices or payable and receivable entries from your product against the company's own account structure, idempotently.
Read customer, supplier and product records per tenant so your product does not ask users to re-enter what Omie already holds.
Support each company's own chart of accounts, categories and document types as per-tenant configuration rather than code.
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
An agent answers what a customer owes by reading that company's own Omie receivables, with each read audited.
An agent drafts an invoice or a payable entry within scoped permissions, with the write attributed.
An agent reports which documents are overdue for one company and what changed this week.
Example prompt
Which Omie receivables for this customer are overdue, and what was the last payment recorded?
Set up Omie in 4 steps
- 01Enable the Omie connector in your fastn dashboard.
- 02Have each company supply their own app key and secret so calls run under their account.
- 03Map their chart of accounts, categories, document types and product fields as per-tenant configuration.
- 04Call it from your product and expose the same connection to your agents through the MCP gateway.
Why teams use the Omie integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an Omie integration without building it. Your customers connect their own Omie account inside your product and work their invoices, payments and vendors there, with no per-customer code on your side.
- Handle the part that actually costs time: financial writes must be idempotent and reconcilable, because a duplicate is an accounting problem rather than a bug. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an Omie update is not your on-call problem.
- One integration serves your product and your agents. The same governed Omie connection powers in-product features and gives AI agents scoped, audited access, so you move financial records without hand-keying them between systems without wiring it twice.
Used by these teams
Compare with
Odoo
QuickBooks
XeroOften used alongside
Tools the same teams tend to run next to Omie, across other categories.
Shopify
Stripe
BigCommerce
AfterShipOmie integration FAQ
How do I add an Omie integration to my product?
Enable the Omie connector in your fastn dashboard, then let each customer authenticate their own Omie account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no Omie client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own Omie account?
Yes. Every connection is scoped to the individual customer, so each authorises their own Omie account and only ever sees their own invoices, payments and vendors. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this Omie integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. An agent answers what a customer owes by reading that company's own Omie receivables, with each read audited.
Who maintains the Omie integration?
fastn does. When Omie changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Is the Omie integration safe for financial writes?
Writes are idempotent, so a retry after a timeout does not post a document twice, and every call is logged per tenant so an entry can be traced back to the event that created it. That matters more in finance than anywhere else, because a duplicate is a number somebody has to explain.
Can it handle each customer's own chart of accounts?
Yes. ERP deployments are configured to the business, so account structures, required fields and fiscal calendars differ per customer. Those are mapped per tenant as configuration, not hard-coded.
What about Omie rate limits during a first import?
Backfills are throttled deliberately. ERP limits are often account-wide rather than per-integration, so an unthrottled import can exhaust a customer's allowance and disrupt their other integrations.
What can I build with the Omie integration?
A common starting point: let each company connect their own Omie account so invoices, receivables and orders are reachable inside your product with no per-customer code. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the Omie integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding Omie does not change your per-connector cost. You can start free with 3 connected accounts.
Add Omie to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.