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 CRM connector page.

Subscribe via the StackOne dashboard

This connector uses Programmatic Webhooks. StackOne creates and manages the webhook subscription automatically when the account is connected: enabling webhook events creates a single Zoho CRM notification channel (via POST /actions/watch) covering every event you enable, pointing at your StackOne callback URL.

1

Select event subscriptions in the dashboard

In the StackOne dashboard, open the Zoho CRM connector profile and enable the webhook events you want delivered downstream. See the Available Webhook Events section below for the full list.

2

Registration on subscribe

When webhook events are enabled (or the selection changes), StackOne enables a notification channel on your behalf using the connected account’s credentials, registered for exactly the events you enabled. You can inspect it with the connector’s List Notifications action.

3

Verify delivery

Create, update, or delete a record in a watched module (for example, create a test lead) and confirm the event reaches your downstream consumer.

4

Unsubscribe

Changing your event selection re-registers the channel. Disconnecting the account disables it (DELETE /actions/watch), stopping deliveries.

Available Webhook Events

The following Zoho CRM events can be enabled. Each event corresponds to a Zoho notification event in the form Module.operation.

1

Sales events

Events on leads, contacts, accounts, deals, and campaigns.

  • Lead Created (Leads.create) — Fired when a lead record is created
  • Lead Updated (Leads.edit) — Fired when a lead record is updated
  • Lead Deleted (Leads.delete) — Fired when a lead record is deleted
  • Contact Created (Contacts.create) — Fired when a contact record is created
  • Contact Updated (Contacts.edit) — Fired when a contact record is updated
  • Contact Deleted (Contacts.delete) — Fired when a contact record is deleted
  • Account Created (Accounts.create) — Fired when an account record is created
  • Account Updated (Accounts.edit) — Fired when an account record is updated
  • Account Deleted (Accounts.delete) — Fired when an account record is deleted
  • Deal Created (Deals.create) — Fired when a deal record is created
  • Deal Updated (Deals.edit) — Fired when a deal record is updated
  • Deal Deleted (Deals.delete) — Fired when a deal record is deleted
  • Campaign Created (Campaigns.create) — Fired when a campaign record is created
  • Campaign Updated (Campaigns.edit) — Fired when a campaign record is updated
  • Campaign Deleted (Campaigns.delete) — Fired when a campaign record is deleted
2

Activities events

Events on tasks, meetings, and calls.

  • Task Created (Tasks.create) — Fired when a task record is created
  • Task Updated (Tasks.edit) — Fired when a task record is updated
  • Task Deleted (Tasks.delete) — Fired when a task record is deleted
  • Meeting Created (Events.create) — Fired when a meeting record is created
  • Meeting Updated (Events.edit) — Fired when a meeting record is updated
  • Meeting Deleted (Events.delete) — Fired when a meeting record is deleted
  • Call Created (Calls.create) — Fired when a call record is created
  • Call Updated (Calls.edit) — Fired when a call record is updated
  • Call Deleted (Calls.delete) — Fired when a call record is deleted
3

Inventory events

Events on products, vendors, price books, quotes, sales orders, purchase orders, and invoices.

  • Product Created (Products.create) — Fired when a product record is created
  • Product Updated (Products.edit) — Fired when a product record is updated
  • Product Deleted (Products.delete) — Fired when a product record is deleted
  • Vendor Created (Vendors.create) — Fired when a vendor record is created
  • Vendor Updated (Vendors.edit) — Fired when a vendor record is updated
  • Vendor Deleted (Vendors.delete) — Fired when a vendor record is deleted
  • Price Book Created (Price_Books.create) — Fired when a price book record is created
  • Price Book Updated (Price_Books.edit) — Fired when a price book record is updated
  • Price Book Deleted (Price_Books.delete) — Fired when a price book record is deleted
  • Quote Created (Quotes.create) — Fired when a quote record is created
  • Quote Updated (Quotes.edit) — Fired when a quote record is updated
  • Quote Deleted (Quotes.delete) — Fired when a quote record is deleted
  • Sales Order Created (Sales_Orders.create) — Fired when a sales order record is created
  • Sales Order Updated (Sales_Orders.edit) — Fired when a sales order record is updated
  • Sales Order Deleted (Sales_Orders.delete) — Fired when a sales order record is deleted
  • Purchase Order Created (Purchase_Orders.create) — Fired when a purchase order record is created
  • Purchase Order Updated (Purchase_Orders.edit) — Fired when a purchase order record is updated
  • Purchase Order Deleted (Purchase_Orders.delete) — Fired when a purchase order record is deleted
  • Invoice Created (Invoices.create) — Fired when an invoice record is created
  • Invoice Updated (Invoices.edit) — Fired when an invoice record is updated
  • Invoice Deleted (Invoices.delete) — Fired when an invoice record is deleted
4

Support events

Events on cases and solutions.

  • Case Created (Cases.create) — Fired when a case record is created
  • Case Updated (Cases.edit) — Fired when a case record is updated
  • Case Deleted (Cases.delete) — Fired when a case record is deleted
  • Solution Created (Solutions.create) — Fired when a solution record is created
  • Solution Updated (Solutions.edit) — Fired when a solution record is updated
  • Solution Deleted (Solutions.delete) — Fired when a solution record is deleted

Delivery format

Details of how Zoho CRM delivers events to StackOne.

1

JSON payloads

Zoho CRM posts a JSON body containing the module API name (module), the operation (insert, update, or delete), the affected record IDs (ids), server_time in epoch milliseconds, resource_uri, and channel_id. Update deliveries also carry affected_fields with the changed field values.

2

Batched record IDs

A single delivery can list several record IDs in ids. The first ID is used as the event ID and the full envelope, including every ID, is passed through in the event data. The payload does not include full record data — fetch the record by ID when needed.

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.