Transform field mapping is not working
Status: Open · Asked by Mortgage Free on · 0 views
Hi Pabbly Support Team,
In Action Step 4 of my workflow (API by Pabbly), I am trying to map webhook fields inside the “Enable Select Transform” → “Transform Template” section, but the dynamic field mapping is not working.
The webhook data is being captured correctly in Step 1, however:
- mapped fields are not appearing properly inside the transform template
- variables are not resolving dynamically
- the template keeps treating the mapped values as plain text
I am trying to send nested JSON data to the Zoho Webinar API using Transform mode.
Could you please help me fix this issue ASAP?
Thank you.
Hi @MATRIXFREEDOM,
I’ve reviewed your workflow again. The reason your variables are showing as plain text is that when 'Select Transform' is enabled, the Template box doesn't pull directly from your Webhook. It only pulls from the 'Data' field directly below it.
To fix this, please follow these steps:
- Map the Webhook Data: In the 'Data' field (below the Template), map the entire response from Step 1 or the specific fields you need.
- Update the Template: In your Template box, you should reference the data you just mapped. If you map the email to a key called user_email in the Data box, your template should look like this: "email": "{{this.user_email}}".
- Check the Docs: For a deeper understanding of how to structure these transformations, please refer to our official guides:
The 'Transform' feature is powerful for complex data reshaping, but for a standard Zoho Webinar registration, the standard JSON Payload is much simpler to manage!
The 'Transform' feature is powerful for complex data reshaping, but for a standard Zoho Webinar registration, the standard JSON Payload is much simpler to manage!
Hi Team,
Thank you for the clarification regarding the Transform feature.
I understand that Transform is mainly intended for complex JSON reshaping. Since my use case is a standard Zoho Webinar registration API request, could you please guide me on the recommended and simplest payload method for this scenario?
I specifically need to send the following nested JSON structure dynamically from my Elementor webhook data:
{
"registrant": [
{
"email": "dynamic_email",
"firstName": "dynamic_firstname",
"lastName": "dynamic_lastname"
}
]
}
Could you please suggest the best approach in Pabbly Connect to send this payload correctly without using complex Transform mapping, if possible?
Also, if there is a preferred configuration using:
- JSON Payload
- Raw Body
- Set Parameters
- Custom Request
or any simpler method,
please share the exact recommended setup.
Thank you.
Hi @MATRIXFREEDOM,
I’ve taken a deep look at your workflow, and while we can simplify the JSON mapping, there is a major stability issue in Step 3 (your Token Generation step).
The Problem: You are using a one-time authorization_code. Zoho tokens expire every hour, so your workflow will break constantly. Since Zoho Webinar is not yet a native app in Pabbly Connect, building a manual API connection is complex and prone to these errors.
The Solution: Use Pabbly Action Builder Instead of struggling with manual API steps and unstable tokens, you can use our Action Builder to create a custom Zoho Webinar app for your account.
- AI-Powered Setup: You can simply describe the Zoho Webinar API to the AI, and it will generate the code and handle the authentication logic for you.
- Stability: It creates a dedicated 'Action' that you can use just like any other native Pabbly app, making it much more stable than a manual API request.
- Simpler Mapping: Once built, you won't need to write any JSON in your workflow; you'll get a simple form with fields for Email, First Name, and Last Name.
Check out the guide here to get started: ? Pabbly Action Builder - Guide for Creating Custom Action Step APIs
If you'd like to stick with your current API step for now, please uncheck 'Enable Select Transform' and use the JSON Payload method as mentioned previously.
Hi @Hrishabh.pabbly,
Thank you for the clarification.
I understand the concern regarding the temporary authorization_code token flow and agree that long-term stability is important for recurring webinar registrations.
Before migrating fully to Action Builder, could you please guide me on the simplest working JSON Payload setup inside the current API module (without using Transform mode)?
Also, regarding Action Builder:
- Does it automatically handle Zoho access token refresh using refresh_token?
- Do you have a sample Zoho Webinar Action Builder configuration for attendee registration APIs?
I’d appreciate any example setup or best practice recommendation for Zoho Webinar integrations.
Thank you.
Thanks for getting back to us.
Yes, the Action Builder does support the refresh token flow and can handle access token refresh automatically.
However, since your API setup is already working, what we would recommend instead is using the “Zoho Meeting : Custom API Request” action. Zoho Meeting also supports Zoho Webinar-related APIs, so this should work fine for your use case.
Using the native Zoho Meeting connection with the Custom API Request action will help you avoid manually handling the authorization/access token flow, and you can simply configure your API request directly there.
Please try this approach and let us know how it goes.
Additionally, if required, we can also ask our team to consider creating a dedicated native action for the Zoho Webinar attendee registration APIs.