AProcessing...
Calibrating response parameters. 
this might take a couple of minutes... beep boopA🤖 AI Response
Your observation about the discrepancy between parameter naming conventions—snake_case in the request body (e.g.,
References:
1. https://kestra.io/docs/best-practices/naming-conventions
2. https://www.youtube.com/watch?v=zbMAxBISOEw
3. https://buildship.com/changelog
4. https://buildship.com/blog/framer-form-data-to-external-apis
5. https://buildship.com/blog/secure-api-point-with-low-code
first_name) versus camelCase in workflow inputs (e.g., firstName)—is correct and can indeed cause issues in BuildShip workflows. According to BuildShip's documentation, when setting up the workflow input schema, the parameter names must match exactly as they appear in the incoming request body. If your request body uses first_name, your workflow input should also be named first_name to ensure proper mapping and data flow. If you need to convert between formats (e.g., from snake_case to camelCase), you can use a Transform node within your workflow to handle the conversion before passing the data to subsequent nodes. This approach ensures consistency and prevents mapping errors between your trigger data and workflow inputs. References:1. https://kestra.io/docs/best-practices/naming-conventions
2. https://www.youtube.com/watch?v=zbMAxBISOEw
3. https://buildship.com/changelog
4. https://buildship.com/blog/framer-form-data-to-external-apis
5. https://buildship.com/blog/secure-api-point-with-low-code
BuildShip AI Support
•7/11/25, 4:16 PM