data mapping issue in my workflow

[Alectos]

Your Workflow URL

https://connect.pabbly.com/v2/app/workflow/mapping/IjU3NjYwNTY0MDYzNDA0MzQ1MjY1NTUzMTUxM2Ii_pc

Your Task History ID

IjU3NjYwNTY0MDYzNDA0MzQ1MjY1NTUzMTUxM2Ii_pc

Consent to Access & Modify

I authorize Pabbly Support to log in to my account and make changes to the specified workflow for troubleshooting.

1. Hello Pabbly Connect community, I'm experiencing an issue where data from my Formatter steps appears to be empty when sent to my final API endpoint, even though I can see and select the values correctly in Pabbly's data picker. My workflow: Step 1: Webhook (receiving Firebase data) Steps 2-10: Formatter (9 steps cleaning different values - company name, email, phone, etc.) Step 11: API call (get session token) Step 12: Final API call (create customer in external system) The Problem: I can see all the Formatter "Result" values in Step 12's data picker I can successfully select and map them to the correct fields (name, email, phone, etc.) However, when the API request is sent, the receiving system returns validation errors saying the fields are empty/missing The external API responds with errors like "Field 'name' does not exist in object" or "Required field missing" What works: All Formatter steps show correct cleaned values when tested individually Data picker shows all the formatter results and allows me to map them Hardcoded values in the API call work fine What doesn't work: The actual mapped/dynamic values from Formatter steps don't appear to be included in the API payload Question: Why are the formatted values not being transmitted in the API request, even though they're visible and mappable in Pabbly? Is there a specific configuration needed to ensure dynamic values from Formatter steps are included in form-data API calls? Any insights would be greatly appreciated!

 

[Hrishabh.pabbly]

Hello @Alectos ,

We have reviewed your workflow "NGF" and noticed that in Step 11, where you are generating the session ID, the configuration is correct.

However, in Step 12, where you are creating the customer, the error is occurring because the session token used in the authorization is missing the Company ID.

To fix this, please follow these steps:

1. Use the Data Transformer (Pabbly) → Base64 Encode action.
2. In the input field, first write your Company ID, then add a colon “::”, and after that, map the session token received from Step 11.
   (Example format: 12345:{{session_token}})
3. Map the encoded output value from the Data Transformer step to the Authorization field in Step 12.

Once this is done, your API request should authenticate successfully.