• Instructions to Ask a Question

    For any assistance, please click the "Ask a Question" button and select the Pabbly product for which you require support.

    We offer seven comprehensive applications designed to help you efficiently manage and grow your business:

    Our support team endeavors to respond within 24 business hours (Monday to Friday, 10:00 AM to 6:00 PM IST). We appreciate your understanding and patience.

    🚀 Exclusive Lifetime Offers 🚀

    We invite you to take advantage of our special one-time payment plans, providing lifetime access to select applications:

    • 🔥 Pabbly Connect — Lifetime Access for $249View Offer
    • 🔥 Pabbly Subscription Billing — Lifetime Access for $249View Offer
    • 🔥 Pabbly Chatflow — Lifetime Access for $249View Offer

    Make a one-time investment and enjoy the advantages of robust business management tools for years to come.

Webhook to Beehiiv Error Message - Custom Fields

kurt

Member
Your Task History ID
IjU3NjYwNTZiMDYzMzA0MzQ1MjZhNTUzMTUxMzAi_pc
hi,

I'm getting an error back from Beehiiv, but I think its due to formatting, not that the custom fields are not available, as I've made them and verified.

I made this video of the issue, including both Pabbly and Beehiiv screens : https://d.pr/v/k3GvX6

screen shot here

when I send a test of the api, I get back 'unprocessable_entity' from Beehiiv. and I have verifed in Beehiiv that the data is not appearing.

can you help me?
 

kurt

Member
Not sure if it's related, but this is something happening in the same webhook, with the data passing into pebbly. customer.io requires the json webhook to have placeholders, but I'm only getting the default placeholders, (ie default: 'form name') not the data, int Pabbly. Is there an issue with the json?

video of issue. https://d.pr/v/YnQlOr

JSON

{
"campaign_id": {{ campaign.id }},
"segment_id": 38,
"customer.email": "{{ customer.email }}",
"customer.first_name": "{{ customer.first_name }}",
"customer.SIGNUP_URL": "{{ customer.SIGNUP_URL | default: 'URL' }}",
"customer.DUE_DATE": "{{ customer.DUE_DATE | default: 'due-date' }}",
"customer.utm_source": "{{ customer.utm_source | default: 'utm_source' }}",
"customer.utm_content": "{{ customer.utm_content | default: 'utm_content' }}",
"customer.FORM_NAME": "{{ customer.FORM_NAME | default: 'form name' }}",
"customer._created_in_customerio_at": "{{ customer._created_in_customerio_at | default: 'cio_created_date' }}"
}
 

Preeti Paryani

Well-known member
Staff member
Hello @kurt,

Apologies for the delayed response.

Upon reviewing the workflow, it appears that you’ve already resolved the issue on your end. Please let us know if you need any further assistance — we’re here to help.
 

kurt

Member
Hello
Hello @kurt,

Apologies for the delayed response.

Upon reviewing the workflow, it appears that you’ve already resolved the issue on your end. Please let us know if you need any further assistance — we’re here to help.

Actually they are both in the same workflow, but this issue is not resolved. (thought the earlier one was!). perhaps you can help.

This is something happening in the same webhook, with the data passing into pabbly. customer.io requires the json webhook to have placeholders, but I'm only getting the default placeholders, (ie default: 'form name') not the data, int Pabbly. EVEN when the data exists. Is there an issue with the json?

video of issue. https://d.pr/v/YnQlOr

JSON

{
"campaign_id": {{ campaign.id }},
"segment_id": 38,
"customer.email": "{{ customer.email }}",
"customer.first_name": "{{ customer.first_name }}",
"customer.SIGNUP_URL": "{{ customer.SIGNUP_URL | default: 'URL' }}",
"customer.DUE_DATE": "{{ customer.DUE_DATE | default: 'due-date' }}",
"customer.utm_source": "{{ customer.utm_source | default: 'utm_source' }}",
"customer.utm_content": "{{ customer.utm_content | default: 'utm_content' }}",
"customer.FORM_NAME": "{{ customer.FORM_NAME | default: 'form name' }}",
"customer._created_in_customerio_at": "{{ customer._created_in_customerio_at | default: 'cio_created_date' }}"
}
 

kurt

Member
Hi Preeti, Here is the most clear version looking into a single task form task history:

IjU3NjUwNTY4MDYzNDA0Mzc1MjY0NTUzMjUxMzA1MTY2NTQzOTBmMzUi_pc

you can see the data is now coming into the connect, but not passing out, but it is visible mashed up in one field.
video of task: https://d.pr/v/MnJWbL
 

ArshilAhmad

Moderator
Staff member

It looks like you're now receiving the correct data in your trigger step. Apart from the Due Date field, all other fields are showing actual data instead of placeholders.
1751576245067.png



We have now set up the 'Custom Field: Name(s)' and 'Custom Field Value' fields on your behalf, based on the information previously shared. We cannot pass the Due Date to Beehiiv, as we are not receiving it in the trigger step. Additionally, there appears to be an issue with the 'signup_URL' field. Have you made any changes to the 'signup_URL' custom field in Beehiiv?
1751576346170.png



Just a quick note—please create separate threads for different issues to help avoid confusion.
 
Top