Skip to main content

Prerequisites

The connector should already be set up, with a Connector Profile and a Linked Account. See Getting Started on the Zoho Books connector page.

Automatic webhook setup

StackOne creates and manages the Zoho Books webhooks automatically when the account is connected, and removes them when the account is disconnected. Each webhook posts to a StackOne URL unique to that account, so there is nothing to configure in Zoho Books.

1

What StackOne creates

For each event enabled in StackOne, one webhook and one workflow rule are added to the organization set on the connection.

  • The rules appear in Zoho Books under Settings > Automation > Workflow Rules, named StackOne followed by the event (for example, StackOne invoice.add)
  • Do not edit or delete these rules or their webhooks, or events stop being delivered until the account is reconnected

Available webhook events

The following Zoho Books events can be enabled. Only events selected in StackOne get a workflow rule, so Zoho Books will not deliver events that are not subscribed.

1

Sales document events

Events related to invoices, quotes, sales orders, credit notes and recurring invoices.

  • Invoice Created (invoice.created) — Fired when an invoice is created
  • Invoice Updated (invoice.updated) — Fired when an invoice is edited, including status changes
  • Invoice Deleted (invoice.deleted) — Fired when an invoice is deleted
  • Estimate Created (estimate.created) — Fired when a quote (estimate) is created
  • Estimate Updated (estimate.updated) — Fired when a quote (estimate) is edited, including status changes
  • Estimate Deleted (estimate.deleted) — Fired when a quote (estimate) is deleted
  • Sales Order Created (salesorder.created) — Fired when a sales order is created
  • Sales Order Updated (salesorder.updated) — Fired when a sales order is edited, including status changes
  • Sales Order Deleted (salesorder.deleted) — Fired when a sales order is deleted
  • Credit Note Created (creditnote.created) — Fired when a credit note is created
  • Credit Note Updated (creditnote.updated) — Fired when a credit note is edited, including status changes
  • Credit Note Deleted (creditnote.deleted) — Fired when a credit note is deleted
  • Recurring Invoice Created (recurring_invoice.created) — Fired when a recurring invoice profile is created
  • Recurring Invoice Updated (recurring_invoice.updated) — Fired when a recurring invoice profile is edited, including status changes
  • Recurring Invoice Deleted (recurring_invoice.deleted) — Fired when a recurring invoice profile is deleted
2

Payment events

Events related to payments received from customers and payments made to vendors.

  • Customer Payment Created (customer_payment.created) — Fired when a customer payment is created
  • Customer Payment Updated (customer_payment.updated) — Fired when a customer payment is edited, including status changes
  • Customer Payment Deleted (customer_payment.deleted) — Fired when a customer payment is deleted
  • Vendor Payment Created (vendor_payment.created) — Fired when a vendor payment is created
  • Vendor Payment Updated (vendor_payment.updated) — Fired when a vendor payment is edited, including status changes
  • Vendor Payment Deleted (vendor_payment.deleted) — Fired when a vendor payment is deleted
3

Purchase document events

Events related to bills, purchase orders, vendor credits and expenses.

  • Bill Created (bill.created) — Fired when a bill is created
  • Bill Updated (bill.updated) — Fired when a bill is edited, including status changes
  • Bill Deleted (bill.deleted) — Fired when a bill is deleted
  • Purchase Order Created (purchaseorder.created) — Fired when a purchase order is created
  • Purchase Order Updated (purchaseorder.updated) — Fired when a purchase order is edited, including status changes
  • Purchase Order Deleted (purchaseorder.deleted) — Fired when a purchase order is deleted
  • Vendor Credit Created (vendor_credit.created) — Fired when a vendor credit is created
  • Vendor Credit Updated (vendor_credit.updated) — Fired when a vendor credit is edited, including status changes
  • Vendor Credit Deleted (vendor_credit.deleted) — Fired when a vendor credit is deleted
  • Expense Created (expense.created) — Fired when an expense is created
  • Expense Updated (expense.updated) — Fired when an expense is edited, including status changes
  • Expense Deleted (expense.deleted) — Fired when an expense is deleted
4

Contact events

Events related to customers and vendors. Zoho Books treats them as separate modules, so each has its own events.

  • Customer Created (customer.created) — Fired when a customer is created
  • Customer Updated (customer.updated) — Fired when a customer is edited, including status changes
  • Customer Deleted (customer.deleted) — Fired when a customer is deleted
  • Vendor Created (vendor.created) — Fired when a vendor is created
  • Vendor Updated (vendor.updated) — Fired when a vendor is edited, including status changes
  • Vendor Deleted (vendor.deleted) — Fired when a vendor is deleted
5

Project and item events

Events related to projects and items.

  • Project Created (project.created) — Fired when a project is created
  • Project Updated (project.updated) — Fired when a project is edited, including status changes
  • Project Deleted (project.deleted) — Fired when a project is deleted
  • Item Created (item.created) — Fired when an item is created
  • Item Updated (item.updated) — Fired when an item is edited, including status changes
  • Item Deleted (item.deleted) — Fired when an item is deleted

Delivery format

Details of how Zoho Books delivers events to StackOne.

1

One record per request

Each request carries one full record as JSON, nested under the Zoho Books module key (for example invoice, contact for customers and vendors, or payment for customer payments). Deleted events carry the record as it was just before deletion.

2

Side effects also fire update events

Changes Zoho Books makes on its own also count as edits. For example, recording a payment against an invoice fires Invoice Updated as well as Customer Payment Created.

Verify

Your Connector should now be able to receive and process events. Try triggering an event and you should see an Event appear in the Connector logs.