urgent: Kit.com Subscriber Fields Not Fetching Consistently in Pabbly (Last 10–15 Days)

Hello Pabbly Support Team,

I am experiencing an issue with one of my Pabbly Connect workflows.

My leads are submitting my Kit.com form, and all the data is being saved correctly in Kit.com. However, Pabbly Connect is not consistently fetching all the subscriber data.

The main issue is with the custom field:

Subscriber Fields  Whatsapp_number

Sometimes this field is fetched correctly, but many times it is missing, even though the value exists in Kit.com. Because of this inconsistent behavior, my workflow fails and the automation does not run properly.

This has been happening repeatedly for the last 10–15 days, and it is affecting multiple leads and multiple workflow executions.

Workflow Details:

• Workflow URL: mentioned
• Task History ID: mentioned

Could you please investigate why the Subscriber Fields Whatsapp_number field is not being fetched consistently from Kit.com?

If this is a known issue with the Kit.com integration, please let me know if there is any workaround or permanent fix.

Thank you, and I look forward to your assistance.

great post

Hello,

Thank you for reaching out to us and for sharing the workflow details and the task history ID.

To help us investigate this further, could you please share a screenshot from your Kit.com account showing that the Subscriber Fields → Whatsapp_number field is populated for the subscriber mentioned in the task history?

This will help us verify whether the value is present in Kit.com at the time the trigger is processed and better understand why the field is not being fetched consistently in Pabbly Connect.

Once we receive the screenshot, we'll investigate the issue further and assist you accordingly.

Hello,

Thank you for reaching out to us and for sharing the requested details.

Upon checking, we can see that your workflow is using an instant trigger, where the webhook is installed on the trigger application (Kit.com), and the trigger data is sent directly by Kit.com to the webhook.

From the task history, it appears that in some instances, Kit.com is not sending the Whatsapp_number field in the webhook payload. Since the payload is generated and sent directly from Kit.com's end, we are unable to determine why this field is occasionally missing.

As you mentioned that this issue has started occurring only recently, we recommend reaching out to the Kit.com support team and asking them to verify why the Whatsapp_number field is not being included in certain webhook payloads.

Once you receive an update from their team, please let us know. We'll be happy to assist you further based on their response.