1. Webhooks

Event-driven external communication

Key Characteristics

• Trigger: Can be triggered by workflows, approvals, and real-time event-based(record creation, updates, deletions).
  
• Execution: External to the CRM platform. Send HTTP POST/GET requests to an external URL.
  
• Response time: Near-instantaneous.
  
• Reliability: Dependent on external endpoint's availability.
  

When should you use Webhooks?

• Send simple, real-time notifications to external systems.
  
• These are lightweight notifications where you just want to inform external systems that something happened in your CRM, but do not expect a response.
  
• Trigger immediate actions in the external app.
  
• When data changes happen in your CRM, you can use webhooks to inform the external system of the same and trigger specific actions in the external system.
  
• Live notification and alerts.
  
• Webhooks can send live notifications and alerts when an important event occurs in CRM. You can use multiple channels like SMS, emails, push notifications, etc., to notify of the event.
  

Examples

• Notifying an external system when a lead is converted.
  
• Triggering payment processing when invoice status changes.
  
• Sending SMS immediately when a high-priority lead is created.
  

2. Functions

Server-side custom logic

Key Characteristics

• Trigger: Can be triggered by various events or called directly through APIs, workflows, or button actions.
  
• Execution: Internal to the CRM platform as they run on Zoho CRM servers.
  
• Response time: Fast.
  
• Reliability: High, with in-built error handling mechanisms.
  
• Support full Deluge scripting.
  
• Can call external APIs and handle responses.
  

When should you use Functions?

• Complex business logic that requires access to CRM data
  
• Involves complex decision-making processes to compare and analyze data from multiple modules of your CRM or other service. Functions work great here as they can access data via APIs easily.
  
• Data validation and transformation
  
• You can check for data correctness to align with your business rules and convert them to the right format to use them as necessary at various places. Functions are ideal as they can validate against existing CRM data and apply complex transformation logic in real-time.
  
• Custom workflow actions
  
• You can orchestrate functions to perform multi-step processes across modules that standard workflow actions cannot perform.
  

Examples

• Validating data against business rules before saving.
  
• Implement approval workflows with multiple stakeholders.
  
• Triggering complex multi-module workflows like converting a lead to a contact and account, triggering workflow rules for the new account, adding a follow-up task to the converted lead, and adding it to marketing campaigns.
  

3. Schedules

Time-Based Automation

Key Characteristics

• Trigger: Time-based schedules like a cron job.
  
• Execution: Internal to the CRM platform.
  
• Response time: Depends on the schedule frequency.
  
• Reliability: High, with automatic retry mechanisms.
  
• Support full Deluge scripting.
  
• Supports OAuth-based API calls and data fetching from internal or external systems.
  

When should you use Schedules?

• Batch data processing
  
• Instead of processing records one at a time as they are created or updated, you can batch them all in groups to be processed later, say after business hours. This is not only efficient but also does not impact system performance during peak hours.
  
• Synchronize data
  
• You can run a schedule to compare data between your CRM and external system and regularly update them to have up-to-date information on both systems.
  
• Periodic reporting and analytics of your data
  
• Create reports, update dashboards, and analytics like weekly sales performance, at set intervals to ensure your teams and stakeholders have the right data.
  
• Maintenance and housekeeping
  
• These are the usual behind-the-scenes tasks like archiving old data, deleting temporary files, etc., once a week to keep your CRM system running smoothly.
  

Examples

• Daily data backup and archival
  
• Weekly sales performance reports
  
• Monthly lead scoring recalculation
  
• Quarterly data cleanup and deduplication
  
• Sync product data in CRM with an external ERP system every eight hours.
  

Best Practices

• Keep it simple. When you need a quick, no-frills integration, go with webhooks first.
  
• Put your smarts in one place. Use functions whenever you need custom business rules or to tie together different parts of your CRM.
  
• Schedule wisely. If you have regular batch jobs or routine tasks, set them to run on a schedule, ideally during off-peak hours so your team's daily operations are not slowed down by behind-the-scenes processes.
  
• Watch and learn. Build in error logging and notifications for both functions and scheduled jobs, so you can catch and fix problems before they snowball.
  
• Stay efficient. Remember that functions and scheduled scripts count against your API and execution limits. So, write lean code and keep an eye on your usage.
  

Previous Kaizen post - Token generation in Python SDK

See Also

• Help documentation:
  
• Functions in Zoho CRM
  
• Schedules
  
• Webhooks
• Kaizen directory