🧠 Introduction

HTTP requests allow you to connect your bot with external services like CRMs, internal systems, or platforms like Zapier. However, poor configuration can cause this data to never reach its destination… and without warning!

This article will help you identify and resolve the most common errors when using this component.

🧨 Frequent errors when using the HTTP component

🔗 Double URL inclusion: Occurs when the address is concatenated twice (e.g. https://https://hooks.zapier.../). How to prevent it: Check that the URL doesn't have duplications when copying/pasting. It should always start with a single https://.
❌ Invalid or incorrectly copied URL: The flow doesn't send anything, not even show an error. How to prevent it: Paste the URL in your browser to validate the format or use tools like Postman.
🛑 HTTP component doesn't activate: The user never reaches that part of the flow because the previous conditions aren't met. How to prevent it: Check the logic of the flow design and simulate a conversation to ensure the route activates.
🔇 Silent error in Zapier: Zapier doesn't register the entry, but also doesn't throw a visible error in Atom. How to prevent it: Check if the webhook is properly configured by reviewing the requests received in Zapier's task history.

🧪 What to do if the information didn't reach Zapier?

If you're unsure why the connection failed, follow these steps:

📤 Review the URL in Atom: Verify that it only has a valid address and avoid accidental concatenations.
🧪 Simulate the flow: From Atom, test the flow ensuring that the condition that activates the HTTP request is actually met.
🕵️ Check the conversation logs: Enter the chat from the Reporting or History module and check if the HTTP component step is listed as executed.
🔁 Review the task history in Zapier: Go to Zapier > Zaps > Task History. If there's no trace of the webhook, the problem is on the Atom configuration side.

🔎 Empty system fields: How to detect it

Sometimes, even though the HTTP component executes correctly, external systems don't receive key values like phone number, name, or email. This is usually due to a silent failure in field capture.

How to identify if the field wasn't sent?

Check the logs: If in the conversation history the field appears empty (null or ""), it means it wasn't captured previously or was overwritten.
Confirm the save: If you use the Save field component, validate that the value is populated before the integration step. Avoid overwriting system fields like phone.
Check the exact field name: Did you use phone, telefone, or phone_user in the HTTP body? It must match exactly with the variable saved in Atom. Avoid accents, spaces, or unnecessary uppercase letters.

✅ Checklist if the flow was duplicated or edited

If you recently made changes to your flow, ask yourself these questions:

🔁 Were the components that capture or save data copied correctly?
🧩 Do the variable names in the HTTP body match exactly with those in the flow?
🧠 Is the correct logical order maintained (Data capture → HTTP request)?
🧪 Were real tests done after the changes?

⚠️ Errors from data type discrepancies

In some cases, the bot may receive a different data type from the API than expected, which causes the value not to be stored or the flow not to continue.

🎯 Common scenario: Boolean vs. String A common situation is that the service returns a boolean value (true or false), but the flow field in Atom is prepared to save a text string (string). This generates a silent error.

🛠️ How to prevent it? Use the Manage errors option within the HTTP Request component. This allows you to:

Verify if the API returns an error or a different type.
Redirect to another part of the flow in case of failure.

📌 Practical solution example: If the endpoint returns true/false but you need text, create a Conditional or Save field component after receiving the data:

If the response is true ➡️ save "Yes".
If the response is false ➡️ save "No".

🧰 Final recommendations before testing

✅ Always test your endpoint in Postman with the exact values before passing it to Atom.
🔄 Compare the API result with what your flow expects to receive.
💬 Simulate the complete conversation from Atom to validate data capture.
💡 Additional tip: If your flow expects text, make sure all your API responses come formatted as strings (in quotes) to avoid conflicts.

🔗 Related article: [How to test your API in Postman]

Don't let any data get lost along the way! 🚀

Mastering the configuration and diagnosis of HTTP requests guarantees you robust flows and flawless integrations. Follow these best practices and connect Atom with your tools without interruptions. ✅

How to detect and solve errors in your bot's HTTP requests