Fixing problems with the ManyChat connection

Every MemberArea step answers in a full sentence, so the message in your flow already names the problem. This page adds what to do about it.

"This ManyChat connection is not signed in to a MemberArea"

The API key in the app settings is not valid any more. Either it was rotated or deleted in your memberarea, or it was pasted with a stray space.

Open Settings, then API, create a fresh key, and paste it into the app settings in ManyChat. Nothing in your flows needs rebuilding.

"The API is not included in this MemberArea's plan"

The API is part of every paid plan, and it is switched on during the free trial. An expired trial and the Free (Legacy) plan have no API, so every step answers with this message and no event starts a flow. The ManyChat panel in your memberarea says the same and offers Change plan. Picking any paid plan makes steps and events work again straight away.

"This ManyChat connection is not allowed to run this step"

The key works, but it does not carry the permission this particular step needs. This is why one step in a flow can work while the next one refuses: Add tag and Grant access ask for different permissions.

The message asks you to reconnect the app, which is the general advice ManyChat shows. In your memberarea the fix is more specific: create a key that carries every permission the app uses, or leave a key at full access, and paste it in again. The permissions the app needs are listed in Connecting ManyChat to your memberarea.

The item a step points to is gone or not ready

A step remembers the item you picked in its dropdown. If that item was deleted afterwards, the step names it, for example "This product does not exist in your MemberArea any more. Please pick it again in your flow." The same sentence exists for courses, events, groups, tags, member fields and automations. Open the step and choose the item again from the dropdown.

Some items still exist but cannot be used right now. The step then says why:

• "This product is still a draft in your MemberArea, so no access was granted." Publish the product, or pick another one.
• "This product cannot be bought right now because it is inactive or has no active price." Check the product and its prices.
• "This course is not published yet, so nobody can be enrolled." Publish the course first.
• "This event is sold as a product in your MemberArea, so it cannot be booked from a chat flow without a purchase." Send the checkout link instead.
• "This person cannot see this event, because it belongs to a community area they are not part of." Add the person to the area first.
• "Registration for this event has closed." Or the closing text you wrote for the event, if it has one.

"Too many requests reached this MemberArea"

A flow is calling more often than your memberarea allows. Two limits sit behind this message: a per minute one that catches a short burst, and a daily one that caps the total number of calls. This is normal during a viral campaign and it is not an error in your setup. The answer carries a Retry-After value that says how many seconds to wait before the step is called again. A few seconds means the per minute limit and the flow can simply try again. Several hours means the daily limit, and then only sending less helps: not every branch needs to write to your memberarea.

"Something went wrong inside this MemberArea"

Something failed on our side and we already know about it. Let the step run again a few minutes later. If it keeps happening, write to support@memberarea.io and name the step and roughly the time.

A dropdown stays empty

The lists only offer what a step can really use. An empty list says which one it is:

• Product and Or bundle offer active products and bundles, no drafts.
• Course offers published courses.
• Group offers your own groups. Groups your memberarea keeps up to date by itself are not offered.
• Member field offers every field type except multiple choice, image, file, audio and video.
• Event offers recurring events and events that have not ended yet.
• Automation offers automations that are published and switched on.

Create or publish the item, then reopen the dropdown. Nothing needs reconnecting.

Every field is suddenly mandatory

If a step refuses to save and complains about missing fields, the app version in ManyChat is out of date. Reinstall the app from the install link and rebuild that one step. Optional fields such as Or bundle carry a default in the current version, so they can stay empty.

In Grant access and Revoke access you pick either a Product or a bundle under Or bundle. When both are filled, the product wins.

An event never starts a flow

Three different things can be missing here.

The page is not connected

Steps inside a flow work with the address and API key alone, but events need the App Key of the page on top. Open Settings, then Integrations, and open ManyChat: if no page is listed under ManyChat app connections, no event can reach ManyChat yet. Paste the App Key and press Connect page.

The plan has no API

On an expired trial or the Free (Legacy) plan, events do not start flows even when the page shows as connected. The panel says "Your plan does not include the API." and offers Change plan.

The person is unknown to ManyChat

An event can only start a flow for a subscriber of that page. If the buyer never wrote to your page, there is nobody to message, and the panel records that under Last problem. Build the link inside a chat first, with Save contact in MemberArea or Create member, and every later event finds them.

Checking a connection from your side

In your memberarea, open Settings, then Integrations, and open ManyChat. The panel lists the connected pages with their state, when a flow was last started and what the last problem was. It covers the events your memberarea sends to ManyChat. A step that fails inside a flow shows its message in ManyChat, not here.