Automation library · Lead generation

Monitor Reddit communities lead generation with Slack

Started by another system calling it, and works across Slack. 33 steps, 4 branches, 1 loop 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
1Loop or waits
1Service it connects to

The flow

Starts it 3Logic 7Service 23

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

  1. 1Daily Content OrchestratorSchedule triggerStarts it
  2. 2Manual Content RequestWebhookStarts it
  3. 3Merge Entry PointsMergeLogic
  4. 4Get Google TrendsHttp RequestService
  5. 5Get Twitter TrendsHttp RequestService
  6. 6Get Reddit Hot TopicsHttp RequestService
  7. 7Analyze Competitor ContentHttp RequestService
  8. 8Aggregate Trend IntelligenceMergeLogic
  9. 9AI Topic Scoring & RankingHttp RequestService
  10. 10Route by Content ScoreSwitchLogic
  11. 11Send to Slack for ApprovalSlackService
  12. 12Wait for ApprovalWaitLogic
  13. 13Check Approval StatusIfLogic
  14. 14Generate Platform-Specific ScriptsHttp RequestService
  15. 15Research Trending HashtagsHttp RequestService
  16. 16Calculate Optimal Post TimesHttp RequestService
  17. 17Add to Publishing QueueHttp RequestService
  18. 18Upload to YouTube (with Retry)Http RequestService
  19. 19YouTube Error HandlerIfLogic
  20. 20Log YouTube FailureHttp RequestService
  21. 21Upload to TikTok (with Retry)Http RequestService
  22. 22TikTok Error HandlerIfLogic
  23. 23Log TikTok FailureHttp RequestService
  24. 24Upload to Instagram (with Retry)Http RequestService
  25. 25Publish Instagram ContainerHttp RequestService
  26. 26Log Instagram FailureHttp RequestService
  27. 27Send Success NotificationSlackService
  28. 28Send Failure AlertSlackService
  29. 29Analytics Collector (Every 4h)Schedule triggerStarts it
  30. 30Get YouTube AnalyticsHttp RequestService
  31. 31Get TikTok AnalyticsHttp RequestService
  32. 32Get Instagram InsightsHttp RequestService
  33. 33Store Performance DataHttp RequestService

How it's built

Starts on
Another system calling it
Steps
33, with 4 branches, 1 loop 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.