Automation library · Data collection

Export Jamf policies to Slack as CSV for instant auditing

Started by another system calling it, and works across Slack. 12 steps, 1 loop or waits: a working afternoon to understand properly.

Medium

12 stepsMedium: a working afternoon
0Branches: places the flow splits
1Loop or waits
1Service it connects to

The flow

Starts it 2Logic 6Service 4

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

  1. 1ClickManual triggerStarts it
  2. 2Webhook-policiesWebhookStarts it
  3. 3Jamf ServerSetLogic
  4. 4Get Policies idsHttp RequestService
  5. 5XML-JSONXmlLogic
  6. 6Split Policies IDSplit OutLogic
  7. 7Loop Over ItemsSplit In BatchesLogic
  8. 8XMLXmlLogic
  9. 9Get Policy:idHttp RequestService
  10. 10Set-fieldsSetLogic
  11. 11ConvertConvert To FileService
  12. 12Post to SlackSlackService

How it's built

Starts on
Another system calling it
Steps
12, 1 loop or waits
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. 12 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 12 steps before you point it at anything that matters.