

How to Send Zoho CRM VIP Case Alerts to Slack with Make
Watches Zoho CRM for new cases from high-value accounts and immediately posts a formatted alert to a Slack support channel so your team can prioritize response.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Best for
Support teams that handle enterprise or VIP accounts and need sub-minute Slack alerts when those customers open a new case in Zoho CRM.
Not ideal for
Teams with fewer than 20 VIP accounts — a simple Zoho CRM notification email or Zoho Flow handles that without a third-party tool.
Sync type
real-timeUse case type
notificationReal-World Example
A 25-person B2B SaaS company uses this to ping #support-vip in Slack the moment an enterprise customer opens a case in Zoho CRM. Before this, support leads checked Zoho every 30–45 minutes and routinely missed new cases from paying accounts for over an hour. Now the on-call rep sees the case title, account tier, and a direct CRM link within 60 seconds of submission.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Import this workflow directly into Make
Copy the pre-built Make blueprint and paste it straight into Make. All modules, filters, and field mappings are already configured — you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Case Subject | Subject | |
| Account Name | Account_Name | |
| Case Priority | Priority | |
| Account Type | Account_Type | |
| Record ID | id | |
4 optional fields▸ show
| Case Status | Status |
| Case Owner | Case_Owner |
| Case Description | Description |
| Created Time | Created_Time |
Step-by-Step Setup
make.com > Scenarios > Create a new scenario
Create a new Make scenario
Log into Make at make.com and click the blue 'Create a new scenario' button in the top right of the Scenarios dashboard. You'll land on the visual canvas with a single empty module in the center. This canvas is where you'll chain all the modules for this workflow. Give the scenario a name immediately — click the default 'New scenario' text at the top left and type something like 'Zoho CRM VIP Case → Slack Alert'.
- 1Click the blue 'Create a new scenario' button at the top right
- 2Click the pencil icon or 'New scenario' text at the top left
- 3Type a descriptive name: 'Zoho CRM VIP Case → Slack Alert'
- 4Press Enter to save the scenario name
Canvas > Add Module > Zoho CRM > Watch Records
Add the Zoho CRM trigger module
Click the large circle in the center of the canvas to open the module picker. Search for 'Zoho CRM' in the search bar and select it. Make will show a list of available triggers and actions — choose 'Watch Records'. This trigger fires via webhook-like polling on a very short interval and detects new records in any Zoho CRM module you specify, including Cases.
- 1Click the empty circle on the canvas
- 2Type 'Zoho CRM' in the module search field
- 3Select 'Zoho CRM' from the results
- 4Choose 'Watch Records' from the trigger list
- 5Click 'Add' to place the module
Zoho CRM Module > Connection > Add > OAuth
Connect your Zoho CRM account
In the configuration panel, click 'Add' next to the Connection field to authenticate. Make will open a popup asking for your Zoho CRM data center region — select the correct one (US, EU, AU, IN, or JP) based on where your Zoho account is hosted. Log in with your Zoho credentials in the OAuth popup. Make will request read access to your CRM data.
- 1Click the 'Add' button next to the Connection field
- 2Select your Zoho data center region from the dropdown
- 3Click 'Save' and complete the OAuth login in the popup window
- 4Grant the requested CRM read permissions
Zoho CRM Watch Records > Type > Cases > New Records Only
Configure the trigger to watch Cases
With the connection set, configure the trigger fields. Set 'Type' to 'Module' and select 'Cases' from the Module dropdown. Set 'Watch' to 'New Records Only' so the scenario only fires when a brand-new case is created, not when existing cases are updated. Set the polling interval to the shortest available on your plan — ideally 1 minute. In the 'Maximum number of returned records' field, enter 2 to avoid processing a flood of cases if multiple come in simultaneously during the first run.
- 1Set 'Type' to 'Module'
- 2Select 'Cases' from the Module dropdown
- 3Set 'Watch' to 'New Records Only'
- 4Set the maximum returned records to 2
- 5Click 'OK' to save the trigger configuration
Canvas > Arrow between modules > Right-click > Set up a filter
Add a filter to catch VIP accounts only
Click the small wrench icon on the arrow between the Zoho CRM trigger and the next module (you'll add the next module first, then add the filter). After adding the next module in step 6, right-click the arrow connecting the two modules and select 'Set up a filter'. This filter is the most important part of this workflow — without it, every new case triggers a Slack alert, not just VIP ones. Use the filter to check the account tier field from Zoho CRM.
- 1After adding your next module, right-click the connecting arrow
- 2Select 'Set up a filter'
- 3Set Condition 1: map the Zoho CRM field 'Account_Type' (or your custom tier field)
- 4Set the operator to 'Equal to'
- 5Enter the value 'VIP' or 'Enterprise' — match exactly what's stored in Zoho CRM
- 6Click 'OK' to apply the filter
Canvas > + > Slack > Create a Message
Add the Slack module
Click the '+' icon on the right edge of the Zoho CRM module to add the next module. Search for 'Slack' and select it. From the action list, choose 'Create a Message'. This is the action that posts the alert to your Slack channel. You'll connect your Slack workspace in the next step.
- 1Click the '+' icon on the right side of the Zoho CRM module
- 2Search for 'Slack' in the module picker
- 3Select 'Slack' from the results
- 4Choose 'Create a Message' from the action list
- 5Click 'Add' to place the module
Slack Module > Connection > Add > Slack OAuth
Connect your Slack workspace
In the Slack module configuration panel, click 'Add' next to the Connection field. Make will redirect you through Slack's OAuth flow. Sign into your Slack workspace and authorize Make. You'll need to be a Slack workspace admin or have permission to install apps — if you're not, coordinate with your IT admin before this step.
- 1Click 'Add' next to the Connection field in the Slack module
- 2Select your Slack workspace from the dropdown in the OAuth popup
- 3Click 'Allow' to grant Make permission to post messages
- 4Confirm the connection is shown in the Connection field
Slack Module > Channel > Text > Variable Picker
Configure the Slack message content
With Slack connected, set the Channel field to your VIP support channel (e.g., #support-vip). In the 'Text' field, build the alert message by clicking inside the field and using Make's variable picker to insert Zoho CRM data. Click the Zoho CRM module icon in the variable picker to see all available fields. Build a message that includes the case subject, account name, priority, and a direct CRM link. Use Slack's mrkdwn format for bold text: *bold*.
- 1Set 'Channel' to your VIP support channel (e.g., #support-vip)
- 2Click inside the 'Text' field to open the variable picker
- 3Type your message template, inserting Zoho CRM variables
- 4Use this structure: ':rotating_light: *VIP Case Alert*\n*Account:* [Account_Name]\n*Case:* [Subject]\n*Priority:* [Priority]\n*Status:* [Status]\n*Link:* https://crm.zoho.com/crm/EntityInfo.do?module=Cases&id=[id]'
- 5Click 'OK' to save the Slack module configuration
📬 New entry: {{1.name}}
Email: {{1.email}}
Details: {{1.description}}Canvas > Clock Icon (bottom left) > Scheduling > Interval
Set the scheduling interval
Click the clock icon at the bottom left of the canvas to open the scenario scheduling settings. Set the interval to '1 minute' if your Make plan supports it (Core and above). If you're on the free plan, the minimum is 15 minutes. Click 'OK'. This controls how often Make polls Zoho CRM for new cases — shorter intervals mean faster alerts but consume more Make operations.
- 1Click the clock icon at the bottom left of the scenario canvas
- 2Select 'Minutes' as the interval unit
- 3Set the value to '1' (or the minimum your plan allows)
- 4Click 'OK' to save the schedule
Canvas > Run once > Zoho CRM (create test case) > Canvas execution view
Run a test with a real Zoho CRM case
Before activating the scenario, click 'Run once' at the bottom of the canvas. Then immediately go to Zoho CRM and create a test case assigned to a VIP account. Return to Make within 2 minutes and watch the scenario execution. Click each module to inspect the data bubbles — green means success, red means an error. Verify the filter caught the right case and the Slack message arrived in #support-vip.
- 1Click 'Run once' at the bottom left of the canvas
- 2Open Zoho CRM in a new tab
- 3Create a new case under a VIP or Enterprise account
- 4Return to Make and wait for the scenario to execute
- 5Click each module's data bubble to inspect what was received and sent
Canvas > Toggle Switch (bottom left) > Active
Activate the scenario
Once the test passes, click the toggle switch at the bottom left of the canvas to activate the scenario. The toggle turns blue and the status changes from 'Inactive' to 'Active'. Make will now poll Zoho CRM on your set interval continuously. Check the scenario's execution history after 24 hours to confirm it's running cleanly and operation counts are within your plan limits.
- 1Confirm the test run completed without errors
- 2Click the toggle switch at the bottom left to activate
- 3Verify the status label changes to 'Active' (blue)
- 4Check back in the 'History' tab after 1 hour to confirm successful runs
Paste this formula into a Make 'Set Variable' module placed between the Zoho CRM trigger and the Slack module. It formats the priority field with an emoji indicator and truncates long case descriptions to 200 characters so the Slack message stays readable. Add the Set Variable module by clicking + after the filter, then reference the output variables (formatted_priority, short_description) in your Slack text field.
JavaScript — Custom Function{{-- Place in a Set Variable or Tools > Set Multiple Variables module --}}▸ Show code
{{-- Place in a Set Variable or Tools > Set Multiple Variables module --}}
{{-- Variable 1: Priority with emoji --}}
formatted_priority =... expand to see full code
{{-- Place in a Set Variable or Tools > Set Multiple Variables module --}}
{{-- Variable 1: Priority with emoji --}}
formatted_priority =
if(Priority = "Critical"; "🔴 Critical";
if(Priority = "High"; "🟠 High";
if(Priority = "Medium"; "🟡 Medium";
if(Priority = "Low"; "🟢 Low";
Priority
)
)
)
)
{{-- Variable 2: Truncate description to 200 chars --}}
short_description =
if(length(Description) > 200;
substring(Description; 0; 200) & "...(truncated)";
if(length(Description) = 0;
"No description provided";
Description
)
)
{{-- Variable 3: Formatted creation timestamp --}}
formatted_time = formatDate(Created_Time; "MMM D, YYYY h:mm A"; "UTC")Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Make for this if your support team needs conditional logic in the alert path — for example, routing Critical cases to a different channel than High cases, or transforming Zoho CRM picklist values into emoji-formatted Slack text. Make's router module and filter system handle this in a single scenario without writing code. You'd also pick Make if you're already using it for other Zoho CRM workflows, since consolidating scenarios reduces your total API call count against Zoho's daily limits. The one scenario where you'd skip Make entirely: if you need true instant alerts (under 10 seconds), use Zoho Flow with a native webhook — Make's polling architecture means a minimum 1-minute lag even on paid plans.
The math here is simple. Each scenario run uses 2 Make operations (1 for the Zoho CRM trigger, 1 for the Slack message). If you get 200 VIP cases per month, that's 400 operations. At a 1-minute polling interval with zero new cases, Make still burns 1 operation per poll — that's 43,200 polls per month. In practice, Make is smart enough to count empty polls as fractional operations, but budget for roughly 1,000–2,000 operations/month on a quiet account. Make's Core plan gives you 10,000 operations/month for $9. Zapier's equivalent (Starter plan) costs $19.99/month for 750 tasks — significantly more expensive for the same volume.
Zapier does one thing better here: its Zoho CRM trigger is more mature and handles Zoho's quirky API pagination more reliably than Make's, which occasionally misses records when Zoho returns results in non-chronological order. n8n wins on self-hosting — if your company can't send CRM data through a third-party cloud, run n8n on your own infrastructure and Zoho data never leaves your environment. Power Automate is the right call if your team is already in Microsoft 365, since the Zoho CRM connector is pre-certified and IT governance approvals are faster. Pipedream gives developers the most flexibility with full Node.js and direct Zoho API access, but there's no visual builder for non-technical support ops people. Make remains the right choice for teams that want a visual builder, need conditional routing between Slack channels, and don't have a developer available to maintain code-based workflows.
Three things you'll hit after go-live. First, Zoho CRM's API rate limit is 5,000 calls per day on standard plans — if you have five Make scenarios all watching Zoho CRM at 1-minute intervals, you'll consume roughly 7,200 API calls per day and hit the ceiling. Consolidate Zoho-watching scenarios into one using a router. Second, Zoho CRM's 'Case_Owner' field returns the owner's name as a string in some API responses and as a nested object in others depending on your CRM version — test this field specifically during your setup and confirm what Make actually receives before building the Slack message around it. Third, Slack's rate limit for bot messages is 1 message per second per channel — if a data migration creates 50 VIP cases simultaneously, Make will queue the Slack posts and some may be delayed by up to a minute, or fail with a 429 error if retries aren't configured.
Ideas for what to build next
- →Route by Priority to Different Slack Channels — Add a Make router module after the filter to send Critical cases to #support-critical and High cases to #support-vip, giving each tier a separate response queue and reducing noise for non-critical alerts.
- →Create a Zoho CRM Task Automatically — After the Slack alert, add a second branch in the router to create a follow-up Task in Zoho CRM assigned to the case owner with a due date 2 hours out — so the alert in Slack and the action item in CRM are created in the same scenario run.
- →Send a Daily VIP Case Digest — Build a separate scheduled Make scenario that runs at 9 AM each day, queries Zoho CRM for all open VIP cases, and posts a single summary digest to Slack instead of individual alerts — reducing Slack noise while keeping the team informed.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup