How to Set Priority Escalation Alerts with Pipedream

Dashboard > New Workflow

Create New Pipedream Workflow

Navigate to pipedream.com and click 'New Workflow' in your dashboard. You'll see the workflow builder with an empty trigger step at the top. This is where you'll configure ClickUp to send webhook data when task priorities change.

1. 1Click the green 'New Workflow' button
2. 2Name your workflow 'ClickUp Priority Escalation'
3. 3Click 'Create Workflow' to open the builder

Trigger Step > Search Apps > ClickUp

Configure ClickUp Webhook Trigger

Click the trigger step and search for 'ClickUp' in the app list. Select 'New Webhook Event' as your trigger type. Pipedream will generate a unique webhook URL that ClickUp will call when priorities change. Copy this URL - you'll need it in the next step.

1. 1Click the empty trigger step
2. 2Search for 'ClickUp' and select it
3. 3Choose 'New Webhook Event (Instant)' trigger
4. 4Copy the webhook URL from the bottom panel

ClickUp Space > Settings > Integrations > Webhooks

Set Up ClickUp Webhook

In ClickUp, go to your Space settings and find the Webhooks section. Create a new webhook pointing to your Pipedream URL. Set it to trigger on 'taskUpdated' events only - this captures priority changes without flooding your workflow with irrelevant updates.

1. 1Open ClickUp and navigate to your Space settings
2. 2Click 'Integrations' then 'Webhooks'
3. 3Click 'Create Webhook' and paste your Pipedream URL
4. 4Check only 'taskUpdated' in the events list
5. 5Click 'Create Webhook'

ClickUp Task > Priority > Urgent | Pipedream Trigger > Test Data

Test Priority Change Detection

Change a task priority to 'Urgent' in ClickUp to trigger your webhook. Return to Pipedream and you'll see the webhook data appear in your trigger step. Click 'Select' on the test event to use this data for building the rest of your workflow.

1. 1Go to any ClickUp task and change priority to 'Urgent'
2. 2Return to your Pipedream workflow
3. 3Click 'Refresh' on the trigger step
4. 4Select the test event that appears

Add Step > Code (Node.js)

Add Priority Filter Logic

Add a new Code step after your trigger to filter for urgent priorities only. This prevents notifications for non-urgent changes. Write a simple condition that checks if the priority matches 'urgent' or '1' depending on how ClickUp sends the data.

1. 1Click the '+' button below your trigger
2. 2Select 'Code' from the step types
3. 3Choose 'Run Node.js code'
4. 4Replace the default code with the priority filter

Add Step > Slack > Send Direct Message

Connect Slack Account

Add a new Slack step to send the DM to the assignee. Click 'Connect Account' when prompted and authorize Pipedream to access your Slack workspace. Make sure you grant permissions for direct messages and user lookups.

1. 1Click '+' to add another step
2. 2Search for 'Slack' and select it
3. 3Choose 'Send Direct Message' action
4. 4Click 'Connect a new account'
5. 5Authorize Pipedream in the Slack popup

Slack Step > Configure Fields

Configure Assignee DM

Map the ClickUp assignee data to Slack's user field. Use the assignee email from ClickUp webhook data to look up the Slack user. Set your message to include the task name, urgency, and a direct link back to ClickUp.

1. 1Set 'User' field to steps.trigger.event.task.assignees[0].email
2. 2Set 'Text' to your urgent task message template
3. 3Include steps.trigger.event.task.name in the message
4. 4Add steps.trigger.event.task.url for the ClickUp link

Add Step > Code (Node.js)

Add Manager Lookup Step

Add another Code step to find the assignee's manager. This requires either a lookup table in your code or integration with your HR system. For now, create a simple mapping object that matches employee emails to manager emails.

1. 1Add a new Code step after the Slack DM
2. 2Create a manager mapping object
3. 3Look up the assignee's manager using their email
4. 4Export the manager email for the next step

Add Step > Slack > Send Direct Message

Configure Manager DM

Add a second Slack DM step for the manager notification. Use your existing Slack connection and map the manager email from the previous code step. Customize the message to give managers context about the escalation.

1. 1Add another Slack 'Send Direct Message' step
2. 2Use your existing connected account
3. 3Set 'User' field to steps.manager_lookup.manager_email
4. 4Write a manager-specific message template

Deploy > Test Workflow

Test End-to-End Flow

Deploy your workflow and test it with a real priority change in ClickUp. Check that both the assignee and manager receive their respective DMs in Slack. Monitor the workflow execution log to catch any field mapping issues.

1. 1Click 'Deploy' to activate your workflow
2. 2Change another ClickUp task priority to Urgent
3. 3Check Slack for both DM notifications
4. 4Review execution log in Pipedream

Add this code in your priority filter step to handle ClickUp's inconsistent priority formats and add duplicate prevention using workflow storage.

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

export default defineComponent({
  async run({ steps, $ }) {
    const task = steps.trigger.event.task;
    const currentPriority = task.priority;
    
    // Handle different priority formats
    const isUrgent = currentPriority === 'urgent' || 
                     currentPriority === 1 || 
                     currentPriority === '1' ||
                     currentPriority?.name === 'urgent';
    
    if (!isUrgent) {
      $.flow.exit('Task priority is not urgent');
    }
    
    // Prevent duplicate notifications
    const taskId = task.id;
    const lastNotified = await $.service.db.get(`notified_${taskId}`);
    const now = Date.now();
    
    // Don't notify again if we sent alert in last 10 minutes
    if (lastNotified && (now - lastNotified) < 600000) {
      $.flow.exit('Already notified for this task recently');
    }
    
    // Store notification timestamp
    await $.service.db.set(`notified_${taskId}`, now);
    
    return {
      task_id: taskId,
      task_name: task.name,
      assignee_email: task.assignees?.[0]?.email,
      task_url: task.url,
      notified_at: now
    };
  }
});