Connect and test your Manychat request and reply flows

Before you start

Complete the account, OpenAI, prompt, and automation steps first. Your automation needs a published prompt, response field mappings, and a Responses flow. Keep the correct Manychat account open while configuring it. A flow installed in another account cannot serve as this account's reply flow.

There are two directions to verify. The request flow sends the customer's message to SiloBox using the automation's identity. The Responses flow sends the generated answer back through Manychat, using the mapped response fields. Pointing both settings at the request flow does not complete the return path.

Connect both directions

1. Open the automation's settings in SiloBox and review the available Starter Template and flow instructions. Install the appropriate template in Manychat if needed. Follow the supplied instructions for its fields and request configuration.
2. Copy Automation ID from SiloBox into the intended place in your Manychat request flow. Keep the identifier exactly as copied. The managed SILOBOX_API field is part of the integration credential setup; do not replace its value with an automation ID.
3. Connect Manychat's Default Reply to the SiloBox request flow as described by your setup instructions. Check that the entry point applies to the channel you will use for the test.
4. In SiloBox, refresh fields if the template added any. Review response mappings and choose the Responses flow that actually sends the answer. If entering a flow identifier manually, use the flow's URL or identifier as supported by the picker, not its display name or the Automation ID.
5. Save and enable the automation in SiloBox. Publish the reply logic and any edited template flows in Manychat. Saving one side does not publish changes on the other side.
6. Send a fresh, recognizable question through the connected channel. Allow for any configured processing delay. Open the corresponding conversation in Chats and then check the original channel for the delivered reply.

Check the result

The incoming message should reach the intended automation, the reply should reflect the published prompt, and the answer should return to the same customer conversation. Guided setup can complete when a conversation arrives, so still verify the return path yourself.

If you get stuck

No incoming message points you toward the entry point, request flow, account, or Automation ID. An incoming message with a generation error points toward the prompt or provider. A generated answer without delivery points toward field mappings, Responses flow, account access, or channel restrictions. Use the diagnostic guides below to narrow the problem before repeating the test.

Migrate without mixing routes

Each channel's Default Reply must point to its corresponding Starter Template flow. When replacing a working flow, first route only tagged test contacts to the starter flow and leave everyone else on the existing route. Confirm that untagged contacts still follow the old route before switching customer traffic.

Check where your installed flow gets the Automation ID. If it reads a default-automation Bot Field, update that field and verify that the flow copies it into the automation-ID contact field. With multiple automations, preserve the intended ID for each route. The request channel must match the triggering channel; channels have separate conversations and pause controls.

A mapping preview does not update subscriber fields or run a flow. A live automation test uses the saved published automation, can consume credits, updates real subscriber fields, and sends the configured flow after your confirmation. Use an intended test contact, verify delivered text and buttons, and repeat the test after changing saved settings.

Related guides

• Create an automation
• Automation not replying
• Manychat delivery diagnostics