Inputs inadvertently being swapped to equal '[Base64]'
However, they are all referenced the same way
Body received from Rest API Call:
{ "body": { "args": {
"resource": "jobs",
"request_type": "get",
"first_name": "Joe",
"last_name": "Shmoe" }}
Inputs listed:
resource -- [Base64]
request_type -- [Base64]
first_name -- [Base64]
last_name -- Shmoe
Note:
- Name keys all have the same format (e.g., last_name)
- Received body shows keys with values, but not listed in the inputs section of the log
MAIN ISSUE: The original intended value of a key is not available in the INPUT section, causing downstream nodes to fail.
3 Replies
Processing...
🤖 Compiling the latest insights for you. 🔄 this might take a couple of minutes... beep boop
🤖 AI Response
To resolve issues with accessing nested input parameters from REST API triggers in BuildShip, you should use the platform's mapping features to extract nested values and make them available as workflow inputs. Specifically, after fetching the latest request structure in the Connect tab, you need to map each required nested field (such as
body.args.resource, body.args.request_type, etc.) directly to your workflow inputs. This ensures that downstream nodes can access these values without failure. If further restructuring is needed, you can use the No-code Output Editor or a Transform node to customize the output fields, making the nested data accessible for subsequent workflow steps. The Output Editor allows you to add or edit fields and ensures that these mapped values are available throughout your workflow.
🔗 References:
1. https://www.youtube.com/watch?v=mmihZ-L-Yxg
2. https://support.buildship.com/m/1356779810168373440
3. https://www.moesif.com/blog/technical/api-design/REST-API-Design-Best-Practices-for-Sub-and-Nested-Resources/
4. https://buildship.com/changelog
5. https://www.youtube.com/watch?v=86cwaUY9LQ0BuildShip AI Support
@AI Support This is correctly set, as it was from when I first created this flow. However, the unexpected value of '[Base64]' still exists.
See above: Both first_name and last_name are mapped correctly, and both show in the original body. However, only last_name keeps it's value when read in the INPUTS section.
- last_name: Trigger Data -> body -> args -> last_name
-- Key: last_name
-- Type: String
-- Placeholder: ""
-- Default Value: ""
-- Description: ""
-- Required Field: No
-- Sensitive Field: No
-- Validation Regex: ""
- first_name: Trigger Data -> body -> args -> first_name
-- Key: first_name
-- Type: String
-- Placeholder: ""
-- Default Value: ""
-- Description: ""
-- Required Field: No
-- Sensitive Field: No
-- Validation Regex: ""
