Find Reddit posts asking for automation help.
Spot Reddit posts where teams ask how to automate manual work, replace spreadsheets, connect tools, or choose workflow automation software.
The useful threads have a buying situation behind the wording.
Automation requests are useful because the buyer usually describes the broken process before they know the exact product category. The post often includes the tools involved, the handoff that fails, and the reason manual work is no longer acceptable.
They ask how to connect tools, remove repeated manual work, or stop using spreadsheets as a process layer.
They describe a current stack like Airtable, Zapier, Slack, HubSpot, Notion, Google Sheets, or internal scripts.
They often ask whether to use no-code automation, custom scripts, an agency, or a full workflow tool.
The best posts name the trigger, destination, failure point, and business impact.
Separate real buyer intent from Reddit noise.
Prioritize posts with repeated manual work and a clear consequence.
Check whether the buyer owns the workflow or is only exploring ideas.
Score higher when multiple tools, teammates, customers, or revenue processes are involved.
Skip vague productivity questions with no process, owner, or pain.
Examples of posts worth acting on.
“We still copy trial signups from Stripe into HubSpot and Slack. What is the safest way to automate this?”
“What are some cool automation tools?”
“Our agency onboarding is a mess across forms, Notion, and email. Has anyone automated client intake without Zapier breaking?”
“Is automation worth learning?”
“Need a way to route support tickets from Intercom into Jira only when engineering needs to see them.”
“What does workflow automation mean?”
Monitor the language around the buying moment.
Manual pain
Manual pain shows the process already exists and has become expensive enough to fix.
Automation request
Automation language means the buyer is past awareness and looking for a practical path.
Tool-stack clues
Named tools reveal implementation fit, integration depth, and likely buyer constraints.
Subreddit and category fit matters.
No-code, automation, operations, RevOps, and founder communities
SaaS, agency, and small business communities where messy processes show up
Support, sales, data, ecommerce, and marketing communities with repeated handoffs
Developer communities when automation pain is technical enough for scripts or APIs
Be useful before you mention yourself.
Start by naming the safest architecture or tradeoff, not by selling a tool.
Ask for missing context when the trigger, destination, or failure condition is unclear.
Mention your product or service only when it directly fits the workflow described.
Warn about brittle automation when the buyer is trying to patch a process that needs review first.
Turn these posts into a repeatable review workflow.
Monitor automation and manual-workflow phrases across communities where your buyers ask for help.
Score posts by process pain, tool-stack fit, urgency, and reply risk.
Keep the original workflow context attached before routing the lead to sales or services.
Draft replies that answer the process question before introducing your offer.
Keep exploring buyer intent.
Common questions.
Are automation-help posts good leads?
They can be strong when the post includes a real workflow, named tools, repeated manual work, and a consequence like missed follow-up, wasted hours, or customer impact.
What automation posts should I skip?
Skip broad productivity questions, beginner curiosity, and posts where the author has no specific workflow or business reason to change.
How should automation vendors reply?
Explain the workflow tradeoff first. A useful reply might compare no-code, custom scripts, and managed software before mentioning your own solution.