Does ml-connector push all Zoho Books tables into Snowflake or do I choose which ones?

You choose. ml-connector can load invoices, bills, purchase orders, vendor payments, customer payments, contacts, chart of accounts, journals, items, or expenses. Define which tables you need and the column schema for Snowflake, and ml-connector routes only those records.

How does ml-connector handle Zoho Books multi-region setups?

Zoho Books returns the region (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia) in the OAuth2 token response. ml-connector stores the region per customer and routes all API calls to the correct regional base URL. If your organization moves to a different region, update the credential to reflect the new region.

Can ml-connector pick up Zoho Books changes in real time or does it need to poll?

Both. ml-connector can subscribe to Zoho Books webhook events for near-real-time push, or poll on a schedule you set if webhooks are not enabled. Polling is recommended for accounting close cycles where a daily or weekly refresh is sufficient.

Zoho BooksSnowflake

Zoho Books and Snowflake integration

Zoho Books powers accounting and finance for SMBs. Snowflake powers analytics and data warehouse queries on those records. Connecting the two moves your full general ledger, invoices, bills, vendor payments, and chart of accounts into Snowflake on a schedule you define. Finance teams get a unified view of transactions and can run reports, reconcile accounts, and audit payment flows directly from Snowflake without re-keying or exporting from Zoho Books.

How Zoho Books works

Zoho Books exposes invoices, bills, purchase orders, vendor payments, customer payments, contacts, chart of accounts, journal entries, items, and expenses through a REST API. The platform uses OAuth2 Authorization Code flow with user-delegated refresh tokens and requires an organization ID as a query parameter on every call. Access tokens expire after 1 hour and must be refreshed proactively. Zoho Books operates on region-specific base URLs (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia), and the region is returned in the token response. The platform supports outgoing webhooks configured via the API for real-time event push to a registered endpoint, including events for invoices, bills, purchase orders, contacts, and payments. It also supports polling via list endpoints with offset-based pagination.

How Snowflake works

Snowflake is a cloud-based data warehouse that stores and queries financial data. It does not have built-in finance objects; connectors define and populate user tables for vendors, invoices, purchase orders, payments, chart of accounts, and other entities. Snowflake uses Key Pair Authentication (JWT from an RSA private key) or Programmatic Access Tokens for server-to-server access. It is pull-only; there are no inbound webhooks. Change detection uses timestamp watermarking or Snowflake Streams (native CDC with destructive consumption). The SQL API supports async queries that return a statement handle and require polling. Unquoted identifiers are uppercased automatically, and network policies require service account egress IPs to be whitelisted.

What moves between them

All records flow from Zoho Books into Snowflake. Invoices, bills, purchase orders, vendor payments, customer payments, contacts, chart of accounts, journal entries, and expenses are loaded into corresponding Snowflake tables on a schedule tied to your accounting close cycle or daily refresh window. ml-connector polls Zoho Books or subscribes to webhook events, transforms each record into the Snowflake column schema you define, and inserts or upserts into the target table. Currency data is resolved from Zoho Books currency tables and stored in the fact table so Snowflake can report in native currency or convert.

How ml-connector handles it

ml-connector stores the Zoho Books OAuth2 client credentials encrypted and maintains a proactive refresh of the access token before the 1-hour expiry window closes to prevent mid-flow 401 errors. It stores the organization ID and regional base URL per customer and routes all Zoho Books API calls to the correct region. Because Zoho Books requires the organization ID on every call, ml-connector resolves it once at setup and caches it per customer workspace. ml-connector accepts Zoho Books webhook events where enabled and can also poll on a cadence aligned to your accounting close timeline. It deduplicates using BullMQ jobId to ensure a failed insert or network timeout does not create duplicate records. For rate limiting, ml-connector backs off exponentially when Zoho Books returns HTTP 429. It creates the target Snowflake tables based on your schema if they do not exist, and it stores a full audit trail of every load so failed records can be replayed from the audit log into Snowflake when the downstream error is fixed.

A real-world example

A 200-person software services firm uses Zoho Books for accounting across four departments and currencies. Finance needs a single source of truth for invoicing trends, vendor payment patterns, and account reconciliation, but pulling exports from Zoho Books and loading them manually into their Snowflake data warehouse each week is error-prone. With Zoho Books and Snowflake connected, every invoice and payment flows into Snowflake automatically on a daily schedule. Finance analysts query Snowflake to see unbilled revenue by department, payment aging by vendor, and cross-currency settlement without re-keying or waiting for manual extracts.

What you can do

Load Zoho Books invoices, bills, and purchase orders into Snowflake tables on a daily or weekly schedule aligned to your accounting cycle.
Sync vendor and customer payments, chart of accounts, and journal entries into Snowflake with full transaction history and supporting detail.
Resolve and store currency data from Zoho Books so Snowflake can report in native and converted currency.
Handle Zoho Books regional base URLs, organization ID routing, OAuth2 token refresh, and rate-limit backoff transparently.
Deduplicate records using BullMQ jobId and replay failed loads from the audit trail when downstream Snowflake errors are resolved.

Questions

Does ml-connector push all Zoho Books tables into Snowflake or do I choose which ones?: You choose. ml-connector can load invoices, bills, purchase orders, vendor payments, customer payments, contacts, chart of accounts, journals, items, or expenses. Define which tables you need and the column schema for Snowflake, and ml-connector routes only those records.
How does ml-connector handle Zoho Books multi-region setups?: Zoho Books returns the region (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia) in the OAuth2 token response. ml-connector stores the region per customer and routes all API calls to the correct regional base URL. If your organization moves to a different region, update the credential to reflect the new region.
Can ml-connector pick up Zoho Books changes in real time or does it need to poll?: Both. ml-connector can subscribe to Zoho Books webhook events for near-real-time push, or poll on a schedule you set if webhooks are not enabled. Polling is recommended for accounting close cycles where a daily or weekly refresh is sufficient.

Connect Zoho Books and Snowflake

Free to use. Add your credentials, ping your real systems, and see if we fit.

Get started