Data mapping errors

[Megan55]

Your Workflow URL

https://connect.pabbly.com/workflow/mapping/IjU3NjcwNTZjMDYzMDA0MzM1MjY1NTUzYzUxMzAi_pc

Your Task History ID

IjU3NjUwNTY0MDYzMzA0MzA1MjZmNTUzMjUxMzQ1MTZhNTQzNzBmMzEi_pc

Consent to Access & Modify

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

Hey Pabbly team,

I'm using Pabbly to connect system.io to Kit. I have a very simple workflow—capturing emails + first and last name in System.io and mapping them to Kit. However i've noticed that the mapping seems to be random. Sometimes it's captures the first name correctly, sometimes it coatures the last name instead and sometimes it pulls the subscribers country.

I've mapped all the fields correctly in the workflow, and doubled checked and remapped many times. However, this keeps happening?
Any advice appreciated.

Cheers,
Megan

 

[Hrishabh.pabbly]

Hi @Megan55 ,

Thank you for your patience. We’ve carefully reviewed the webhook data being received from Systeme.io, and we’ve identified the root cause of the issue.

The problem is not with Kit or the mapping itself — it’s happening because Systeme.io sends the fields data in a different order each time.

However, the position of first name, last name, and country keeps changing between submissions.

For example:

• In one submission, 0 = Last Name
• In another submission, 0 = Country
• In another, 0 = First Name

Since the mapping was done using these numeric positions (0, 1, 2), when the order changes, the wrong value gets mapped to the wrong field — which is why it appears random

To fix this permanently, please follow these steps:

Step 1: Capture the Trigger Response in Advanced Format​

• Go to your Systeme.io trigger step.
• Click on “Advanced” while capturing the webhook response.
• Re-capture a fresh submission.

This ensures we get the complete raw JSON structure properly.

Step 2: Use Action – JSON Extractor (Pabbly)​

• Add a new action step.
• Select “JSON Extractor (Pabbly)”.
• Pass the full webhook response into the JSON field.
• Extract values using the slug (like first_name, surname, country) instead of using index numbers (0,1,2).

This will allow us to dynamically pull:

• First Name
• Last Name
• Country

Correctly every time — regardless of order.

Step 3: Map Extracted Fields to Kit​

• Now, in the Kit action step,
• Map the extracted First Name and Last Name fields from the JSON Extractor step.

This will completely stop the random field swapping issue.

Once implemented, the mapping will remain stable even if Systeme.io changes the order of fields again.