Actions62
- Account Actions
- Contact Actions
- Deal Actions
- Invoice Actions
- Lead Actions
- Product Actions
- Purchase Order Actions
- Quote Actions
- Sales Order Actions
- Tags Actions
- Vendor Actions
Overview
The Zoho CRM Custom node for n8n allows you to interact with the Zoho CRM API. Specifically, when configured with the Resource: Contact and Operation: Get, this node retrieves detailed information about a single contact in your Zoho CRM account using its unique Contact ID.
Common scenarios:
- Fetching up-to-date details of a specific contact for use in subsequent workflow steps.
- Enriching data from other systems by pulling full contact records from Zoho CRM.
- Verifying or displaying contact information before performing updates or related actions.
Practical example:
Suppose you have a workflow that receives a Contact ID from another system (e.g., a form submission or webhook). You can use this node to fetch all available details about that contact from Zoho CRM and then use those details in emails, reports, or further automation.
Properties
Name | Type | Meaning |
---|---|---|
Contact ID | String | ID of the contact to retrieve. This is required and uniquely identifies the contact record in Zoho CRM. |
Output
- The output will be a JSON object containing all available fields for the specified contact as returned by the Zoho CRM API.
- The structure of the output depends on your Zoho CRM configuration and custom fields, but typically includes standard contact properties such as name, email, phone, address, etc.
Example output:
{
"id": "1234567890",
"First_Name": "John",
"Last_Name": "Doe",
"Email": "[email protected]",
"Phone": "+123456789",
// ...other standard and custom fields...
}
- No binary data is produced by this operation.
Dependencies
- External Service: Requires access to the Zoho CRM API.
- Authentication: Needs valid Zoho OAuth2 credentials configured in n8n under the credential type
zohoOAuth2Api
. - n8n Configuration: Ensure the Zoho CRM integration is set up with appropriate permissions to read contacts.
Troubleshooting
Common issues:
- Invalid Contact ID: If the provided Contact ID does not exist or is incorrect, the node will throw an error indicating the resource was not found.
- Authentication errors: If the Zoho OAuth2 credentials are missing, expired, or lack sufficient permissions, authentication errors will occur.
- API limits: Hitting Zoho CRM API rate limits may result in temporary failures.
Error messages and resolutions:
"Resource not found"
: Double-check the Contact ID for typos or ensure the contact exists in Zoho CRM."Invalid Credentials"
or"Unauthorized"
: Re-authenticate or update your Zoho OAuth2 credentials in n8n."API limit exceeded"
: Wait and retry after some time, or review your Zoho CRM plan's API quota.
Links and References
- Zoho CRM API Documentation – Contacts
- n8n Documentation – Zoho CRM Integration
- How to create and manage credentials in n8n