How to Send Jira Updates to Slack Channels with Pipedream

Workflows > New

Create new Pipedream workflow

Go to pipedream.com and click Workflows in the left sidebar. Click the green New button in the top right corner. You'll land on the workflow builder with an empty trigger step. Click the trigger step to configure it.

1. 1Click Workflows in the left navigation
2. 2Click the green New button
3. 3Click the empty trigger step labeled 'Select a trigger'

Trigger > Search Apps > Jira

Add Jira webhook source

Search for 'Jira' in the app search box. Select 'Jira (Developer)' from the results. Choose 'New Issue Event (Instant)' as your trigger. This creates a webhook endpoint that Jira will call when issues change.

1. 1Type 'Jira' in the search box
2. 2Click 'Jira (Developer)' from the dropdown
3. 3Select 'New Issue Event (Instant)' trigger
4. 4Click Continue

Trigger Configuration > Connect Account

Connect Jira account

Click 'Connect Account' to authenticate with Jira. Enter your Jira domain (yourcompany.atlassian.net), email, and API token. Generate an API token from Jira Account Settings > Security > API Tokens if you don't have one.

1. 1Click the 'Connect Account' button
2. 2Enter your Jira domain without https://
3. 3Enter your Atlassian email address
4. 4Paste your Jira API token
5. 5Click Save

Jira Settings > System > Webhooks

Configure Jira webhook in Atlassian

Switch to your Jira instance. Go to Settings (gear icon) > System > Webhooks. Click Create a WebHook. Paste the Pipedream webhook URL and select which events to track - typically Issue Updated and Issue Assigned.

1. 1Click the Settings gear icon in Jira
2. 2Navigate to System > Webhooks
3. 3Click 'Create a WebHook'
4. 4Paste the Pipedream webhook URL
5. 5Check 'Issue Updated' and 'Issue Assigned' events
6. 6Click Create

Pipedream Trigger > Test

Test the Jira trigger

Return to Pipedream and click 'Test' on your trigger step. Go to Jira and update any ticket - change status, add a comment, or reassign it. Within 30 seconds, you should see the webhook data appear in Pipedream's test section.

1. 1Click 'Test' in the Pipedream trigger step
2. 2Switch to Jira and edit any ticket
3. 3Change the status or add a comment
4. 4Wait 30 seconds and refresh Pipedream
5. 5Confirm webhook data appears

Workflow > Add Step > Slack

Add Slack step

Click the + button below your trigger to add a new step. Search for 'Slack' and select it. Choose 'Send Message to Channel' as the action. This will post your formatted Jira updates directly to the specified channel.

1. 1Click the + button below the trigger step
2. 2Search for 'Slack' in the app list
3. 3Select 'Slack' from the results
4. 4Choose 'Send Message to Channel'
5. 5Click Continue

Slack Step > Connect Account

Connect Slack workspace

Click 'Connect Account' in the Slack step. Authorize Pipedream to access your Slack workspace. You'll need permissions to post in the target channels. Select your workspace from the OAuth dialog and approve the permissions.

1. 1Click 'Connect Account' in the Slack configuration
2. 2Select your Slack workspace from the list
3. 3Click 'Allow' to grant permissions
4. 4Verify the connection shows as 'Connected'

Slack Configuration > Channel & Message

Configure channel and message

Select your target channel from the Channel dropdown. In the Text field, reference Jira data using {{ }} syntax. Use {{steps.trigger.event.issue.key}} for ticket number and {{steps.trigger.event.issue.fields.summary}} for title.

1. 1Select target channel from the Channel dropdown
2. 2Click in the Text field
3. 3Add message template with Jira field references
4. 4Include ticket URL and status information

Workflow > Add Step > Node.js

Add filtering logic

Click + to add a Node.js code step before Slack. Add conditional logic to filter which updates trigger notifications. Check for specific status changes or priority levels to reduce channel noise. Use $.flow.exit() to stop execution for unwanted events.

1. 1Click + between trigger and Slack steps
2. 2Select 'Run Node.js Code'
3. 3Add filtering conditions in the code editor
4. 4Test with different Jira update types

Workflow > Test

Test complete workflow

Click 'Test' on the entire workflow. Make changes to Jira tickets that match your filter criteria. Verify messages appear in your target Slack channel with proper formatting. Check that filtered events don't trigger notifications.

1. 1Click 'Test' at the workflow level
2. 2Update Jira tickets with different changes
3. 3Verify Slack messages appear correctly
4. 4Confirm filtering works as expected
5. 5Click 'Deploy' when satisfied

This code step filters Jira events to only notify on status changes and high-priority updates. Paste it between your trigger and Slack steps to reduce channel noise.

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

export default defineComponent({
  async run({ steps, $ }) {
    const event = steps.trigger.event;
    const changelog = event.changelog;
    
    // Only process status changes or priority updates
    const relevantChanges = changelog.items.filter(item => 
      ['status', 'priority', 'assignee'].includes(item.field)
    );
    
    if (relevantChanges.length === 0) {
      console.log('No relevant changes detected, skipping notification');
      $.flow.exit('Filtered out: no status/priority/assignee changes');
    }
    
    // Skip automated system updates
    if (event.user.accountType === 'atlassian') {
      $.flow.exit('Filtered out: automated system update');
    }
    
    // Format the change message
    const statusChange = relevantChanges.find(item => item.field === 'status');
    const priorityChange = relevantChanges.find(item => item.field === 'priority');
    
    let changeText = '';
    if (statusChange) {
      changeText += `${statusChange.fromString} → ${statusChange.toString}`;
    }
    if (priorityChange) {
      changeText += ` (Priority: ${priorityChange.toString})`;
    }
    
    return {
      shouldNotify: true,
      changeDescription: changeText,
      issueKey: event.issue.key,
      issueSummary: event.issue.fields.summary,
      assignee: event.issue.fields.assignee?.displayName || 'Unassigned'
    };
  }
});