Automation library · Money admin

Handle failed payment renewals with Jira and Slack

Started by another system calling it, and works across Jira and Slack. It hands the judgement calls to OpenAI. 10 steps, 2 branches: a working afternoon to understand properly.

MediumCalls a model: OpenAI

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

The flow

Starts it 1Model 1Logic 5Service 3

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

  1. 1Webhook - Payment FailedWebhookStarts it
  2. 2Validate PayloadFunctionLogic
  3. 3Payload Valid?IfLogic
  4. 4AI AnalysisOpen AiModel
  5. 5Slack Error AlertSlackService
  6. 6Priority SwitchSwitchLogic
  7. 7Set High PrioritySetLogic
  8. 8Set Standard PrioritySetLogic
  9. 9Create Jira Finance TicketJiraService
  10. 10Slack Finance NotificationSlackService

How it's built

Starts on
Another system calling it
Steps
10, with 2 branches
Size
Medium: a working afternoon
Connects to
Jira, Slack
Model
OpenAI

Questions

What does it need to run?

An n8n account, plus your own Jira and Slack accounts, and a key for OpenAI. 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?

Yes. It calls OpenAI. Model calls are billed by the provider, not by n8n.

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.