**To test an automation Flow before activating it for real customers in Papo (https://papo.global/), you can temporarily activate the Flow, manually enroll a test contact, and review the execution history to validate the complete journey. This process lets you debug the logic, verify actions, and fix issues without affecting any real lead or customer.**

Before releasing a Flow to the public, it is essential to ensure that every step — messages, questions, conditions, and actions — behaves exactly as planned. Building the visual flow is the first step; proving it works in practice is the next. Fortunately, Papo provides the resources needed for complete validation with a single control contact.

## Test process overview

| Step | Action | What to watch |
| :--- | :--- | :--- |
| 1. Build the Flow | Design the flow with action, question, and condition nodes, and save it. | The visual logic is correct, with no loose nodes. |
| 2. Temporarily activate | Change the Flow status to **Active** in the Flows module. | Only active Flows process contacts. |
| 3. Enroll test contact | In the CRM, open a test contact and choose to manually enroll it in the active Flow. | The contact should be a test profile, not a real customer. |
| 4. Monitor execution | Go to the Flow execution history and see each node the contact went through. | Conditions, captured answers, and executed actions. |
| 5. Fix and repeat | If you find issues, deactivate the Flow, adjust the logic, and repeat the test. | Until the result is as expected. |

## How the test works, step by step

### 1. Build the Flow and save the draft

Use the visual editor of the **Flows / Chatbot** module to build the journey. Add the necessary action nodes (send message, ask a question, add tag, etc.), define branches with conditions, and make sure there are no dead ends. When you finish, save the Flow — it will remain inactive until you decide to activate it.

### 2. Activate the Flow for testing

An inactive Flow does not receive contacts or execute actions. Therefore, to perform the test, you need to change the status to **Active**. This activation is temporary while you validate operation; you can deactivate the Flow again if you find problems and then reactivate it when it is ready for production.

### 3. Create or choose a test contact

To isolate the test from the real environment, use a contact created specifically for this purpose. Go to **CRM**, add a new contact with a fictitious name and phone number, for example, “Test Flow” with a number you control (such as your own personal WhatsApp, if you want to receive the messages). This contact will be the automation’s test subject.

### 4. Manually enroll the contact in the Flow

With the Flow active, open the test contact’s profile in the CRM. Find the option to enroll it in a Flow and select the automation you want to test. This manual enrollment inserts the contact at the beginning of the journey, exactly as would happen with a real lead, but in a controlled way.

### 5. Monitor the execution history

Immediately after enrollment, Papo begins processing the contact. Go to the same Flow, look for the **execution history** section, and find your test contact’s entry. When you open the details, you will see the exact sequence of nodes traversed — each message sent, each question answered, and each condition evaluated. Compare this real path with what you designed in the editor.

### 6. Analyze the results and iterate

If the contact stopped at a condition node where it should not have stopped, check whether the captured answer was recognized correctly (pay attention to variations such as “yes” and “Yes”). If an action such as **Add Tag** or **Update Contact** was not executed, confirm in the history whether the node was reached. With the diagnosis in hand, deactivate the Flow, make the necessary adjustments, activate it again, and repeat the test with the same contact (or a new one) until everything flows perfectly.

## Who this process is for

- **Administrators creating their first automation** and want to avoid surprises with real leads.
- **Marketing and sales teams** that build qualification, survey, or welcome Flows and need to guarantee the customer experience.
- **Any user who customizes a Flow from the Library** and wants to validate the adaptations before releasing it to the public.

## Frequently asked questions

### Can I test a Flow without activating it?

No. Only Flows with the status **Active** can receive and process contacts. To test the logic, you need to temporarily activate the Flow. After testing, you can deactivate it without problems.

### Can my test Flow interfere with real customers?

No, as long as you use an exclusive test contact. Until you enroll any real customer in the Flow — whether manually, in bulk, or through another automation — interactions remain restricted to the control profile.

### What should I do if the test contact does not advance past a node?

Check the execution history: the stopping node indicates where the logic failed. It is usually a condition that did not recognize the contact’s answer (for example, the question expects “Yes” and the contact typed lowercase “yes”) or a dead-end path. Fix the condition or add a default route to capture unexpected answers.

### Do I need to create a new contact for each test?

It is not mandatory. You can reuse the same test contact multiple times. Just enroll it again in the Flow (after restarting or adjusting) and monitor the new history. If you prefer to keep separate records, create a new contact for each test round.

### After testing, can I deactivate the Flow and reactivate it normally?

Yes. You can switch the status between Active and Inactive at any time. After final adjustments, keep the Flow active to start receiving enrollments from real contacts.

### Does the execution history show the answers the contact sent?

Yes. When inspecting an **Ask a Question** node in the history, you can view the exact input provided by the contact. This is essential to validate whether the correct branch was followed.

## See also

- [How to debug an automation Flow that is not working](/hc/papo/articles/how-to-debug-an-automation-flow-that-isnt-working)
- [What is the difference between Flow and Sequence in Papo?](/hc/papo/articles/difference-between-flow-and-sequence-in-papo)

---

**[Start testing for free now →](https://papo.global/?utm_source=helpcenter&utm_medium=article&utm_campaign=how-to-test-an-automation-flow-before-activating-it&utm_content=en)**

The first user is free and lets you validate automation Flows with no commitment, even before inviting your team.