How to Send Lost Deal Alerts from Zoho CRM to Slack with Power Automate

make.powerautomate.com > My flows > + New flow > Automated cloud flow

Set Up the Zoho CRM Webhook Trigger in Power Automate

Go to make.powerautomate.com and click 'My flows' in the left sidebar, then click '+ New flow' and select 'Automated cloud flow'. Name the flow something like 'Zoho Lost Deal → Slack Alert'. In the trigger search bar, type 'Zoho CRM' and select the connector. Choose the trigger 'When a record is created or updated' — this is the correct trigger for catching stage changes in Zoho CRM deals.

1. 1Click 'My flows' in the left sidebar
2. 2Click '+ New flow' then select 'Automated cloud flow'
3. 3Enter a flow name, e.g. 'Zoho Lost Deal → Slack Alert'
4. 4In the trigger search bar type 'Zoho CRM'
5. 5Select 'When a record is created or updated' as the trigger

Flow canvas > Zoho CRM trigger card > Module Name dropdown

Configure the Zoho CRM Trigger for Deals Module

Inside the trigger card, set the 'Module Name' dropdown to 'Deals'. Leave the trigger set to fire on both creates and updates — you cannot filter to updates-only at the trigger level in this connector. The filtering to lost deals happens in a Condition step later. Make sure your Zoho CRM Connection is authenticated before moving forward; Power Automate will prompt you to sign in if no connection exists yet.

1. 1Click inside the Zoho CRM trigger card to expand its settings
2. 2Click the 'Module Name' dropdown and select 'Deals'
3. 3If prompted, click 'Sign in' to create a new Zoho CRM Connection and authenticate with your Zoho account
4. 4Confirm the Connection shows your Zoho org domain in the connection label

Flow canvas > + New step > Control > Condition

Add a Condition to Filter for Lost Stage Only

Click '+ New step' and search for 'Condition' — select the built-in Control action named 'Condition'. This is where you isolate only deals whose Stage field equals 'Closed Lost'. In the left value box, click inside and select 'Stage' from the dynamic content picker (this is the Deal_Stage field from Zoho). Set the operator to 'is equal to' and type 'Closed Lost' in the right value box exactly as it appears in your Zoho CRM picklist.

1. 1Click '+ New step' below the trigger card
2. 2Search for 'Condition' and select the 'Condition' Control action
3. 3Click the left value box and choose 'Stage' from the dynamic content panel
4. 4Set the middle dropdown to 'is equal to'
5. 5Type 'Closed Lost' in the right value box (match the exact spelling in your Zoho picklist)

Flow canvas > Condition > No branch > + Add an action > Control > Terminate

Add a Terminate Action in the 'No' Branch

Click inside the 'No' branch of your Condition. Add a 'Terminate' action from the Control connector. Set Status to 'Succeeded' and leave the message blank. This cleanly ends the flow run for any deal update that is not a lost deal, keeping your flow run history clean and avoiding unnecessary Slack noise.

1. 1Click '+ Add an action' inside the 'No' branch
2. 2Search for 'Terminate' and select the Control action
3. 3Set the 'Status' field to 'Succeeded'
4. 4Leave the 'Code' and 'Message' fields empty

Flow canvas > Condition > Yes branch > + Add an action > Data Operation > Parse JSON

Add a Parse JSON Action to Extract Zoho Deal Fields

Inside the 'Yes' branch, click '+ Add an action' and search for 'Parse JSON' — it lives under the Data Operation connector. In the 'Content' field, insert the dynamic content output from the Zoho CRM trigger (typically labeled 'body' or the raw record output). You need to provide a schema so Power Automate can surface individual fields like Deal_Name, Closing_Reason, Competitor, and Amount as named tokens. Click 'Generate from sample' and paste a real Zoho deal JSON payload to auto-generate the schema.

1. 1Click '+ Add an action' inside the 'Yes' branch
2. 2Search 'Parse JSON' and select 'Parse JSON' under Data Operation
3. 3In the 'Content' field, select the raw body output from the Zoho CRM trigger via the dynamic content panel
4. 4Click 'Generate from sample', paste a real Zoho CRM deal record JSON, and click 'Done'
5. 5Verify that fields like Deal_Name, Closing_Reason, and Competitor appear in the generated schema

Flow canvas > Condition > Yes branch > + Add an action > Data Operation > Compose

Add a Compose Action to Build the Slack Message

Add a 'Compose' action (Data Operation connector) in the Yes branch after Parse JSON. Use this to construct the Slack Block Kit JSON payload. This gives you full control over the message format before passing it to the Slack action. Build a JSON object with a 'blocks' array that includes a header block with the deal name, a section block with loss reason and competitor, and a context block with deal amount and close date.

1. 1Click '+ Add an action' after the Parse JSON step
2. 2Search 'Compose' and select 'Compose' under Data Operation
3. 3Click inside the 'Inputs' field and switch to the expression editor
4. 4Paste the Block Kit JSON structure (see pro_tip_code below) referencing Parse JSON dynamic tokens
5. 5Click 'OK' to save the expression

Flow canvas > Yes branch > + Add an action > Slack > Post message (V2)

Connect to Slack and Configure the Post Message Action

Add a new action and search for 'Slack'. Select the 'Post message (V2)' action. If you don't have a Slack connection yet, click 'Sign in' and authenticate with the Slack workspace where you want alerts posted. For the 'Channel' field, type or select the management channel (e.g., #lost-deals). In the 'Message Text' field, enter a plain-text fallback. In the 'Blocks' field, reference the output of your Compose step.

1. 1Click '+ Add an action' after the Compose step
2. 2Search 'Slack' and select 'Post message (V2)'
3. 3Click 'Sign in' to create a Slack Connection if none exists; authorize Power Automate in your Slack workspace
4. 4Set the 'Channel' field to your target channel (e.g., #lost-deals)
5. 5In the 'Blocks' field, select the 'Outputs' dynamic token from the Compose step

Flow canvas > Slack action > ... menu > Configure run after

Add Error Handling with a Parallel Branch

Select the Slack 'Post message' action card, click the three-dot menu, and choose 'Configure run after'. Enable the 'has failed' and 'has timed out' checkboxes. Below the Slack action, add a parallel branch that fires only on failure: add another 'Post message' action to a different Slack channel (e.g., #automation-errors) with a static alert that the lost deal notification failed. Include the flow run ID using the expression workflow()['run']['name'] so your team can trace the failed run.

1. 1Click the '...' menu on the Slack Post message action card
2. 2Select 'Configure run after'
3. 3Check the 'has failed' and 'has timed out' boxes, then click Done
4. 4Click '+ Add a parallel branch' and add a second Slack 'Post message' action
5. 5Set the error channel to #automation-errors and include the expression workflow()['run']['name'] in the message body

make.powerautomate.com > My flows > [Your Flow] > 28 day run history

Test the Flow with a Real Zoho Deal

Save the flow, then go to your Zoho CRM account and find an existing test deal. Change its Stage to 'Closed Lost', set a Closing Reason, and fill in the Competitor field. Wait up to 60 seconds for Power Automate's polling interval to pick up the change. Back in Power Automate, click '28 day run history' in the flow detail page to see if a run fired. Click into the run to inspect each step's inputs and outputs.

1. 1Save the flow by clicking the 'Save' button in the top right
2. 2Open Zoho CRM in a separate tab and navigate to a test deal
3. 3Set Stage to 'Closed Lost', fill in Closing Reason and Competitor, and save
4. 4Wait 60 seconds then return to Power Automate
5. 5Click '28 day run history' on your flow's detail page and inspect the latest run

make.powerautomate.com > My flows > [Your Flow] > Detail page > Owners / Run only users

Turn the Flow On and Set Run-Only Permissions

If the flow is still in draft or off state, toggle it to 'On' from the flow detail page. Then click 'Edit' next to 'Run only users' at the bottom of the flow detail screen. This controls who can trigger a manual run — for an automated flow you can leave this as owner-only, but document the owning account clearly. Add at least one co-owner under 'Owners' so the flow doesn't orphan if the original creator's account is deactivated.

1. 1Navigate to the flow's detail page and confirm the status toggle reads 'On'
2. 2Scroll to the 'Owners' section at the bottom of the detail page
3. 3Click 'Edit' next to Owners and add a second owner (e.g., your team's shared admin account)
4. 4Save the ownership change

Paste this expression into the Compose action's Inputs field (switch to the Expression tab in the dynamic content panel). It builds a complete Slack Block Kit payload using dynamic tokens from the Parse JSON step, formats the Amount as currency, and truncates the Description field to 200 characters so Slack cards stay readable. Replace 'body' references with the actual Parse JSON output token names if they differ in your schema.

{
  "blocks": [
    {

{
  "blocks": [
    {
      "type": "header",
      "text": {
        "type": "plain_text",
        "text": concat('🔴 Deal Lost: ', body('Parse_JSON')?['Deal_Name'])
      }
    },
    {
      "type": "section",
      "fields": [
        {
          "type": "mrkdwn",
          "text": concat('*Loss Reason:*\n', body('Parse_JSON')?['Closing_Reason'])
        },
        {
          "type": "mrkdwn",
          "text": concat('*Competitor:*\n', if(empty(body('Parse_JSON')?['Competitor']), 'Not specified', body('Parse_JSON')?['Competitor']))
        },
        {
          "type": "mrkdwn",
          "text": concat('*Deal Value:*\n$', body('Parse_JSON')?['Amount'])
        },
        {
          "type": "mrkdwn",
          "text": concat('*Owner:*\n', body('Parse_JSON')?['Owner'])
        }
      ]
    },
    {
      "type": "section",
      "text": {
        "type": "mrkdwn",
        "text": concat('*Notes:* ', substring(if(empty(body('Parse_JSON')?['Description']), 'No notes provided.', body('Parse_JSON')?['Description']), 0, min(200, length(if(empty(body('Parse_JSON')?['Description']), 'No notes provided.', body('Parse_JSON')?['Description'])))))
      }
    },
    {
      "type": "context",
      "elements": [
        {
          "type": "mrkdwn",
          "text": concat('Account: *', body('Parse_JSON')?['Account_Name'], '* | Close Date: ', body('Parse_JSON')?['Closing_Date'])
        }
      ]
    }
  ]
}