Docs

Docs / Integrations / Zoho CRM integration

Zoho CRM

A Zoho CRM deal at your stage, a contact you tick or a record in your own module sends your agreement, and a note says when it is signed. Zapier or Make today.

Planned. Built, and not yet connectable. The native connection is written against Zoho CRM's documentation and tested against stand-ins: a button on the deal sends what you choose to its contacts, or a stage you name does, so does a contact, a lead or a custom module's record whose field you choose reaches a value you choose, a lost or deleted one voids what nobody signed, and a note goes on the record when they have signed. It has not run against a live Zoho CRM account, and it cannot be connected until SignSealer's Zoho app exists. Until then Zapier and Make carry both directions, and the guide has the steps.

Today, step by step

  1. In Zapier: Zoho CRM's Updated Module Entry on Deals, then SignSealer's Send a Form to Sign. In Make, Watch Objects does the same.
  2. A second Zap or scenario: SignSealer's Document Completed, then Update Module Entry (Make: Update an Object) on the deal.
  3. Use the deal's ID as your reference, so each document leads back to its deal.

The signature coming back

A second Zap or scenario: SignSealer's Document Completed (or a SignSealer webhook) → Zoho CRM's Update Module Entry in Zapier, or Update an Object in Make, on the deal whose ID you sent as the reference. A declined document carries the signer's reason.

What the native connection does, now that it is built

It is written against Zoho CRM's API v8 and tested against stand-ins, and it waits on SignSealer's Zoho app: nothing here can be switched on until that app exists.

  • Connecting. Connect sends you to Zoho to sign in and approve SignSealer for one organization. Zoho sends you back naming your data center, and SignSealer only ever talks to that one: the United States, Europe, India, Australia, Japan, Canada, Saudi Arabia or the United Kingdom. It asks to read your organization, your modules' records and their fields, to add notes and attachments, to update records (only to make the two changes below, when you ask for them), and to keep a notification channel, and for nothing else.
  • Deals. SignSealer opens a notification channel on your deals at the connection's own address. A notification is taken only with the channel's secret token and within an hour of Zoho sending it, and the deal is then read back from Zoho. A deal at a stage you name on the connection's page sends what its contact, and each contact with a role on the deal, owes (none does until you name one); one at a canceling stage (Closed Lost and Closed Lost to Competition), or deleted, voids what nobody has signed; any other stage changes nothing. Stage names are matched without regard to capitals, spaces or hyphens.
  • Sending from the deal. The connection's page gives you an address for a button. In Zoho CRM's setup, add a button to the Deals module that opens a URL, with that address: pressing it on a deal opens SignSealer, signed in as you, to choose what goes, any of your templates and forms, or what your rules say it needs, and whether to the deal's contact or everyone on it. The deal is read from Zoho when you press Send, whatever its stage. A button on Contacts or Leads works the same way, with Contacts: or Leads: before the record's id.
  • Contacts, leads and your own modules. On the connection's page, add up to ten modules besides deals, each by its API name (Zoho CRM shows them under Setup, Developer Hub, APIs and SDKs, API Names): a field on it, the values that send and those that cancel, and who signs. A Send for signature checkbox on Contacts sends when it is ticked (its value is true); a Status picklist on a custom module sends at Ready to sign. Who signs is the record itself (a contact or a lead, by its name, email and phone), or the record a lookup field on it names, such as a custom module's Client lookup to Contacts. The channel watches exactly the modules you list, and saving the page changes it at once.
  • The channel. Zoho closes a channel after a week at most, so SignSealer opens it for six days and renews it a day before it ends, from the connection's own queue. A renewal that fails is retried and shows in the connection's activity like any delivery.
  • The signature coming back. When every document is signed, or one is declined, a note goes on the deal, or on the record that sent, with each document, who signed it, when, and a link to it. When everything is signed, each signed PDF, sealed with its certificate, is added to the record's attachments too, unless you turn that off on the connection's page; one already there is not added twice.
  • Moving a signed deal on. On the connection's page, name a stage a signed deal moves to, such as Closed Won (not one that sends or cancels), and a field by its API name, such as Signing_Status, that says Signed when everything is signed or Declined when somebody declines. The field is written on whatever record sent, a contact or your own module's as well as a deal, so add it to each; only a deal is moved. Both are off until you fill them in; one Zoho refuses is said in the connection's activity, and the note still goes. Nothing else on a record is ever changed.
  • Disconnecting. Closes the channel and revokes SignSealer's access at Zoho.

Once it can be connected, connecting it comes with the membership, like every system SignSealer connects to; Zapier, Make and the API work on Free today.

With the API directly

PUT https://api.signsealer.com/v1/subjects
Authorization: Bearer mk_live_…

{ "provider": "zoho-crm", "external_id": "…", "starts_on": "2026-10-10",
  "participants": [{ "ref": "…", "full_name": "…", "email": "…", "is_primary": true }] }

POST https://api.signsealer.com/v1/packets/{packet_id}/start

Keyed on the Zoho CRM ID, so sending the same record twice is one reservation, and starting again sends nothing already sent. See Reservations and packets and Webhooks for the signature coming back.

Signing links go by email. They also go by text only when SignSealer holds that guest's consent to receive texts from your business, recorded with the exact words they agreed to — at your counter, on your booking form through POST /v1/sms-consents, or on SignSealer's own opt-in. That check runs when the link is queued (app.may_text), not in the integration.

No booking system can give SignSealer that consent, so none is treated as if it could. Each adapter records what the provider's data said — VERIFIED_CONSENT, NO_CONSENT or INSUFFICIENT_EVIDENCE — and only NO_CONSENT changes anything: the guest's number is not written at all. Every provider built so far can only ever say INSUFFICIENT_EVIDENCE. The connection's activity shows, for each guest with a number, whether the link was also texted and why not.

How to record consent you took yourself.

This page as Markdown Ask an AI about it: ChatGPT · Claude · Perplexity · Google AI · Grok

Ready to build? An API key takes a minute in the portal, and the free plan covers the first 10 agreements a month.

Get an API key