Function Categories
A quick reference for the seven Function categories in Zoho CRM.
Table of Contents
1. Button
2. Automation
3. Schedule
4. Related List
5. Signals
6. Validation Rule
7. Standalone
When creating a Function, you must select a category. The category determines the Function's return data type and the contexts it can be associated with within Zoho CRM.
Button
Associates the Function with a custom button on a CRM record. The Function is triggered manually when a user clicks the button.
Common uses: generating an invoice from a Deal record, fetching additional details from a third-party database, or updating record fields on demand.
Automation
Associates the Function with CRM automation features such as Workflow Rules, Blueprints, Approvals, and Circuits. The Function is triggered automatically when a predefined condition is met.
Common uses: updating a Lead's status when qualifying criteria are met, syncing related module records when a Blueprint stage changes, or reassigning a rejected record in an Approval process to the correct user.
Schedule
Runs the Function automatically at a pre-defined interval or time, independent of any user action or CRM event.
Common uses: sending daily pipeline reports to the sales team, running weekly data sync jobs with external systems, or automating periodic cleanup tasks such as removing outdated records.
Related List
Associates the Function with a related list on a CRM module, allowing custom actions to be executed directly on the linked records without navigating away from the parent record.
Common uses: updating all invoices linked to a Contact from within the Contact record's related list.
Signals
Triggers a Zoho CRM Signal, a real-time notification raised when a specific event occurs. Functions in this category are typically used to consume inbound webhook data from third-party systems, format the payload, and forward it to the Signals API.
Common uses: surfacing a real-time notification in CRM when an external system event occurs via webhook.
Validation Rule
Executes before a record is saved to validate field data against custom business logic. Functions in this category extend the built-in validation rules with conditional or complex validation that the standard rule builder cannot express.
Common uses: enforcing cross-field validation, applying business-specific data consistency rules before a record is committed.
Standalone
A general-purpose Function that is not tied to any specific CRM event or UI element. Standalone Functions are designed for programmatic invocation. They can be called from other Functions or exposed as REST API endpoints that can be invoked over HTTP.
Common uses: centralizing reusable business logic that multiple triggers need to call, exposing CRM data or operations as a REST API for external systems, receiving inbound webhook payloads from third-party services, and building integration endpoints for AI agents or partner applications.
Tip:
Use the Standalone category whenever you want to decouple your core logic from a specific trigger. This makes the Function reusable across workflow actions, button clicks, scheduled jobs, and external HTTP calls without duplicating code.
Inline Invocation: Standalone Functions can be invoked inline from other Functions. To call a Standalone Function inline, invoke the target Function by name and pass a parameter object; the caller receives the Function's return value synchronously. Example (pseudocode):
result = Standalone.MyStandaloneFunction(arg1,arg2);
Not sure which category to pick?
If the Function is meant to be called by other Functions or accessed externally via HTTP, choose Standalone. For all other use cases, choose the category that matches the trigger. For example, use Button for custom buttons, Automation for Workflow Rules and Blueprints, and Schedule for time-based jobs.