In Review
HTTP request testing in journeys
In Review
U
5 months ago
1 comments
Business problem
Currently, there is no way to test HTTP requests directly within a journey. Users are forced to run the entire journey via a sandbox WhatsApp environment to verify if a request works, which is time-consuming and inefficient for debugging.
Wished result
A "Test request" functionality within the HTTP request block that allows users to trigger the request and view the response immediately during configuration.
💡
Reminder: Insights help guide our direction. Votes and discussions help us understand demand, but don't guarantee development. Every insight receives a response within 30 days.
Discussion (1)
Sign in to join the discussion