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.
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: ""
Solution:Jump to solution
marking this resolved ✅ fix has been released 10 days ago. @RFA you must received the updated via email as well.
6 Replies
Processing...
🤖 Assembling the pieces of the puzzle. 🧩 this might take a couple of minutes... beep boop
🤖 AI Response
When passing data through a REST API call to your workflow, some fields may appear as Base64-encoded in the INPUTS section, while others like
last_name retain their original value. This typically happens when the incoming data contains special characters or is not in the expected format, prompting the system to encode it as Base64 for security and compatibility reasons.
To address this:
- Check your input mapping in the trigger configuration. Ensure all fields are mapped correctly in the "Connect" tab so that the workflow receives the expected data types.
- Update your workflow input schema to match the structure and types of the incoming data. This helps prevent unnecessary encoding by ensuring the system recognizes the data format.
- For fields displayed as [Base64], use a Transform Data or JSON Parse node early in your workflow to decode these values. In Power Automate, for example, you can use functions like base64ToBinary() to convert Base64 strings back to their original format.
- Even if values appear as [Base64] in the INPUTS section, the original data remains accessible in the full request body. You can retrieve it directly from the trigger data, such as Trigger Data -> body -> args -> first_name.
If the issue persists, contacting support with your workflow ID will allow for a more detailed investigation of your configuration.
🔗 References:
1. https://www.youtube.com/watch?v=0FlCebCVWOo
2. https://www.servicenow.com/community/developer-forum/i-have-an-issue-with-the-base64-encoding-in-servicenow/m-p/1710131
3. https://linnzawwin.blogspot.com/2021/02/handle-base64-and-binary-file-content.html
4. https://community.powerplatform.com/forums/thread/details/?threadid=4da2250c-f6c6-4899-9648-1b2ed59f66c5
5. https://community.dynamics.com/blogs/post/?postid=7d132f60-08ce-4433-be65-7241314c62a2BuildShip AI Support
@Answer Overflow
@RFA can you send this via in-app support? Will add a fix
Dm me
Solution
marking this resolved ✅ fix has been released 10 days ago. @RFA you must received the updated via email as well.