🤖 Creating campaign flows in Atom

In Atom, flows allow you to automate interactions and processes within the platform to enhance your campaigns. You can approach this configuration in two ways: creating from scratch for full control, or using predefined flows to speed up implementation.

🛠️ 1. Creating flows from scratch

This option is ideal for building processes tailored to your business.

Go to the Create Flows area and select "Flows from scratch".
Choose the WhatsApp number for the flow and click Continue.
On the creation screen, select your trigger in the right panel:
- Template: Use a previously approved WhatsApp template to start the flow.
- Webhook: Set up an event that connects your server application with the client.
Flowbuilder Tools:
- Section 1: Do, undo, zoom slider, and export image buttons.
- Section 2: Keyboard shortcuts and flow navigation mini map.
- Section 3: Error indicator, save button, flow simulator, and publish button.

⚡ 2. Integration and creation with Webhooks

Webhooks link an event on your server (such as a CRM or ERP) so that Atom sends a message to the client.

Base configuration: Choose Webhook as the trigger, connect it to a template component, and add the necessary nodes (such as "Evaluate Response").
Input parameters: Every webhook in Atom requires the "phone" parameter (number entered with the + sign and area code, no spaces or dashes). If your template has custom variables, these also become mandatory.
Get the JSON data: Before publishing, double-click the Webhook component and select "Show POST request" to copy the parameters you will need in your external system.

🧪 Test your flow with Postman

Before activating your campaign, simulate the execution:

Copy your flow URL from the Webhooks submodule.
In Postman, set the method to POST.
In the Headers, enter:
- Content-Type: application/json
- Authorization: Bearer [Your_API_Token] (Get your token in My Company > Security Settings).
In the Body, select raw and insert the parameters in JSON format. Example:

JSON
```
{   
"phone": "+5795755112756",
"client_name": "Martin Lopez"
}
```

🚨 ATOM Webhook Response Codes

Scenario	Response Code	Response Body
Successful send	200 - Ok	`{"message":"Webhook ejecutado satisfactoriamente"}`
Non-existent token	401 - Unauthorized	`No authorization token found.`
Incorrect token	404 - Not Found	`Cannot find a company with uuidToken = xxxxxxx`
Required parameter	500 - Internal Server Error	`{"message": "El parametro xxxx es requerido","hasErrors": true}`
Active flow simulation	500 - Internal Server Error	`{"message":"El contacto se encuentra simulando un flujo.","hasErrors":true}`

🔄 3. Returning data using the "HTTP Request" component

If you need Atom to send captured client responses back to your system:

Insert the "HTTP Request" component and choose the POST method.
Insert your receiving server's URL.
Activate the Body button to insert fields in JSON format. Use the / (slash) key to expand and insert dynamic Atom variables (such as recent responses).

📋 4. Creation from predefined flows

To gain speed, use the platform's templates:

Select "Predefined Flows".
Filter by industry and choose the use case (e.g. "Appointment Confirmation" or "Vehicle Interest"). You can preview the design with the eye icon.
Click CREATE, assign the WhatsApp number, and rename the flow.
Note: If the flow requires templates or fields you don't have, Atom will show you an alert to create them automatically.

⚠️ Critical Considerations

Lifespans: All flows have a duration defined by the response evaluator times, plus 5 additional minutes. Actions outside that range will not execute.
Mandatory Closures: Every execution branch must end forcibly in a Flow End component or in an Assignment (to a group or agent).
Tokens: If you regenerate an API Token for security, you must update it in all active webhooks of your CRM/ERP.

Connect and automate without limits! 🚀

Mastering flows and webhooks in Atom allows you to create seamless user experiences, from a simple notification to complex two-way integrations with your CRM. Always remember to test in Postman, carefully review your 200 OK response codes, and make sure no branch of your flow is left without a defined closure. Let's add intelligence to your campaigns! ✅