Automation library · Alerts and monitoring

Monitor partner API usage with Slack and Jira

Started by another system calling it, and works across Gmail, Jira and Slack. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 4Service 6

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

  1. 1Incoming Partner Usage DataWebhookStarts it
  2. 2Validate Partner Usage PayloadCodeLogic
  3. 3Is Usage Payload Valid?IfLogic
  4. 4Calculate API Usage PercentageCodeLogic
  5. 5SwitchSwitchLogic
  6. 6Create Jira Partner Review TicketJiraService
  7. 7Send Slack Partner Usage Alert1SlackService
  8. 8Send a messageGmailService
  9. 9Send Slack Partner Usage AlertSlackService
  10. 10Create Jira Partner Review Ticket1JiraService
  11. 11Send Slack Partner Usage Alert2SlackService

How it's built

Starts on
Another system calling it
Steps
11, with 2 branches
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 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. 11 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 11 steps before you point it at anything that matters.