Skip to main content

Well is there

Hey everyone,

I'm running a ManyChat automation, and I’m hitting Meta’s 250 messages per day limit. The challenge is that I can’t track exactly which messages were successfully sent and which weren’t. Since the automation is still running, I have no clear way to determine who actually received the message and who didn’t.

The NEXT STEP of the message is just running no metter the message wsa sent or not.

What I'm Trying to Achieve

  1. Track message delivery – Identify which messages were sent successfully and which were blocked due to the daily limit.
  2. Run follow-up actions ONLY for successfully sent messages – Avoid triggering actions for users who never received the initial message.
  3. Handle messages that exceed the daily limit – Make sure users who didn’t get the message today will be prioritized for the next day.

Challenges

🚨 Meta limits messages per day, so some messages may not be sent at all.
🔄 The automation keeps running, making real-time tracking difficult.
❌ There’s no built-in way to see a per-user delivery status inside ManyChat.

Questions for the Community

✅ Is there a way to log the status of each message in ManyChat by API calls?
✅ Can we trigger actions only if a message was actually sent?
✅ What’s the best method to queue messages for the next day if the limit was reached?

Would love to hear any solutions or workarounds. Thanks in advance! 🚀

any option to know 

If I were in your place, I would try the following approach:

I would create a numeric "Bot Field" to store the number of messages sent.

I would also create a TAG to mark the leads that have already gone through the flow and, consequently, received the message.

In the flow, I would add the following steps:

1- Check if the Bot Field has a numeric value ≥ 250. If yes, stop the flow. If not, proceed.

2- Add the TAG to the contact so that when starting the campaign, those with this TAG are excluded, as they have already received the message in previous days.

3- Increase the value in the Bot Field by 1.

You would also need to reset the Bot Field value daily, either by creating another specific flow for this or doing it manually.

I believe that this method, or a slight adaptation of it, would work.

Reply


Community Terms & ConditionsCookie settings