How to Send Monday.com Status Alerts to Slack with Pipedream

pipedream.com > Workflows > + New Workflow

Create a new Pipedream Workflow

Go to pipedream.com and click 'Workflows' in the left sidebar. Click the green '+ New Workflow' button at the top right. You'll land on the workflow canvas with an empty trigger slot at the top. Give the workflow a name — something like 'Monday Status → Slack Alert' — by clicking the pencil icon next to 'My Workflow' at the top.

1. 1Click 'Workflows' in the left sidebar
2. 2Click '+ New Workflow' in the top right
3. 3Click the pencil icon next to 'My Workflow' and rename it
4. 4Click the 'Add Trigger' block at the top of the canvas

Trigger Panel > Search 'Monday.com' > New Event (Instant)

Add the Monday.com Webhook Trigger

In the trigger search box, type 'Monday.com' and select the Monday.com app. Choose the trigger called 'New Event (Instant)' — this uses Monday.com's native webhook system so the workflow fires within seconds of a board change. You'll be prompted to connect your Monday.com account via OAuth; click 'Connect Account' and follow the auth flow. Once connected, select the specific board you want to monitor from the dropdown.

1. 1Type 'Monday.com' in the trigger search box
2. 2Select 'Monday.com' from the app results
3. 3Choose 'New Event (Instant)' as the trigger
4. 4Click 'Connect Account' and complete the OAuth flow
5. 5Select your target board from the 'Board ID' dropdown

Trigger Config > Event Type > change_column_value

Configure Which Monday.com Events to Watch

Under the trigger config, expand the 'Event Type' dropdown. You'll see options including 'change_column_value', 'create_pulse' (item created), and 'item_due_date_arrived'. Select 'change_column_value' to catch status changes. If you also want to catch item creation, you'll need a second workflow using 'create_pulse' — Pipedream doesn't let you subscribe to multiple event types in a single trigger step. For status changes specifically, also set the 'Column ID' field to your board's status column ID.

1. 1Open the 'Event Type' dropdown in the trigger config
2. 2Select 'change_column_value'
3. 3Set 'Column ID' to the ID of your status column (e.g., 'status')
4. 4Click 'Save & Test' to pull a sample event

Canvas > + > Run Node.js code

Add a Node.js Code Step to Parse the Payload

Click the '+' button below the trigger to add a new step. Choose 'Run Node.js code' from the step options. Pipedream passes the Monday.com webhook payload as an object you can access via steps.trigger.event. The raw payload contains the item name, board name, previous column value, and new column value — but they're nested and need to be extracted before sending to Slack. This step pulls out the fields you actually care about and formats the Slack message text.

1. 1Click the '+' icon below the Monday.com trigger
2. 2Select 'Run Node.js code' from the step type list
3. 3Paste the extraction code into the code editor (see Pro Tip below)
4. 4Click 'Test' to run the step against your sample event

Paste this into the Node.js code step (Step 4). It extracts and formats all the fields you need from the raw Monday.com webhook payload, builds the item URL, handles the nested JSON parsing for status labels, and returns a clean object that every downstream step can reference with steps.parse_payload.$return_value.fieldName.

export default defineComponent({
  async run({ steps, $ }) {
    const event = steps.trigger.event.event;

export default defineComponent({
  async run({ steps, $ }) {
    const event = steps.trigger.event.event;

    if (!event) {
      $.flow.exit('No event payload found — skipping');
    }

    // Monday.com sends status values as nested JSON strings
    // Parse them safely before reading the label
    let newStatus = 'Unknown';
    let previousStatus = 'Unknown';

    try {
      const newVal = typeof event.value === 'string'
        ? JSON.parse(event.value)
        : event.value;
      newStatus = newVal?.label?.text || newVal?.index?.toString() || 'Unknown';
    } catch (e) {
      console.log('Could not parse new value:', event.value);
    }

    try {
      const prevVal = typeof event.previousValue === 'string'
        ? JSON.parse(event.previousValue)
        : event.previousValue;
      previousStatus = prevVal?.label?.text || prevVal?.index?.toString() || 'Not set';
    } catch (e) {
      console.log('Could not parse previous value:', event.previousValue);
    }

    // Build the direct Monday.com item URL
    const boardId = event.boardId;
    const itemId = event.pulseId;
    const itemUrl = boardId && itemId
      ? `https://monday.com/boards/${boardId}/pulses/${itemId}`
      : null;

    // Format the timestamp for display in Slack
    const changedAt = event.changedAt
      ? new Date(event.changedAt * 1000).toUTCString()
      : 'Unknown time';

    const result = {
      itemName: event.pulseName || 'Unnamed item',
      boardId: boardId,
      itemId: itemId,
      itemUrl: itemUrl,
      newStatus: newStatus,
      previousStatus: previousStatus,
      columnId: event.columnId,
      userId: event.userId,
      changedAt: changedAt,
      slackMessage: `*${event.pulseName}* moved from \`${previousStatus}\` → \`${newStatus}\``,
    };

    console.log('Parsed Monday event:', JSON.stringify(result, null, 2));
    return result;
  }
});

Canvas > + > Filter

Add a Filter Step for Relevant Status Changes

Click '+' below the code step and select 'Filter' from the built-in Pipedream helpers. This lets you stop the workflow early if the status change isn't worth notifying about — for example, if someone moves an item from 'Done' back to 'Done' after a typo correction. Set the condition to check that steps.parse_payload.$return_value.newStatus does not equal steps.parse_payload.$return_value.previousStatus. This prevents duplicate or meaningless Slack messages.

1. 1Click '+' below the Node.js code step
2. 2Select 'Filter' from the helper step list
3. 3Set the left operand to '{{steps.parse_payload.$return_value.newStatus}}'
4. 4Set condition to 'does not equal'
5. 5Set the right operand to '{{steps.parse_payload.$return_value.previousStatus}}'

Canvas > + > Slack > Send Message to a Channel

Add the Slack Step

Click '+' below the filter step and search for 'Slack'. Select the Slack app and choose the action 'Send Message to a Channel'. Click 'Connect Account' and authenticate with your Slack workspace — you'll need to authorize the Pipedream Slack app. Once connected, select the target channel from the dropdown (e.g., #project-updates). Set the 'Message Text' field using values from the previous steps.

1. 1Click '+' below the filter step
2. 2Search for 'Slack' and select the Slack app
3. 3Choose 'Send Message to a Channel' as the action
4. 4Click 'Connect Account' and authorize the Pipedream Slack app
5. 5Select the target channel from the 'Channel' dropdown

Slack Step > Message Text field

Build the Slack Message

In the 'Message Text' field, build your notification using the parsed values from the code step. Use Slack's mrkdwn formatting for emphasis. A solid format: '*{{steps.parse_payload.$return_value.itemName}}* moved from {{steps.parse_payload.$return_value.previousStatus}} → {{steps.parse_payload.$return_value.newStatus}} on board *{{steps.parse_payload.$return_value.boardName}}*'. Add the item URL on a new line so team members can click straight into Monday.com. Optionally, set the 'Username' field to 'Monday.com Bot' and add an emoji icon.

1. 1Click into the 'Message Text' field
2. 2Type your message template using {{steps.parse_payload.$return_value.fieldName}} references
3. 3Add the item URL on a separate line
4. 4Set 'Username' to 'Monday.com Bot' in the optional fields
5. 5Set 'Icon Emoji' to ':white_check_mark:' or similar

Workflow Canvas > Test Workflow button

Test the Full Workflow End-to-End

Click 'Test Workflow' at the top of the canvas. This runs all steps in sequence using the sample event captured in Step 3. Watch each step turn green as it passes. Check your Slack channel — the message should appear within a few seconds. If any step shows a red error badge, click it to see the exact error output and which line failed.

1. 1Click 'Test Workflow' at the top of the canvas
2. 2Watch each step execute in sequence
3. 3Open your Slack channel to confirm the message arrived
4. 4Click any red step badge to read the error detail

Workflow Canvas > Deploy button (top right)

Deploy the Workflow

Click the 'Deploy' button in the top right of the canvas. Pipedream will register the Monday.com webhook automatically — you don't need to manually paste a URL into Monday.com. The workflow status changes from 'Development' to 'Active'. Go back to Monday.com and change an item status on your target board. The Slack message should appear within 5 seconds.

1. 1Click 'Deploy' in the top right corner
2. 2Confirm the workflow status shows 'Active'
3. 3Go to Monday.com and change a real item status
4. 4Verify the Slack message arrives in under 10 seconds

Workflows > [Your Workflow] > Events tab

Monitor Workflow Runs in the Event Inspector

In the left sidebar, click 'Workflows' and then select your deployed workflow. Click the 'Events' tab to see every run — successes, errors, and filtered-out events. Each row shows the timestamp, trigger payload, and per-step output. This is where you debug any missed notifications. Pipedream retains event history for 30 days on the free tier.

1. 1Click 'Workflows' in the left sidebar
2. 2Select your deployed Monday → Slack workflow
3. 3Click the 'Events' tab
4. 4Click any individual event row to see the full step-by-step execution log