Automation library · Documents and files

Convert an XML file to JSON with Slack

Started by another system calling it, and works across Slack. 9 steps, 1 branch: a working afternoon to understand properly.

Medium

9 stepsMedium: a working afternoon
1Branch: places the flow splits
0Loops or waits
1Service it connects to

The flow

Starts it 3Logic 4Service 2

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

  1. 1POSTWebhookStarts it
  2. 2SwitchSwitchLogic
  3. 3Extract From FileExtract From FileService
  4. 4Change FieldSetLogic
  5. 5Already JSONSetLogic
  6. 6Error ResponseRespond To WebhookStarts it
  7. 7XMLXmlLogic
  8. 8Success ResponseRespond To WebhookStarts it
  9. 9Send to Error ChannelSlackService

How it's built

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