

How to Generate Daily Standup Issue Summaries with Pipedream
Automatically post daily Slack summaries of each team member's Jira issues including new assignments and approaching deadlines.
Steps and UI details are based on platform versions at time of writing — check each platform for the latest interface.
Jira Cloud for Slack exists as a native integration, but it handles basic notifications but no conditional routing. This guide uses an automation platform for full control. View native option →
Best for
Dev teams running daily standups who want automated issue summaries without manual Jira checking
Not ideal for
Teams that prefer verbal updates or don't use structured sprint planning in Jira
Sync type
scheduledUse case type
reportingReal-World Example
A 12-person engineering team at a SaaS company runs this every morning at 8:30 AM before their 9 AM standup. The Slack summary shows each developer's open tickets, new assignments from yesterday, and anything due within 48 hours. Before automation, the scrum master spent 15 minutes each morning manually checking Jira boards and pinging team members about overdue items.
What Will This Cost?
Drag the slider to your expected monthly volume.
Each platform counts differently — Zapier: 1 task per trigger. Make: 1 operation per module per record. n8n: 1 execution per run.





Prices shown for annual billing. Based on published pricing as of April 2026.
Estimated ROI
1000
min saved/mo
$583
labor value/mo
Free
no platform cost
Based on ~2 min manual effort per operation at $35/hr fully loaded labor cost.
Implementation
Import this workflow directly into Pipedream
Copy the pre-built Pipedream blueprint and paste it straight into Pipedream. All modules, filters, and field mappings are already configured — you just need to connect your accounts.
Before You Start
Make sure you have everything ready.
Field Mapping
Map these fields between your apps.
| Field | API Name | |
|---|---|---|
| Required | ||
| Assignee Display Name | assignee.displayName | |
| Issue Summary | summary | |
| Issue Status | status.name | |
| Issue Key | key | |
4 optional fields▸ show
| Due Date | duedate |
| Priority | priority.name |
| Story Points | customfield_10016 |
| Issue Type | issuetype.name |
Step-by-Step Setup
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 see the workflow builder with an empty trigger step. This creates your automation foundation.
- 1Click Workflows in the left navigation
- 2Click the green New button
- 3Select 'Build a workflow' from the dropdown
- 4Name it 'Daily Standup Jira Summary'
Trigger Step > Built-in > Schedule
Add Schedule Trigger
Click the trigger step and select 'Schedule' from the built-in triggers list. Set it to run daily at your preferred time before standup. Choose timezone carefully since your team needs this before the meeting starts.
- 1Click 'Select a trigger' in the workflow
- 2Choose 'Built-in' from the tabs
- 3Select 'Schedule' from the trigger list
- 4Set frequency to 'Daily' and time to 30 minutes before standup
Add Step > Apps > Jira > Search Issues
Connect Jira Account
Click the + button below the trigger to add a new step. Search for 'Jira' and select it. Choose 'Search Issues' as your action since you need to query multiple tickets. Pipedream will prompt you to connect your Jira instance.
- 1Click the + button below the schedule trigger
- 2Type 'Jira' in the search box
- 3Select 'Jira Software Cloud' from results
- 4Choose 'Search Issues' action
- 5Click 'Connect Account' and enter your Jira credentials
Jira Step > Configuration
Configure Jira Query for Active Issues
In the JQL field, write a query to find all active issues assigned to your team members. Use assignee filters and status exclusions to get current work items. Include story points and due dates in the fields parameter for better summaries.
- 1In the JQL Query field, enter: project = YOUR_PROJECT AND assignee is not EMPTY AND status != Done
- 2Set Max Results to 100
- 3In Fields, add: assignee,summary,status,duedate,customfield_10016
- 4Enable 'Expand' and add 'changelog' to track recent changes
Add Step > Code > Run Node.js
Add Code Step to Process Issues
Add a Node.js code step to transform the Jira response into readable summaries grouped by team member. This step handles date parsing, priority sorting, and formatting for Slack display. You'll group issues by assignee and identify urgent items.
- 1Click + below the Jira step
- 2Select 'Code' from the options
- 3Choose 'Run Node.js' action
- 4Replace the default code with issue processing logic
- 5Test the step to verify grouping works
Add this Node.js code in your processing step to identify newly assigned issues from the past 24 hours and flag them in the summary. Paste this after the basic issue grouping logic.
JavaScript — Code Step// Check for recently assigned issues using changelog▸ Show code
// Check for recently assigned issues using changelog const recentlyAssigned = []; const yesterday = new Date(Date.now() - 24 * 60 * 60 * 1000);
... expand to see full code
// Check for recently assigned issues using changelog
const recentlyAssigned = [];
const yesterday = new Date(Date.now() - 24 * 60 * 60 * 1000);
for (const issue of steps.jira.issues) {
if (issue.changelog && issue.changelog.histories) {
for (const history of issue.changelog.histories) {
const changeDate = new Date(history.created);
if (changeDate > yesterday) {
const assigneeChanges = history.items.filter(item =>
item.field === 'assignee' && item.toString
);
if (assigneeChanges.length > 0) {
recentlyAssigned.push({
key: issue.key,
summary: issue.fields.summary,
newAssignee: issue.fields.assignee.displayName,
changeDate: changeDate
});
}
}
}
}
}
// Add 🆕 emoji to newly assigned items in summary
for (const groupedIssue of groupedByAssignee) {
const newAssignment = recentlyAssigned.find(ra =>
ra.key === groupedIssue.key
);
if (newAssignment) {
groupedIssue.summary = `🆕 ${groupedIssue.summary}`;
}
}Add Step > Apps > Slack > Send Message to Channel
Connect Slack Account
Add another step and select Slack. Choose 'Send Message to Channel' since you want the summary in your standup channel. Connect your Slack workspace and grant the necessary permissions for posting messages.
- 1Click + below the code step
- 2Search for 'Slack' and select it
- 3Choose 'Send Message to Channel' action
- 4Click 'Connect Account' and authorize Pipedream
- 5Select your standup channel from the dropdown
Slack Step > Message Configuration
Format Slack Message Content
In the message field, reference the processed data from your code step. Use Slack's block formatting for better readability. Include team member names as headers and list their issues with priority indicators and due dates.
- 1In the Message field, click 'Use data from previous step'
- 2Select the formatted summary from your code step output
- 3Choose 'mrkdwn' for the message format
- 4Add a header like 'Daily Standup Issues - {{new Date().toDateString()}}'
- 5Preview the message formatting
Workflow Actions > Test
Test the Complete Workflow
Click the Test button to run your entire workflow manually. Check that Jira returns the expected issues, your code processes them correctly, and Slack receives a well-formatted summary. Fix any field mapping or formatting issues before going live.
- 1Click the 'Test' button in the top right of the workflow
- 2Watch each step execute and check for green checkmarks
- 3Verify the Slack message appears in your channel
- 4Check that all team members with active issues are included
- 5Confirm due dates and priorities display correctly
Workflow Actions > Deploy
Deploy the Workflow
Once testing passes, click Deploy to activate the schedule. Pipedream will run this automatically at your configured time each day. The workflow shows as 'Active' with the next scheduled execution time displayed.
- 1Click the 'Deploy' button after successful testing
- 2Confirm the deployment in the popup dialog
- 3Verify the status changes to 'Active'
- 4Note the next scheduled run time
- 5Bookmark the workflow URL for easy access
Scaling Beyond 50+ active issues per team member+ Records
If your volume exceeds 50+ active issues per team member records, apply these adjustments.
Implement Issue Prioritization
Sort by priority and due date, then limit display to top 5 issues per person to keep summaries readable during heavy sprint periods.
Use Slack Thread Replies
Post a condensed summary as the main message and add detailed breakdowns in thread replies to avoid overwhelming the channel.
Add Pagination for Large Teams
Split teams with 15+ members into multiple workflow runs or separate messages to stay within Slack's message length limits.
Cache Issue Data
Store yesterday's results in Pipedream's built-in data store and compare for true delta reporting instead of full dumps.
Going live
Production Checklist
Before you turn this on for real, confirm each item.
Troubleshooting
Common errors and how to fix them.
Frequently Asked Questions
Common questions about this workflow.
Analysis
Use Pipedream for this if your team needs custom issue filtering logic or wants to combine Jira data with other tools like GitHub commits or Slack status updates. The Node.js code steps handle complex date calculations and assignee grouping better than drag-and-drop platforms. Skip Pipedream if you just want basic daily issue lists - Zapier's Jira integration with built-in formatting works fine for simple summaries.
This workflow costs about 2 credits per run on Pipedream's pricing. At daily execution, that's 60 credits monthly. Teams with 50+ active issues might hit API rate limits and need the $19 Professional plan. Zapier's equivalent workflow costs $0 on their free tier but lacks the changelog detection for newly assigned tickets.
Zapier handles Jira authentication more smoothly and has better error recovery for API timeouts. Make offers superior date formatting functions and conditional logic for complex team structures. n8n gives you more granular control over the Slack message formatting with their visual editor. Power Automate integrates better if you're already using Microsoft tools for project management. But Pipedream wins for teams that need custom business logic - like excluding certain projects during crunch time or adding burndown calculations.
You'll hit Jira's REST API rate limits with large backlogs - the search endpoint allows 100 results maximum per call. Custom fields like story points have different IDs across Jira instances, so the workflow breaks when moving between environments. Slack's message length limit is 4000 characters, which gets exceeded quickly with verbose issue summaries during heavy development periods.
Ideas for what to build next
- →Add Epic Progress Tracking — Extend the summary to include epic completion percentages and sprint burndown data for better planning context.
- →Create Weekend Digest Version — Build a Friday afternoon version that summarizes the week's completed work and upcoming Monday priorities.
- →Connect Confluence Updates — Pull in recent documentation changes and spec updates relevant to current sprint work for complete standup prep.
Related guides
How to Share Notion Meeting Notes to Slack with Pipedream
~15 min setup
How to Share Notion Meeting Notes to Slack with Power Automate
~15 min setup
How to Share Notion Meeting Notes to Slack with n8n
~20 min setup
How to Send Notion Meeting Notes to Slack with Zapier
~8 min setup
How to Share Notion Meeting Notes to Slack with Make
~12 min setup
How to Create Notion Tasks from Slack with Pipedream
~15 min setup