Choose the connection type:
Give your connection a clear name (e.g., "Zoho CRM - Demo").
Select your Zoho CRM organization and click Submit, then review the permissions and click Accept.
object_id variable (Type: Text), and select Automated process.The app provides three actions to use inside your workflow:
Contact Owner, Lead Owner, Vendor Owner, Account Owner) is done via exact text name mapping (e.g., passing the string "Manager One").(e.g., Account, Reporting To, Parent Account)
Account Name = "Widget Corp") OR the system ID (e.g., Account ID = "8967800...").ID field instead.Account and a Reporting To manager, the manager specified in Reporting To must be associated with the exact same Account in Zoho CRM. Attempting to assign a manager who belongs to a different company (or no company) will result in an API error.Twitter field will reject any string containing a space or special sumbols; currency and number fields will reject any alphabetic characters).AxiosError) instead of the specific validation message. If a workflow fails during a Writeback step, always double-check the formatting and data types of the values being passed to specialized fields.Each Zoho CRM module has required fields that must be mapped in the Writeback step. These fields are marked with a red asterisk (✱) in the UI. Without them, the step will not save and the workflow will not run correctly.
The mandatory fields per module are:
Last NameLast Name, CompanyAccount NameDeal Name, Account Name, Stage, Closing Date Vendor Name⚠️ These fields are also used by the connector to identify whether to update an existing record or create a new one. Make sure the value passed to the mandatory field is accurate and consistent with your Zoho CRM data.
The table below lists the available lookup fields for each module. Refer to section 2 for the general rules on how to map them correctly.
Account - link to an Account record via Account Name or Account IDReporting To - link to another Contact (manager) via name or ID. Must belong to the same Account.Company field is a standard text string, not a relational lookup. You do not need an Account ID to fill it.Parent Account - link to a parent Account record via Account Name or Account IDAccount - link to an Account record via Account NameContact - link to a Contact record via Contact Name or Contact IDCampaign Source - link to a Campaign record via Campaign Source Name or Campaign Source ID⚠️ For each of the above relationships, map either the Name or the ID — never both. Mapping both fields for the same entity may cause workflow failures or unpredictable payload overrides.
Vendor Name - link to a Vendor record via Vendor Name💡 Rule of thumb: Always check this box if your workflow is intended to explicitly change existing values — including names, numbers, or linked lookups (e.g., changing the
Account Namelinked to a Deal).
This section explains how to install and configure the Zoho CRM integration for use with Docusign Workflow Builder.
Before starting, ensure that:
[App Center search results showing the Zoho CRM app by Fluidlabs]
[Zoho CRM app page with the Install App button in the top right corner]Once the app is installed, you need to authorize the connection between Docusign and Zoho CRM.
Initiate Connection: After installation, the app page will show an Installed status. Click the Connect Account button to begin linking your Zoho CRM account.
[App page showing "Installed" badge and the Connect Account button]Select Account Type: You will be prompted to choose the connection visibility:
[Select Account Type screen showing Private and Shared options]Name the Connection: Enter a clear name for your connection (e.g., "Zoho CRM - Demo"). This name will appear in Workflow steps, so make it easily identifiable.
[Name Connection screen with "Zoho CRM - Demo" entered in the field]Authorize with Zoho CRM: You will be redirected to the Zoho authorization screen. The process has two steps:
Step 4a — Select Organization:
A dialog will appear asking you to choose which Zoho CRM organization to connect. Select your organization from the list and click Submit.
[Zoho org selection dialog showing CRM service and organization list with Submit button]Step 4b — Review and Accept Permissions:
Zoho will display the list of permissions being requested (CRUD operations on modules, user data access, metadata). Check the "I allow Docusign Production to access the above data from my Zoho account" checkbox, then click Accept.
[Zoho permissions review screen with checkbox checked and Accept button]Completion: You will be redirected back to the Docusign App Center. The app status will show as Installed and the connection is ready to use in workflows.
You can edit, delete, or add new connections at any time without reinstalling the app.
To access connection settings:
[Manage dropdown showing: Add New Connection, Manage Connections, Manage Apps, Uninstall App]You will be taken to the Connections page, which lists all active connections with their type, status, and the user who created them.
To manage an individual connection, click the three dots (⋮) menu next to it:
[Connections list showing Zoho CRM-Demo as Shared/Active, with three-dot menu open showing Edit connection name, Reconnect, Reload Objects, Delete Connection]To connect an additional Zoho CRM organization, you can either:

Follow the same setup steps as the initial installation.
The Zoho CRM app enables you to work with Zoho CRM data directly within Docusign Workflows. Using this app, you can create workflows that read data from Zoho CRM, update Zoho CRM records, and automatically attach signed documents as part of an automated process.
[Docusign Workflows screen with Create Workflow button]Within the Workflow Builder, the Zoho CRM app provides actions to interact with your data. These actions allow Zoho CRM to act as both a source and a destination within the same workflow.
The following actions are available:

["Add New Step" dialog with "Zoho" searched, showing all three Zoho CRM actions]
In this documentation, we use object_id as the workflow startup variable. This is a common pattern when triggering workflows from an external system via API.
To configure the workflow trigger:
Select From an API Call as the workflow start method.

Create a variable named object_id (Type: Text).

Choose Automated process as the trigger type.

This configuration allows external systems to trigger the workflow and pass a specific identifier (such as a Zoho CRM record ID) into the object_id variable. This variable can then be used in subsequent steps (like Read from Zoho CRM) to identify which record to process.
The Read from Zoho CRM step allows a workflow to retrieve data from any Zoho CRM module. To do this correctly, the workflow must be able to identify which specific record it should work with.
Configuring this step involves three main stages:
In your workflow builder, click + Add Step.
Search for and select Read from Zoho CRM.
Once the block appears, click Configure to start the setup.

You will be prompted to select where to read data from.
Connection: Choose the Zoho CRM connection you created earlier (e.g., "Zoho CRM - Demo (Shared)").
Zoho CRM object: Select the module you want to work with. The integration currently supports the following modules:

💡 Note: The configuration logic described below is identical for all five supported modules - select your fields, define the matching rule, and the retrieved data becomes available as workflow variables. The examples in this guide use the Contacts module.
In this example, select Contacts.

Click Next.
Choose the specific data points you want to retrieve from the Zoho CRM record.
Click Add or Remove Fields.

A field browser will open showing all available fields for the selected module. Select the fields you need (e.g., Name, Contact ID, First Name, Last Name, Full Name, Email, Phone, Account Name, etc.).

The selected fields will become available as workflow variables for use in later steps.
Click Next.
💡 Note: For information on working with special field types, data formatting rules, and other nuances specific to Zoho CRM, refer to the Implementation Guide & Known Behaviors.
In this step, you define which specific Zoho CRM record the workflow should read. You do this by creating a matching rule.
Create a rule that matches a Zoho CRM field to a workflow variable:
Zoho CRM field: Select a unique identifier field (e.g., Contact ID (string)).
Operator: Select Equal to.
Workflow field: Select the variable that contains the identifier (e.g., object_id, configured at the workflow start).

Example Logic: This rule tells the system: "Find the Zoho CRM Contact whose Contact ID matches the object_id provided when the workflow started."
Click Done. The rule is now saved.
Once configured, this step will find the correct record in Zoho CRM and pull the selected field data into the workflow as variables. You can now use these variables in subsequent steps (e.g., to pre-fill a document or pass data to a Writeback step).
The Writeback to Zoho CRM step allows a workflow to update existing records or create new ones in Zoho CRM using data collected during the workflow (e.g., from a signed document or a web form).
This step is typically used at the end of a workflow to save results back to Zoho CRM. A common pattern:
In your workflow builder, click + Add Step.
Search for and select Writeback to Zoho CRM.
Once the block appears, click Configure to start the setup.

Connection: Select your Zoho CRM connection (e.g., "Zoho CRM - Demo (Shared)").
Zoho CRM object: Select the module you want to write to. The same five modules are supported: Accounts, Contacts, Vendors, Deals, and Leads.

Write settings: Choose how the system should handle the data:

Click Next.
In this step, you map workflow data to the corresponding Zoho CRM fields. This tells the system where to write each piece of data.
Click Add or Remove Fields to select which Zoho CRM fields you want to populate.

For each field, select the source variable from your workflow. Data can come from any previous step - for example, from a Send Documents for Signature step (i.e., data filled in by the signer on the signed form).

⚠️ Mandatory fields: Each Zoho CRM module has required fields marked with a red asterisk (e.g., Last Name for Contacts). These fields must be mapped for the step to work. They are also used by the connector to identify whether to update an existing record or create a new one. For the full list of mandatory fields per module, refer to the [Implementation Guide & Known Behaviors]([INSERT LINK]).
Click Next.
Define which specific record in Zoho CRM the workflow should write to by creating a matching rule.
Zoho CRM field: Select a field that can uniquely identify the record (e.g., Email (string)).
Operator: Select Equal to.
Workflow field: Select the corresponding workflow variable (e.g., Email from the signed form).

⚠️ Important: The identifier field must be unique in your Zoho CRM data. If the system finds multiple records matching the rule (e.g., two contacts with the same email), the step will fail. Use the most reliable unique field available, or refer to the Implementation Guide & Known Behaviors for guidance.
Click Done. The step is now configured and will automatically update or create Zoho CRM records when the workflow runs.
The File Upload Zoho CRM step allows a Workflow to upload and attach a file directly to a record in Zoho CRM.
In your workflow builder, click + Add Step.
Search for and select File Upload Zoho CRM.
Once the block appears, click Configure to start the setup.

Select which file from the workflow should be uploaded.
Select a file or envelope: Choose Combined Envelope File (or another file variable generated by a previous step).

💡 If no file is available in the dropdown, it means the file has not been generated yet at this point in the workflow. Make sure a Send Documents for Signature (or something is generating this file) step exists before the File Upload step.
Select connection: Choose your Zoho CRM connection (e.g., "Zoho CRM - Demo (Shared)").

Select drive: Choose the Zoho CRM module you want to attach the file to. Each option includes a helpful hint about how the folder structure will work:

Select folder: After selecting the drive, click Add Folder + to define where within the module the file will be attached.

You have two options:
After clicking Add Folder +, a dropdown will show existing records from your Zoho CRM (displayed as Name#RecordID). Select the specific record you want to attach the file to.

This method uses the record ID retrieved from an earlier Read from Zoho CRM step to dynamically attach the file to the correct record for each workflow run.
In the Select folder dropdown, choose New Subfolder.

In the New folder dialog, click Add Variable.
![New folder dialog showing variable selection for folder names like 'Contacts[] / Contact ID'.](/images/documentation/zoho-for-docusign/cb9418db94b2a435f6ba742b3e7f6f1e.webp)
Select the variable source Read from Zoho CRM and choose Contact ID (or the relevant ID field for your module).
The folder name field will populate with the ID variable (e.g., Contacts[1] / Contact ID). Click Add.

The Select folder field will now show [Contacts[1] / Contact ID].

Result: The file will be attached to the specific record involved in the current workflow run.
Use case: The recommended approach for universal workflows where signed documents need to reach the correct client record automatically.
Click Next.
Use variables and text to create a custom file name.
Click Add Variable to insert a workflow variable, or Add Text to type a static name.
Enter your desired file name (e.g., Signed-MSA).
The File path preview at the bottom will show the full path where the file will be stored.

Click Apply.
Once the workflow runs, the file will be attached to the specified record in Zoho CRM. To verify, open the record in Zoho CRM and navigate to the Attachments section — the uploaded file will appear there, listed with the source as Docusign.

Here are the most common configuration issues and how to resolve them.
Q: I don't see any files available in the "Select a file or envelope" dropdown.
A: This happens when the workflow hasn't generated a file yet at the point where the File Upload step is placed.
Q: The file upload is failing or the file is going to the wrong record.
A: This is usually caused by an incorrect folder configuration in the upload location.
[Contacts[1] / Contact ID]), not a static text name. See the File Upload Zoho CRM guide for the full configuration steps.Q: The Writeback step created a duplicate record instead of updating the existing one.
A: This happens when the matching rule in Step 3 doesn't find the correct record.
Q: The Writeback step is failing and won't save.
A: Check whether all mandatory fields are mapped.
Q: The Writeback step fails with a generic error like AxiosError.
A: This is typically a data formatting issue on a specialized field.
Twitter field rejects values containing spaces, and currency or number fields reject any alphabetic characters. When Zoho returns a 400 Bad Request, the connector may display a generic error instead of the specific validation message.Q: The workflow is failing with a token or authentication error.
A: The connection to Zoho CRM may have expired or lost its authorization.
Solution:
Q: A Writeback step fails when trying to link a related record (e.g., Account or Reporting To).
A: This is caused by mapping both the Name and the ID for the same lookup field simultaneously.