Automation library · Data collection

Sync Azure DevOps work items to GitHub issues

Started by another system calling it, and works across GitHub and Google Sheets. 12 steps: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
0Branches: places the flow splits
0Loops or waits
2Services it connects to

The flow

Starts it 2Logic 3Service 7

The steps in the order they run, from what starts it.

  1. 1Webhook1WebhookStarts it
  2. 2Webhook2WebhookStarts it
  3. 3Filter Story DataCodeLogic
  4. 4Filter Task DataCodeLogic
  5. 5Create Github IssueGithubService
  6. 6Google Sheets1Google SheetsService
  7. 7HTTP Request1Http RequestService
  8. 8GitHub2GithubService
  9. 9Code2CodeLogic
  10. 10GitHub1GithubService
  11. 11HTTP Request2Http RequestService
  12. 12Google SheetsGoogle SheetsService

How it's built

Starts on
Another system calling it
Steps
12
Size
Medium: a working afternoon
Connects to
GitHub, Google Sheets
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own GitHub and Google Sheets accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on another system calling it.

Does it use AI?

No. Every step is fixed logic or a call to a service, so it does the same thing every time.

How long does it take to set up?

Plan an afternoon. 12 steps is enough that you should read each one before running it.

How do I import it?

Copy the workflow, open a new workflow in n8n and paste. The steps appear on the canvas, ready for your own accounts.

Before you run it

Nothing here has been tested by us. It is somebody's working automation, read and described from its own steps. Treat the connections it wants as a list of accounts it will touch, and read the 12 steps before you point it at anything that matters.