Automation library · Data collection

Automate cross-project dependency tracking between Jira

Started by a clock, and works across Gmail, Jira and Slack. 10 steps, 1 branch: a working afternoon to understand properly.

Medium

10 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
3Services it connects to

The flow

Starts it 1Logic 4Service 5

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

  1. 1Trigger (Nightly Run)CronStarts it
  2. 2Fetch Open Jira IssuesJiraService
  3. 3Filter DependenciesIfLogic
  4. 4Extract Dependency DetailsFunctionLogic
  5. 5Compute Impact ScoreFunctionLogic
  6. 6Create Monday.com ItemMonday ComService
  7. 7Create Coordination TaskJiraService
  8. 8Email FormatterCodeLogic
  9. 9Post to SlackSlackService
  10. 10Send Email ReportGmailService

How it's built

Starts on
A clock
Steps
10, with 1 branch
Size
Medium: a working afternoon
Connects to
Gmail, Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail, Jira and Slack accounts. You connect your own accounts after importing it; none are included.

What starts it?

It starts on a clock.

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. 10 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 10 steps before you point it at anything that matters.