Zoho CRM Custom icon

Zoho CRM Custom

Consume Zoho CRM API

Actions62

Overview

The Zoho CRM Custom node for n8n allows you to interact with the Zoho CRM API. Specifically, when using the Deal resource and the Create or Update (upsert) operation, this node will either create a new deal in Zoho CRM or update an existing one if a deal with the specified name already exists.

Common scenarios:

  • Automatically syncing deals from another system into Zoho CRM, ensuring no duplicates.
  • Keeping deal information up-to-date by updating existing records based on the deal name.
  • Integrating sales pipelines where deals are created or updated as part of automated workflows.

Practical example:
If you receive new deal data from a web form or another CRM, you can use this node to ensure that the deal is either created if it doesn't exist, or updated if it does—keeping your Zoho CRM data consistent and current.

Properties

Name Type Meaning
Deal Name string Name of the deal. Used to identify the record; if a deal with this name exists, it will be updated, otherwise a new one will be created.
Stage Name or ID options The stage of the deal. You can select from a list or specify an ID via expression. Required for creating or updating a deal.
Additional Fields collection Optional fields to further define the deal, such as amount, closing date, currency, custom fields, description, probability, etc.
└ Amount number Monetary value of the deal.
└ Closing Date dateTime Expected closing date for the deal.
└ Currency options Currency symbol for the deal's revenue (e.g., USD, EUR, INR, etc.).
└ Custom Fields fixedCollection Set values for custom fields defined in your Zoho CRM instance.
└ Description string Textual description of the deal.
└ Lead Conversion Time number Average days taken to convert a lead into a deal.
└ Next Step string Description of the next step in the sales process.
└ Overall Sales Duration number Average days from lead conversion to winning the deal.
└ Probability number (0–100) Probability of closing the deal, as a percentage (e.g., 12 for 12%).
└ Sales Cycle Duration number Average days for the deal to be won.

Output

The output will be a JSON object containing the details of the created or updated deal as returned by the Zoho CRM API. The structure typically includes:

{
  "id": "string",
  "Deal_Name": "string",
  "Stage": "string",
  // ...other standard and custom fields as set or returned by Zoho CRM
}
  • All fields provided in the input (including additional and custom fields) will be present if supported by Zoho CRM.
  • The id field uniquely identifies the deal in Zoho CRM.
  • Any other fields returned by Zoho CRM for the deal will also be included.

Note: This node does not output binary data.

Dependencies

  • External Service: Requires access to a Zoho CRM account.
  • Authentication: Needs valid Zoho OAuth2 credentials configured in n8n (zohoOAuth2Api).
  • n8n Configuration: Ensure the Zoho CRM API credentials are set up in the n8n Credentials section.

Troubleshooting

Common issues:

  • Missing required fields: If "Deal Name" or "Stage Name or ID" are not provided, the node will throw an error.
  • Invalid field values: Providing invalid values for picklist fields (like Stage or Currency) may result in API errors.
  • Authentication errors: If the Zoho OAuth2 credentials are missing or expired, authentication will fail.
  • Custom field mismatches: If you reference custom fields that do not exist in your Zoho CRM setup, the API call may fail.

Error messages and resolutions:

  • "Required field missing": Ensure all mandatory properties ("Deal Name", "Stage Name or ID") are filled.
  • "Invalid value for field": Double-check the value provided for options like Stage or Currency.
  • "Authentication failed": Reconnect or refresh your Zoho OAuth2 credentials in n8n.
  • "Field does not exist": Verify custom field IDs/names against your Zoho CRM configuration.

Links and References

Discussion