Automation library · Integrations

Manage custom incident response in PagerDuty and Jira

Started by another system calling it, and works across Jira and Mattermost. 14 steps: a working afternoon to understand properly.

Medium

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

The flow

Starts it 3Service 11

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

  1. 1AckWebhookStarts it
  2. 2ResolveWebhookStarts it
  3. 3WebhookWebhookStarts it
  4. 4PagerDuty1Pager DutyService
  5. 5PagerDuty2Pager DutyService
  6. 6Mattermost1MattermostService
  7. 7Mattermost5MattermostService
  8. 8Jira2JiraService
  9. 9Mattermost2MattermostService
  10. 10Mattermost6MattermostService
  11. 11Mattermost7MattermostService
  12. 12Jira1JiraService
  13. 13Mattermost3MattermostService
  14. 14Mattermost4MattermostService

How it's built

Starts on
Another system calling it
Steps
14
Size
Medium: a working afternoon
Connects to
Jira, Mattermost
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

An n8n account, plus your own Jira and Mattermost 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. 14 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 14 steps before you point it at anything that matters.