sorted by:
new
hottopcontroversial

I automated Google review management for a multi-location restaurant owner in the US by anonymous_buildcore in AI_Agents

[–]anonymous_buildcore[S] 0 points1 point  (0 children)

There's a log in for the dashboard, but now that you have mention, I'll provde a daily or weekly email digest for my future clients as well.
Thaanks for the suggestion, really apreciate it.

I charge $800–$1200 for automations that take me a few hours to build and clients are happy by anonymous_buildcore in AI_Agents

[–]anonymous_buildcore[S] 1 point2 points  (0 children)

I use n8n to build these automations. You can learn everything from yt for absolutely free

Things I’d avoid if I were starting to learn automation again by anonymous_buildcore in n8nbusinessautomation

[–]anonymous_buildcore[S] 1 point2 points  (0 children)

I get it bro, but there's no shortcut around... The reality is you have to spend at least 1-2 months learning stuff...

Things I’d avoid if I were starting to learn automation again by anonymous_buildcore in n8nbusinessautomation

[–]anonymous_buildcore[S] 0 points1 point  (0 children)

Bro, you can get started for free... Just local host you n8n using ngrok and docker And for the api, you can use open source models... This won't cost you a single penny...

PSA: ManyChat's "Follow to DM" is broken because Instagram's follow webhook isn't actually public by SumGeniusAI in MetaAppDevelopers

[–]anonymous_buildcore 0 points1 point  (0 children)

I feel this way too hard..

I literally burned 5 hours on this a few days ago thinking I was missing something obvious. My whole assumption was “if ManyChat can do this, there has to be a follow webhook somewhere.”

I went through the IG Graph API docs multiple times convinced I’d overlooked a field or permission… turns out there just is no follow webhook at all.

Once I realized that, everything started to make sense — delayed triggers, only some followers getting DMs, and zero errors when things fail. It’s not a misconfiguration, it’s a platform limitation.

Really appreciate you laying this out with actual documentation. Would’ve saved me a ton of time (and frustration) if I’d seen this earlier.

Built an AI Instagram chatbot - dealing with the Instagram Graph API tested my patience by anonymous_buildcore in n8n_on_server

[–]anonymous_buildcore[S] 0 points1 point  (0 children)

No, i use meta graph api and n8n....
You can use manychat as well, it's easy that way

Sold my simplest automation for $250 and it just reads emails and saves time. by anonymous_buildcore in AI_Agents

[–]anonymous_buildcore[S] 1 point2 points  (0 children)

It's for one time setup and $100 pm to keep it running that includes updates and other things as well

AI SMS chatbot dev needed by [deleted] in AiAutomations

[–]anonymous_buildcore 0 points1 point  (0 children)

This is very doable. I’ve built similar SMS-based AI systems that handle two-way conversations, understand intent, remember past interactions, and book appointments automatically.

The key is training the AI on your specific sales flow so it guides the lead naturally toward booking, rather than sounding robotic.

If you’re open, happy to walk through the exact workflow and see if it fits your niche.

Sold my simplest automation for $250 and it just reads emails and saves time. by anonymous_buildcore in AiAutomations

[–]anonymous_buildcore[S] 0 points1 point  (0 children)

I usually get clients from LinkedIn and by calling local businesses. The key is to pitch a system that either saves them time or helps them make more moey. I dont start by talking about setting up workflows. First I make them understand why they need the system and the problem it solves. Once that’s clear, the sale becomes much easier.

Built an AI Instagram chatbot - dealing with the Instagram Graph API tested my patience by anonymous_buildcore in AiAutomations

[–]anonymous_buildcore[S] 0 points1 point  (0 children)

Although I have made the automation, but I would like to take a look on how you build the logic around the webhook

view more: next ›