Log every new Azure DevOps work item to Google Sheets
Automatically add every new Azure DevOps work item to a Google Sheets tracker so your team can filter, sort, and report without opening Azure DevOps.
Azure DevOps
Google SheetsOperationsEngineeringData SyncRun this as a deterministic code workflow triggered by an Azure DevOps webhook. Subscribe to the Azure DevOps "Work item created" service hook (event type workitem.created) so the workflow fires the moment a new work item is opened in my project.
The webhook payload sometimes arrives thin, carrying little more than the work item id and revision. Before writing anything, check whether the payload already includes the fields I need. If any are missing, call Azure DevOps Get Work Item with the id from the webhook to fetch the full work item and its fields.
Then append one row to my Google Sheets tracker using Append Values, appending after the last row of the existing table so nothing is overwritten. Map the fields to fixed columns in this exact order: work item id, work item type (System.WorkItemType), title (System.Title), assignee (System.AssignedTo display name), state (System.State), priority (Microsoft.VSTS.Common.Priority), area path (System.AreaPath), and created date (System.CreatedDate).
The field-to-column mapping is fixed, so run this with no reasoning or judgement between steps. If a field is empty (for example an unassigned item or an item with no priority), write a blank cell rather than skipping the column so every row keeps the same shape. Format the created date as a readable date and keep exactly one row per work item. This adds a row only when an item is created; it does not update existing rows when items change later.
Additional information
What does this prompt do?
- Watches your Azure DevOps project and captures every work item the moment it's created.
- Adds a new row to your Google Sheets tracker with the item's id, type, title, assignee, state, priority, area path, and created date.
- Fills in any missing details automatically before writing, so every row comes out complete.
- Builds a live, filterable log your whole team can use for backlog and throughput reporting.
What do I need to use this?
- An Azure DevOps account with a project you can add a service hook to.
- A Google account with a Sheets spreadsheet set up as your tracker.
- A header row in the sheet naming the columns you want to capture (recommended so rows line up cleanly).
How can I customize it?
- Choose which columns to capture and the order they appear in.
- Point it at a different spreadsheet or tab for each team or project.
- Filter to specific work item types, like bugs or user stories, if you only want a subset.
FAQs
Do I need to be technical to set this up?
Will this slow down my team in Azure DevOps?
What if a work item is missing some details?
Does it update the spreadsheet if a work item changes later?
Can I use this across more than one project?
Related templates
Every weekday at 7am, your active courses are checked for missing work, silent logins, and slipping grades, with a ranked list sent to your advising channel.
Every Monday at 8am, see exactly which assignments have work waiting, sorted worst first, posted to Slack and logged to a spreadsheet.
Every weekday morning your advising team gets a ranked list of students slipping behind in each course, plus a tracking log that shows whether outreach worked.
Every Monday at 8am, count last week's tickets and SLA results, add one row to a tracking sheet, and post the headlines to Slack.
Every weekday, each person gets one private nudge listing only their own undocumented card spend, plus an aging report for finance.
Every Monday, find the people who never turned on two-factor or never accepted their invite, message them in Slack, and track both numbers.
Give your team a live view of the backlog.
Turn every new Azure DevOps work item into a filterable spreadsheet row automatically, with no manual updates required.