## Introduction
Tracking weekly velocity effectively across multiple departments is essential for operations teams in startups aiming to measure productivity and identify bottlenecks. Velocity, typically measured as the amount of work completed in a time period, gives actionable insights into team performance and project progress. However, manually aggregating data across various tools, emails, and spreadsheets can be error-prone and time-consuming.
This guide walks you through automating the tracking of weekly velocity using n8n, an open-source workflow automation tool. We’ll integrate data sources commonly used in operations — such as Jira (for issue tracking), Google Sheets (for data consolidation), and Slack (for notifications) — to build an end-to-end automated velocity report. This automation will benefit operations managers, project managers, and automation engineers by providing timely, reliable, and centralized velocity reports with minimal manual effort.
—
## What Problem Does This Solve?
– **Data silos & manual aggregation:** Pulling velocity information from various departments can involve multiple platforms.
– **Delayed reporting:** Manual processes cause delays, impacting decision making.
– **Error-prone analysis:** Manual data entry risks inconsistencies.
The n8n automation will provide an automated, centralized weekly report of velocity metrics,
streamlining operations and enabling rapid insights.
—
## Tools and Services Integrated
– **n8n:** Core automation platform.
– **Jira Cloud API:** To fetch sprint and issue data.
– **Google Sheets:** To store and track velocity data historically.
– **Slack:** To notify stakeholders with velocity reports.
—
## How the Automation Workflow Works
**Trigger:** Scheduled weekly trigger in n8n (e.g., every Monday morning).
**Process:**
1. Fetch completed issues from Jira for the past week across relevant departments and projects.
2. Calculate velocity metrics – story points or issue counts per team.
3. Append results to a Google Sheet to maintain historical tracking.
4. Format a summary message highlighting velocity comparisons.
5. Post the velocity summary to a dedicated Slack channel.
—
## Detailed Step-by-Step Workflow Breakdown
### Step 1: Setup a Cron Trigger in n8n
– Use the **Cron** node to start the workflow weekly (e.g., Mondays 8:00 AM).
– This keeps velocity tracking consistent with your sprint cycles.
### Step 2: Query Jira Issues Completed in Last Week
– Use the **HTTP Request** node configured for Jira’s REST API.
– Endpoint: `/search`
– JQL filter example:
“`
project IN (OPS, DEV, SALES) AND status = Done AND resolved >= startOfWeek(-1w) AND resolved <= endOfWeek(-1w)
```
- Request will fetch all issues completed last week by relevant departments.
- Parse the response to extract:
- Issue key
- Department label
- Story points or a custom numeric field representing effort
### Step 3: Aggregate Velocity Data by Department
- Use a **Function** node to iterate over the issues and sum story points per department.
- Output should be a JSON object, e.g.,
```json
{ "Operations": 45, "Development": 60, "Sales": 30 }
```
- This gives velocity totals for each team.
### Step 4: Append Velocity Data to Google Sheets
- Use the **Google Sheets Node** configured with your Sheets API credentials.
- Target a sheet with columns: Date, Department, Velocity
- Iterate over the aggregated data to append each department’s weekly velocity with the current date.
### Step 5: Format Slack Message
- Use a **Function** node or **Markdown** formatting to create a clean summary for Slack, e.g.:
```
Weekly Velocity Report - Week of YYYY-MM-DD
*Operations:* 45 points
*Development:* 60 points
*Sales:* 30 points
Keep up the great work! :rocket:
```
### Step 6: Send Velocity Report to Slack
- Use the **Slack** node with a webhook or OAuth authentication.
- Post the formatted message to the designated operations channel.
---
## Common Errors and Tips
- **API Rate Limits:** Jira and Slack APIs have rate limits. Use pagination and retries in n8n to handle large data sets gracefully.
- **Authentication:** Securely store API credentials in n8n credentials manager.
- **Data Quality:** Ensure Jira issues are consistently tagged and story points are accurately filled.
- **Time Zones:** Carefully handle timezone differences when querying Jira date filters.
- **Error Handling:** Use error workflows or catch nodes in n8n to log and alert any API failures.
- **Data Volume:** If dealing with very large projects, limit the query scope or increase runtime intervals.
---
## How to Adapt or Scale This Workflow
- **Add More Departments or Projects:** Adjust JQL queries dynamically or parameterize the departments list.
- **Visualize Data:** Connect Google Sheets with Data Studio or similar BI tools for charts.
- **Real-Time Updates:** Change trigger from weekly Cron to event-based Jira webhooks for instant updates.
- **Include Other Metrics:** Integrate with time-tracking tools or CRM data to enhance velocity insights.
- **Multi-Cloud Storage:** Store backups or raw data in AWS S3 or Google Cloud Storage.
---
## Summary
This n8n automation efficiently consolidates weekly velocity data across departments, transforming manual reporting into an automated, reliable process. Operations teams gain timely insights that drive better decisions and highlight productivity trends. By integrating Jira, Google Sheets, and Slack, your velocity reports become accessible and actionable.
---
## Bonus Tip: Make Your Workflow Modular
Split your workflow into sub-workflows (using n8n’s reusable workflows features) for each major part:
- One for Jira data extraction
- One for data transformation
- One for reporting
This modular approach enhances maintainability and allows easier scaling as your organization grows.