Automation library · Money admin

Handle failed Stripe payments with Slack and ClickUp

Started by an event in a connected app, and works across ClickUp, Gmail, Google Sheets, HubSpot and one other. 11 steps, 2 branches: a working afternoon to understand properly.

Medium

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

The flow

Starts it 1Logic 3Service 7

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

  1. 1Stripe TriggerStripe triggerStarts it
  2. 2Parse & Enrich Payment DataCodeLogic
  3. 3High Value CheckIfLogic
  4. 4Slack, Critical AlertSlackService
  5. 5Slack, Standard AlertSlackService
  6. 6ClickUp, Create Recovery TaskClick UpService
  7. 7Retry Count CheckIfLogic
  8. 8Slack, Escalation AlertSlackService
  9. 9Send a messageGmailService
  10. 10Log to Google SheetsGoogle SheetsService
  11. 11Create or update a contactHubspotService

How it's built

Starts on
An event in a connected app
Steps
11, with 2 branches
Size
Medium: a working afternoon
Connects to
ClickUp, Gmail, Google Sheets, HubSpot, Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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

What starts it?

It starts on an event in a connected app.

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.