Automation library · Alerts and monitoring

CSV to JSON converter with Slack

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

Medium

13 stepsMedium: a working afternoon
2Branches: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 4Logic 6Service 3

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

  1. 1Send Raw CSVHttp RequestService
  2. 2POSTWebhookStarts it
  3. 3SwitchSwitchLogic
  4. 4Extract From FileExtract From FileService
  5. 5Change FieldSetLogic
  6. 6Error ResponseRespond To WebhookStarts it
  7. 7AggregateAggregateLogic
  8. 8Convert Raw Text To CSVCodeLogic
  9. 9Send to Error ChannelSlackService
  10. 10Success ResponseRespond To WebhookStarts it
  11. 11Check if ValueIfLogic
  12. 12Aggregate1AggregateLogic
  13. 13Success Response2Respond To WebhookStarts it

How it's built

Starts on
Another system calling it
Steps
13, with 2 branches
Size
Medium: a working afternoon
Connects to
Slack
Model
None. This is plumbing, not judgement

Questions

What does it need to run?

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