Retrieving a custom action in Zoho CRM lets you inspect, reuse, or troubleshoot the automated actions — such as field updates, email notifications, webhooks, and functions — that drive your sales and marketing workflows. Here at Beam Help (independent expert support for Zoho, not official Zoho support), we walk you through exactly how to locate and review those actions.
Why this matters
Custom actions in Zoho CRM are the building blocks of automation: they fire when workflow rules, blueprints, or approval processes are triggered. If an action is misbehaving, duplicated, or needs to be reused in a new rule, you first need to know how to retrieve and inspect it. Understanding where these actions live also helps when you want to associate an existing function or webhook with a new workflow rather than recreating it from scratch. [8]
Step-by-step
Step 1. Log in to your Zoho CRM account and navigate to Setup (the gear icon in the top-right corner). This is the central hub for all customisation and automation configuration. [8]
Step 2. Inside Setup, go to Automation and then select Actions. This section lists every action that has been configured in your CRM — including workflow tasks, field updates, email notifications, webhooks, and associated functions. [8]
Step 3. On the Actions page you will see the full catalogue of saved actions grouped by type. Browse or use the search bar to locate the specific custom action you need. The list displays the action name, type, and the module it belongs to, making it straightforward to identify the right entry. [8]
Step 4. Click the name of the action you want to retrieve. This opens the detail view where you can inspect every setting — for example, the fields being updated, the function script attached, or the webhook endpoint configured. [8]
Step 5. If the custom action involves a function (a Deluge script), the detail view will show the code block and any connection references used to invoke external services. Connections are identified by a Link name, and the code block itself shows the HTTP method (GET, POST, PUT, or DELETE) and any dynamic parameters the function passes at runtime. [7]
Step 6. To reuse the action in another workflow rule, return to the workflow rule editor, scroll to the Actions section, and choose Associate. The dropdown will surface all previously created actions of the relevant type, so you can attach the retrieved action without rebuilding it. [8]
Step 7. If the action you are looking for is tied to a connector (an integration with a third-party service), navigate to Setup → Developer Space → Connections. Here you can view the Link name, Service name, and current Status of every connection, along with the ready-to-use code snippet for invoking it inside a function. [7]
Common pitfalls
- Action not appearing in the list. Actions are module-specific in some contexts. If you cannot find an action, confirm you are looking in the correct module scope — an action built for Leads will not automatically appear when editing a Contacts workflow. [8]
- Connection status is inactive. When retrieving a function-based action, always verify the associated connection shows an Active status under Setup → Connections. An inactive connection will cause the function to fail silently at runtime. [7]
- Dynamic parameters returning blank values. If the retrieved action uses parameters to pull record-specific data (such as a lead's name or email), double-check that the parameter mappings still reference valid field API names. Field API names can change if a field is deleted and recreated. [7]
- Invoking a standalone function from another function. If your custom action calls a standalone function via a URL (using
invokeurl), confirm the endpoint path and authentication type are still correct — for example, OAuth-based calls require a valid, non-expired connection. [2]
What to check
- Action is still linked to at least one active rule. Open the action detail view and confirm it is associated with a live workflow rule or blueprint; orphaned actions can be easy to overlook during audits. [8]
- Connection credentials are valid. If the action integrates a third-party service, verify the connection under Setup → Connections shows the correct Link name and an Active status before relying on the action in production. [7]
- Function parameters map to current field names. After retrieving a function-based action, cross-reference any dynamic parameter references against the current field list in the relevant module to avoid runtime errors. [7]