Problem Description:
We are experiencing issues with using dynamic variables in metadata fields within HTTP requests in Make.com. Here’s a breakdown of the situation:
-
Goal: We are attempting to send dynamic data (booking information) to Stripe as metadata within a
setup_intent
request. Our aim is to pass booking-related metadata likebooking_number
andinternal_booking_number
as dynamic variables into these fields to associate them with each customer in Stripe. -
Issue: When we use static values in the metadata fields, the HTTP request works correctly, and the metadata appears as expected in Stripe. However, when we switch to dynamic variables, even though the variables are mapped correctly from previous steps, they are not being passed to Stripe. In each HTTP request input and output, the metadata fields appear as empty.
-
Debugging Steps Taken:
-
Verified Variable Population: We confirmed that the variables hold the correct data just before the HTTP request step.
-
Tried Using Text Composer and Text Aggregator: We attempted to pass dynamic data through both the Text Composer and Text Aggregator modules to ensure proper formatting, but the data remains empty when passed to Stripe.
-
Checked Advanced Settings: We reviewed the HTTP request module’s advanced settings, including “Parse response,” “Body type” (set to
application/x-www-form-urlencoded
), and other parameters to make sure they align with Stripe’s requirements. -
Tested Alternative JSON Format: We considered switching to JSON format, but as the Stripe endpoint typically expects
x-www-form-urlencoded
, we maintained this format.
- Additional Observations:
-
When we inspect the input and output logs of the HTTP request module, all mapped metadata fields (e.g.,
metadata[booking_number]
) are showing as empty. -
Static text entries work flawlessly, which suggests the problem lies specifically in the handling of dynamic data by Make.com.
- Questions for Support:
-
Is there a known issue with passing dynamic variables in
x-www-form-urlencoded
metadata fields through the HTTP module? -
Are there any specific configurations or transformations we need to apply to ensure dynamic variables are recognized and passed correctly in this format?
-
If
application/x-www-form-urlencoded
is problematic with dynamic data, is there an alternative approach you would recommend for integrating with Stripe while using dynamic metadata?
Attachments: (If applicable, attach screenshots of the HTTP request configuration, input/output logs, and any error messages)
Any insights or solutions would be greatly appreciated, as we’ve exhausted typical debugging steps. Thank you for your assistance!