Automation library · Alerts and monitoring

Automated press release distribution with OpenAI

Started by another system calling it, and works across Slack. 33 steps, 4 branches, 4 loops or waits: large, and worth reading before you trust it with anything live.

Large

Download free
33 stepsLarge: read it before trusting it with anything live
4Branches: places the flow splits
4Loops or waits
1Service it connects to

The flow

Starts it 2Logic 16Service 15

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

  1. 1Schedule TriggerSchedule triggerStarts it
  2. 2Webhook TriggerWebhookStarts it
  3. 3Error Handler - DBCodeLogic
  4. 4Error Handler - DistributionCodeLogic
  5. 5Send Error AlertSlackService
  6. 6Log to Error DatabaseHttp RequestService
  7. 7Merge TriggersMergeLogic
  8. 8Get Scheduled ReleasesHttp RequestService
  9. 9Process Release BatchesSplit In BatchesLogic
  10. 10Classify Release TypeSwitchLogic
  11. 11Requires Approval?IfLogic
  12. 12Financial Release HandlerCodeLogic
  13. 13Send Approval RequestSlackService
  14. 14Wait for ApprovalWaitLogic
  15. 15GPT-4 Content AnalysisHttp RequestService
  16. 16Check Approval StatusIfLogic
  17. 17Parse GPT-4 ResponseCodeLogic
  18. 18Rejection HandlerHttp RequestService
  19. 19Enrich Media ContactsHttp RequestService
  20. 20A/B Test HeadlinesCodeLogic
  21. 21Check Embargo StatusIfLogic
  22. 22Distribute to JournalistsHttp RequestService
  23. 23Distribute to Wire ServicesHttp RequestService
  24. 24Post to Company NewsroomHttp RequestService
  25. 25Prepare Social Media DistributionSplit In BatchesLogic
  26. 26Wait for Embargo LiftWaitLogic
  27. 27Merge Distribution ResultsMergeLogic
  28. 28Post to Social PlatformHttp RequestService
  29. 29Initialize TrackingHttp RequestService
  30. 30Update CRM RecordsHttp RequestService
  31. 31Schedule Follow-up TrackingCodeLogic
  32. 32Send Success NotificationSlackService
  33. 33Queue Tracking JobsHttp RequestService

How it's built

Starts on
Another system calling it
Steps
33, with 4 branches, 4 loops or waits
Size
Large: read it before trusting it with anything live
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?

Take your time. At 33 steps it is large: read it before trusting it with anything live.

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 33 steps before you point it at anything that matters.