Inputs inadvertently being swapped to equal '[Base64]'

Original message was deleted

AI Support•7/11/25, 4:20 PM

Processing...

Gathering bytes and bits.

this might take a couple of minutes... beep boop

AI Support•7/11/25, 4:20 PM

🤖 AI Response

When sending parameters through a REST API call to BuildShip, all parameters from the request body are accessible in your workflow using the same referencing format, such as {inputs.resource}{inputs.resource}, {inputs.request_type}{inputs.request_type}, {inputs.first_name}{inputs.first_name}, and {inputs.last_name}{inputs.last_name}. The [Base64][Base64] notation you see in logs is simply BuildShip's way of indicating how certain values are encoded internally; it does not affect how you access or use these parameters in your workflow nodes. Regardless of how they appear in logs, you can reference all request body parameters directly in your workflow as inputs. If you encounter issues accessing these values, ensure your JSON structure is correct and use the appropriate syntax to reference each component. For more details, you can consult the BuildShip documentation on inputs.

References:
1. https://support.buildship.com/m/1369745528904093787
2. https://www.youtube.com/watch?v=7ehFdORNIaE
3. https://support.buildship.com/m/1270964034207879238
4. https://support.buildship.com/m/1153845446096203916
5. https://support.buildship.com/m/1197545606277779517

BuildShip AI Support

•

7/11/25, 4:20 PM

RFA•7/11/25, 4:22 PM

@AI Support In any case, the original intended value of a key is not available in the INPUT section, causing downstream nodes to fail.