Documentation menu

Zoho CRM

A Zoho CRM deal at the right stage sends the contact your agreement, and a completed signature moves the deal on. Today through Zapier or Make, natively later.

Planned. Planned, not built. Zoho authorises apps per data centre and its notification channels expire within a week unless renewed, which the native connection will do for you. Until then Zapier and Make carry both directions.

Today, step by step

  1. In Zapier or Make: trigger on a Zoho CRM deal update, then SignSealer's Send a Form to Sign.
  2. A second automation: Document Completed, then update the deal.
  3. Use the deal ID as your reference.

The signature coming back

SignSealer's Document Completed → update the Zoho deal by the reference you sent.

What the native integration will do

A Zoho app authorised in your Zoho data centre, with Zoho's notification channels (which expire within a week) renewed automatically, and the channel token checked on every delivery.

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.

Texting and consent

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.

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

Get an API key