How does ml-connector handle Zoho Books regions and OAuth2 authentication?

Zoho Books uses region-specific base URLs (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia). ml-connector accepts the OAuth2 refresh token and determines the region from the token response api_domain field, then routes all API calls to the correct regional base URL. Access tokens expire after 1 hour, so ml-connector refreshes them proactively at 55 minutes to avoid mid-request failures. The organization_id is fetched once and cached for reuse on every API call.

Can I customize which events trigger Twilio notifications?

Yes. ml-connector can be configured to listen for specific Zoho Books webhook events - invoice created, invoice sent, invoice overdue, bill created, purchase order created, vendor payment sent, or expense recorded. Each event type can route to different Twilio channels (SMS to one phone number, email to another recipient) based on your rules.

What happens if a Twilio send fails or times out?

Every Zoho Books event, routing decision, and Twilio send result is logged in the audit trail. If a Twilio request fails or times out, ml-connector surfaces the failure and the original event can be replayed manually or re-queued to Twilio for retry without losing the Zoho Books transaction record.

Zoho BooksTwilio

Zoho Books and Twilio integration

Zoho Books tracks invoices, bills, purchase orders, and cash flow. Twilio sends notifications via SMS and email. Connecting the two lets you alert customers when invoices are sent or due, notify vendors when payments are posted, and alert your finance team when bills arrive or expenses are recorded. ml-connector handles the different authentication schemes and routes accounting events to the right notification channels on demand.

How Zoho Books works

Zoho Books is a cloud accounting platform for small and medium businesses handling invoicing, bills, purchase orders, expenses, and multi-currency accounting. The API is REST-based with region-specific base URLs (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia) and requires OAuth2 authentication with a user-delegated refresh token, plus an organization_id query parameter on every API call. Zoho Books exposes webhooks that push real-time events for invoices, bills, purchase orders, contacts, payments, and expenses, and also supports offset-based polling for historical data. Access tokens expire after 1 hour and must be refreshed proactively. Webhook signatures use HMAC verification against a configurable alphanumeric secret.

How Twilio works

Twilio is a cloud communications platform providing APIs for SMS, MMS, email, voice calls, video, and identity verification. The core API uses HTTP Basic Auth with either an Account SID plus Auth Token or an API Key SID plus API Secret. Twilio exposes multiple REST endpoints for messages, phone numbers, messaging services, verify, lookups, conversations, studio flows, and task routing. It supports webhooks for incoming message callbacks, message status (delivered, failed, read), incoming calls, call status (answered, completed, failed), and verification status changes. Webhook signatures are validated using HMAC-SHA1 with the Auth Token as the key. Twilio does not include finance objects such as invoices, purchase orders, GL accounts, or payments.

What moves between them

Events flow from Zoho Books into Twilio. When an invoice is created, sent, or due in Zoho Books, ml-connector captures the webhook notification and sends an SMS or email via Twilio to the assigned customer contact. Similarly, vendor payment events trigger SMS alerts to payment approvers, and bill creation alerts go to finance team members by email. There is no data flow back into Zoho Books - Twilio is notification-only in this pattern.

How ml-connector handles it

ml-connector listens for Zoho Books webhook events by accepting POST requests signed with the webhook secret. It validates each webhook signature using HMAC and determines which Twilio notification channel (SMS to a phone number or email to an address) should be triggered based on the event type and configured routing rules. Since Zoho Books requires both OAuth2 credentials and an organization_id parameter, ml-connector caches the organization_id after first retrieval and refreshes the OAuth2 access token before expiry at 55 minutes. For Twilio, ml-connector presents HTTP Basic Auth credentials (either Account SID and Auth Token or API Key) and uses the appropriate Twilio endpoint for the notification type. Regional Zoho Books customers require their regional base URL, determined from the OAuth2 token response, so ml-connector routes all Zoho calls to the correct region. Rate limits on Zoho Books (100 requests per minute, daily plans limits) and Twilio usage limits are tracked, and ml-connector backs off on 429 responses. Every notification carries an audit trail showing the original Zoho Books event, the routing decision, and the Twilio send result, allowing for replay if a Twilio call fails.

A real-world example

A mid-sized SaaS company invoices customers via Zoho Books and needs to keep customers informed when invoices are sent, payments are received, and when invoices are approaching due. Before the integration, the billing team manually sent email updates or relied on Zoho Books' built-in email reminders, which lacked customization. With Zoho Books and Twilio connected, invoice creation triggers an SMS to the customer contact with a payment link, and an email to the billing contact with the full invoice details. Payment receipts trigger a thank-you SMS, and overdue invoices trigger escalation alerts to the company's collections team. The billing workflow becomes automated and customers stay informed without manual intervention.

What you can do

Send SMS notifications via Twilio when invoices are created, sent, or approaching due date in Zoho Books.
Email alerts to vendors, customers, and finance staff for purchase orders, bills, and vendor payments from Zoho Books.
Dynamically route invoice and bill events to the correct Twilio messaging service based on event type and customer contact.
Validate webhook signatures from Zoho Books and Twilio to ensure message authenticity.
Track all events and notification sends with full audit trail and error replay on Twilio send failures.

Questions

How does ml-connector handle Zoho Books regions and OAuth2 authentication?: Zoho Books uses region-specific base URLs (US, EU, India, Australia, Japan, Canada, China, Saudi Arabia). ml-connector accepts the OAuth2 refresh token and determines the region from the token response api_domain field, then routes all API calls to the correct regional base URL. Access tokens expire after 1 hour, so ml-connector refreshes them proactively at 55 minutes to avoid mid-request failures. The organization_id is fetched once and cached for reuse on every API call.
Can I customize which events trigger Twilio notifications?: Yes. ml-connector can be configured to listen for specific Zoho Books webhook events - invoice created, invoice sent, invoice overdue, bill created, purchase order created, vendor payment sent, or expense recorded. Each event type can route to different Twilio channels (SMS to one phone number, email to another recipient) based on your rules.
What happens if a Twilio send fails or times out?: Every Zoho Books event, routing decision, and Twilio send result is logged in the audit trail. If a Twilio request fails or times out, ml-connector surfaces the failure and the original event can be replayed manually or re-queued to Twilio for retry without losing the Zoho Books transaction record.

Connect Zoho Books and Twilio

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

Get started