Automation library · Alerts and monitoring

Automate change request approvals with Monday.com and Jira

Started by a clock, and works across Gmail, Google Sheets, Jira and Slack. 12 steps, 3 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 4Service 7

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Get many itemsMonday ComService
  3. 3Edit FieldsSetLogic
  4. 4Route by Risk LevelIfLogic
  5. 5Notify Stackholder Pending RequestSlackService
  6. 6Route Low Risk by ComponentIfLogic
  7. 7Create an issueJiraService
  8. 8Append or update row in sheetGoogle SheetsService
  9. 9Route High Risk by ComponentIfLogic
  10. 10Notify Stackholder Approval RequestSlackService
  11. 11Resubmission RequestMonday ComService
  12. 12Send a messageGmailService

How it's built

Starts on
A clock
Steps
12, with 3 branches
Size
Medium: a working afternoon
Connects to
Gmail, Google Sheets, Jira, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Gmail, Google Sheets, 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. 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.