How to Send Zoho CRM Lost Deals to Slack with Pipedream

pipedream.com > Dashboard > New Workflow

Create a new Pipedream Workflow

Go to pipedream.com and sign in. Click 'New Workflow' in the top-right corner of the dashboard. You'll land on the workflow canvas with an empty trigger slot at the top. Give the workflow a name — something like 'Zoho Lost Deal → Slack Alert' — by clicking the pencil icon next to the default title. This name appears in your Pipedream dashboard and in error notification emails.

1. 1Sign in at pipedream.com
2. 2Click the blue 'New Workflow' button in the top-right
3. 3Click the pencil icon next to the default workflow name
4. 4Type 'Zoho Lost Deal → Slack Alert' and press Enter

Workflow Canvas > Trigger > Search Apps > Zoho CRM > New or Updated Module

Configure the Zoho CRM Webhook Trigger

Click the trigger block and search for 'Zoho CRM' in the app search bar. Select the 'New or Updated Module' event — this fires whenever a record changes in any Zoho CRM module. Choose 'Deals' as the module. Pipedream will generate a unique webhook URL for this trigger immediately. Copy that URL — you'll need it in Zoho CRM in the next step.

1. 1Click the empty trigger block on the canvas
2. 2Type 'Zoho CRM' in the search box
3. 3Select 'Zoho CRM' from the results
4. 4Choose 'New or Updated Module' as the trigger event
5. 5Set Module to 'Deals'
6. 6Copy the generated webhook URL from the trigger panel

Trigger Panel > Connect Account > Zoho CRM OAuth Popup

Connect Your Zoho CRM Account

In the trigger configuration panel, click 'Connect Account' under the Zoho CRM section. A popup will appear asking you to authorize Pipedream to access your Zoho CRM org. Sign in with your Zoho credentials and click 'Accept'. Pipedream stores the OAuth token in Connected Accounts — you won't need to re-enter credentials for future Zoho steps in any workflow.

1. 1Click 'Connect Account' in the Zoho CRM trigger panel
2. 2Sign in with your Zoho CRM admin credentials in the popup
3. 3Click 'Accept' to grant Pipedream read access
4. 4Select the connected account from the dropdown if prompted

Zoho CRM > Setup > Developer Space > Webhooks > + New Webhook

Register the Webhook in Zoho CRM

Open Zoho CRM in a new browser tab. Navigate to Setup > Developer Space > Webhooks and click '+ New Webhook'. Give it a name like 'Lost Deal Pipedream Alert'. Paste the Pipedream webhook URL from Step 2 into the URL field. Set the method to POST and the format to JSON. Under Modules, select 'Deals' and set the trigger event to 'Edit'. This fires the webhook every time a deal record is saved.

1. 1In Zoho CRM, go to Setup > Developer Space > Webhooks
2. 2Click '+ New Webhook'
3. 3Enter a name: 'Lost Deal Pipedream Alert'
4. 4Paste the Pipedream URL into the Notify URL field
5. 5Set Method to POST, Format to JSON
6. 6Set Module to Deals, Trigger to Edit
7. 7Click Save

Zoho CRM > Any Deal Record > Edit > Stage: Lost > Save | Pipedream Trigger Panel > Events tab

Send a Test Event to Capture the Payload

Go back to Pipedream. The trigger is listening. In Zoho CRM, open any existing deal, change the Stage field to 'Lost', fill in a Loss Reason and Competitor if your fields support it, and click Save. Pipedream will capture this event within 2–5 seconds. Click on the captured event in the trigger panel to see the full JSON payload. Expand the body to confirm all the fields you added in Step 4 are present.

1. 1Open a test deal in Zoho CRM
2. 2Change Stage to 'Lost', enter a Loss Reason and Competitor
3. 3Click Save in Zoho CRM
4. 4Switch to Pipedream and click the 'Events' tab in the trigger panel
5. 5Click the captured event to expand the JSON payload
6. 6Verify Deal_Name, Stage, Loss_Reason, Competitor, Amount, and Owner are all present

Workflow Canvas > + Add Step > Run Node.js Code

Add a Code Step to Filter for Lost Deals Only

Click '+ Add Step' below the trigger and choose 'Run Node.js code'. This step checks whether the incoming deal's Stage is actually 'Lost' before continuing. Without this filter, the workflow runs on every deal edit — including stage changes like Proposal to Negotiation — which means noisy, incorrect Slack alerts. The code uses $.flow.exit() to halt execution for non-lost deals without marking the run as an error.

1. 1Click '+ Add Step' below the trigger block
2. 2Select 'Run Node.js Code'
3. 3Paste the filter code into the code editor
4. 4Click 'Test' to verify it passes for Stage = Lost and exits for other stages

This code combines the filter, deduplication check, and Slack Block Kit message formatting into two code steps. Paste the filter/dedup block into Step 6 and the formatter block into Step 7 on your Pipedream workflow canvas. The deduplication uses Pipedream's built-in key-value data store to prevent duplicate Slack alerts when Zoho fires the webhook twice for the same deal save.

// STEP 6: Filter for Lost deals + deduplicate using Pipedream Data Store
import { axios } from '@pipedream/platform';
export default defineComponent({

// STEP 6: Filter for Lost deals + deduplicate using Pipedream Data Store
import { axios } from '@pipedream/platform';

export default defineComponent({
  props: {
    data: { type: 'data_store' },
  },
  async run({ steps, $ }) {
    const payload = steps.trigger.event.body;
    const deal = Array.isArray(payload.Deals) ? payload.Deals[0] : payload;

    // Only continue if Stage is Lost
    const stage = deal.Stage ?? '';
    if (stage !== 'Lost') {
      $.flow.exit('Deal stage is not Lost — skipping');
    }

    // Deduplicate: skip if same deal was processed in the last 60 seconds
    const dealId = deal.id ?? deal.Deal_Name;
    const lastSeen = await this.data.get(dealId);
    const now = Date.now();
    if (lastSeen && now - lastSeen < 60000) {
      $.flow.exit(`Duplicate event for deal ${dealId} — skipping`);
    }
    await this.data.set(dealId, now);

    // Export clean deal object for next step
    return {
      dealName: deal.Deal_Name ?? 'Unnamed Deal',
      stage: deal.Stage,
      lossReason: deal.Loss_Reason ?? 'Not specified',
      competitor: deal.Competitor ?? 'Unknown',
      amount: deal.Amount ? `$${Number(deal.Amount).toLocaleString()}` : 'N/A',
      accountName: deal.Account_Name ?? 'Unknown Account',
      ownerName: deal.Owner?.name ?? 'Unknown Owner',
      closingDate: deal.Closing_Date ?? 'N/A',
      dealId,
    };
  },
});

// STEP 7: Format Slack Block Kit message
export default defineComponent({
  async run({ steps, $ }) {
    const d = steps.filter_lost_deal.$return_value;

    const blocks = [
      {
        type: 'header',
        text: {
          type: 'plain_text',
          text: `🔴 Deal Lost: ${d.dealName}`,
          emoji: true,
        },
      },
      {
        type: 'section',
        fields: [
          { type: 'mrkdwn', text: `*Account:*\n${d.accountName}` },
          { type: 'mrkdwn', text: `*Amount:*\n${d.amount}` },
          { type: 'mrkdwn', text: `*Loss Reason:*\n${d.lossReason}` },
          { type: 'mrkdwn', text: `*Competitor:*\n${d.competitor}` },
          { type: 'mrkdwn', text: `*Owner:*\n${d.ownerName}` },
          { type: 'mrkdwn', text: `*Expected Close:*\n${d.closingDate}` },
        ],
      },
      {
        type: 'divider',
      },
      {
        type: 'context',
        elements: [
          {
            type: 'mrkdwn',
            text: `Deal ID: ${d.dealId} • Logged via Pipedream`,
          },
        ],
      },
    ];

    return { blocks };
  },
});

Workflow Canvas > + Add Step > Run Node.js Code

Add a Code Step to Format the Slack Message

Click '+ Add Step' and add another Node.js code step. This step pulls the deal fields from the Zoho webhook payload and constructs a structured Slack Block Kit message. Using Block Kit instead of a plain text message gives you bold deal names, organized sections for loss reason and competitor, and an amount field — all scannable at a glance in Slack. The code exports the formatted blocks object for the next step to consume.

1. 1Click '+ Add Step' below the filter step
2. 2Select 'Run Node.js Code'
3. 3Paste the Slack Block Kit formatting code into the editor
4. 4Click 'Test' and check the exported 'blocks' array in the step output

This code combines the filter, deduplication check, and Slack Block Kit message formatting into two code steps. Paste the filter/dedup block into Step 6 and the formatter block into Step 7 on your Pipedream workflow canvas. The deduplication uses Pipedream's built-in key-value data store to prevent duplicate Slack alerts when Zoho fires the webhook twice for the same deal save.

// STEP 6: Filter for Lost deals + deduplicate using Pipedream Data Store
import { axios } from '@pipedream/platform';
export default defineComponent({

// STEP 6: Filter for Lost deals + deduplicate using Pipedream Data Store
import { axios } from '@pipedream/platform';

export default defineComponent({
  props: {
    data: { type: 'data_store' },
  },
  async run({ steps, $ }) {
    const payload = steps.trigger.event.body;
    const deal = Array.isArray(payload.Deals) ? payload.Deals[0] : payload;

    // Only continue if Stage is Lost
    const stage = deal.Stage ?? '';
    if (stage !== 'Lost') {
      $.flow.exit('Deal stage is not Lost — skipping');
    }

    // Deduplicate: skip if same deal was processed in the last 60 seconds
    const dealId = deal.id ?? deal.Deal_Name;
    const lastSeen = await this.data.get(dealId);
    const now = Date.now();
    if (lastSeen && now - lastSeen < 60000) {
      $.flow.exit(`Duplicate event for deal ${dealId} — skipping`);
    }
    await this.data.set(dealId, now);

    // Export clean deal object for next step
    return {
      dealName: deal.Deal_Name ?? 'Unnamed Deal',
      stage: deal.Stage,
      lossReason: deal.Loss_Reason ?? 'Not specified',
      competitor: deal.Competitor ?? 'Unknown',
      amount: deal.Amount ? `$${Number(deal.Amount).toLocaleString()}` : 'N/A',
      accountName: deal.Account_Name ?? 'Unknown Account',
      ownerName: deal.Owner?.name ?? 'Unknown Owner',
      closingDate: deal.Closing_Date ?? 'N/A',
      dealId,
    };
  },
});

// STEP 7: Format Slack Block Kit message
export default defineComponent({
  async run({ steps, $ }) {
    const d = steps.filter_lost_deal.$return_value;

    const blocks = [
      {
        type: 'header',
        text: {
          type: 'plain_text',
          text: `🔴 Deal Lost: ${d.dealName}`,
          emoji: true,
        },
      },
      {
        type: 'section',
        fields: [
          { type: 'mrkdwn', text: `*Account:*\n${d.accountName}` },
          { type: 'mrkdwn', text: `*Amount:*\n${d.amount}` },
          { type: 'mrkdwn', text: `*Loss Reason:*\n${d.lossReason}` },
          { type: 'mrkdwn', text: `*Competitor:*\n${d.competitor}` },
          { type: 'mrkdwn', text: `*Owner:*\n${d.ownerName}` },
          { type: 'mrkdwn', text: `*Expected Close:*\n${d.closingDate}` },
        ],
      },
      {
        type: 'divider',
      },
      {
        type: 'context',
        elements: [
          {
            type: 'mrkdwn',
            text: `Deal ID: ${d.dealId} • Logged via Pipedream`,
          },
        ],
      },
    ];

    return { blocks };
  },
});

Workflow Canvas > + Add Step > Slack > Send a Message

Add the Slack Step to Post the Message

Click '+ Add Step' and search for 'Slack'. Select the 'Send a Message' action. Connect your Slack workspace by clicking 'Connect Account' — this uses Slack's OAuth flow and requires the channels:write and chat:write scopes. Set the Channel field to your management channel name, like #lost-deal-alerts. In the Blocks field, reference the blocks array exported from the previous code step using the expression picker.

1. 1Click '+ Add Step' below the formatting code step
2. 2Search for 'Slack' and select it
3. 3Choose 'Send a Message' as the action
4. 4Click 'Connect Account' and authorize Pipedream in the Slack OAuth popup
5. 5Set Channel to '#lost-deal-alerts' (or your channel name)
6. 6In the Blocks field, click the expression picker and reference steps.format_message.blocks

Workflow Canvas > Format Code Step > Edit Code

Add Error Handling for Missing Fields

Not every lost deal in Zoho will have a Competitor or Loss Reason filled in. If your Slack message template references these fields and they're null, the message either breaks or posts blank lines. Add a short code step before the Slack step (or inside the formatter) to set default values: 'Not specified' for Loss Reason and 'Unknown' for Competitor. This keeps the Slack message clean and readable even for incomplete records.

1. 1Open the formatting code step from Step 7
2. 2Add null-coalescing defaults for Loss_Reason and Competitor fields
3. 3Set fallback text: Loss_Reason ?? 'Not specified', Competitor ?? 'Unknown'
4. 4Click Test to confirm the message renders correctly when fields are empty

Workflow Canvas > Deploy Button (top-right)

Deploy and Enable the Workflow

Click the blue 'Deploy' button in the top-right corner of the Pipedream workflow canvas. The workflow status changes from 'Development' to 'Active'. From this point, every time a deal is edited in Zoho CRM and saved as Lost, the webhook fires, Pipedream processes it, and the Slack alert posts — automatically, with no manual trigger required. Check the 'Event History' tab over the next 24 hours to confirm real events are flowing through correctly.

1. 1Click the blue 'Deploy' button in the top-right corner
2. 2Confirm the status badge changes to 'Active'
3. 3Mark a real deal as Lost in Zoho CRM to test end-to-end
4. 4Check the Slack channel for the alert within 30 seconds
5. 5Review Event History in Pipedream to confirm the run completed without errors

Workflow Canvas > Settings (gear icon) > Error Handling

Set Up Error Notifications

In Pipedream, click on the workflow settings (gear icon near the workflow name). Under 'Error Handling', enter an email address or Slack channel to receive alerts when the workflow fails. This matters because Zoho webhook failures are silent — if Pipedream has an error, no Slack message posts and no one knows. Routing errors to a separate #pipedream-errors channel gives you immediate visibility without cluttering the management channel.

1. 1Click the gear icon near the workflow title
2. 2Go to the 'Error Handling' section
3. 3Enter your email or a Slack webhook URL for error alerts
4. 4Click Save