Skip to main content
Question

Has anyone experienced this with the "New Instagram Follower" automation?

  • July 7, 2026
  • 1 comment
  • 8 views
Pauleth Bravo

Hi everyone,

I'm having an issue with the "New Instagram Follower" automation on Instagram.

Here are the details:

  • My Instagram account is connected correctly.
  • All permissions have been refreshed.
  • The automation was enabled before I launched my campaign.
  • The trigger is "When someone new follows you."
  • My account is a Creator account.
  • I'm using a Profile Visits campaign to gain followers.

According to Instagram Insights, I gained over 1,000 new followers this month, but ManyChat has only triggered the automation around 36 times.

Has anyone experienced the same issue?

Is this a limitation of the Meta API, or is there something I should check in my ManyChat or Instagram settings?

I'd really appreciate any advice or solutions. Thanks!

    1 reply

    SumGenius
    Forum|alt.badge.img
    • SumGenius
    • Smooth talker
    • July 7, 2026

    You can stop checking your settings. Everything you listed (connected, permissions refreshed, automation enabled first, Creator account) is correct. This is a Meta limitation, not your config.

    Two things are behind it:

    1. The "New Instagram Follower" trigger is a beta feature on Meta's side. It fires inconsistently by nature, so only getting a fraction of your follows is expected, not a bug you can fix.

    2. This is the main one: if a new follower already received a follow-to-DM from any other account in roughly the past week, Meta blocks a second one from going out. Followers you gain from a Profile Visits campaign tend to be very active accounts that follow a lot of pages, so a big chunk of them already got a follow-to-DM from someone else recently and get skipped.

    That second rule is almost certainly why you're at ~36 out of 1,000+. It's firing about as much as Meta currently allows for that audience. The low number is the limitation, not your setup. I went deep on this exact issue and wrote up the full breakdown, happy to send it over if you DM me.

    Community Terms & ConditionsAccessibility statement