I’ve configured Make.com to receive data from a WordPress form via a webhook URL, but the payload seems to be missing. I need assistance in troubleshooting this issue to ensure that the data is correctly captured and processed.
The example payload from the WordPress form is in the following format:
json
{
“fname”: “???”,
“lname”: “???”,
“email”: “???”,
“phone”: “???”,
“description”: “???”,
“signup_url”: “???”,
“useripnr”: “???”
}
Hi @Ace_Automate,
Did you ask the webhook to reanalyze the input data to configure the input data structure correctly?
L
Yes, I did that, but it’s not receiving the payload.
I have also created a data structure for the webhook.
and I’m still not receiving the payload.
tried using Postman also. 
Hmmm.…there must be something I’m not understanding in what you’re doing.
Can you post a screenshot of your scenario?
I used the same data as you (making sure to put a value in each field):
I have a simple Webhok that does nothing;
and when I run it from Postman, I get:
Notice that the bubble with the (1) is where the payload is described. and I get this in future modules:
Hopefully something in there helps you.
L
@L_Duperval, When I test it using Postman, I receive the payload, but when I try it with the WordPress form, the payload isn’t coming through. This has left me a bit confused.
I have also uploaded a video so you can check it out.
It looks like the data is not sent correctly to the webhook. You can see by the size of the data received: 77 bytes. But the JSON you shared above is more than that. So for now, I’m leaning toward a problem with the way your WordPress site is calling Make.
Also, in the video, I’m not sure your scenario ran completely. Can you run it once and try again to see what happens? If you see a 0:40 in your video, there is no (1) beside your webhook. So that indicates to me that it wasn’t executed.
Click the “run once” button. If you get a warning about existing data, ignore it and say you want to use new data. Then submit your form again and see if anything changes.
L
The scenario is working fine now, and the lead is being successfully created in the CRM. To be honest, I’m not entirely sure what happened, but I created a new webhook and tested it, and now it’s working properly. However, there’s one more thing I need your help with: UTM parameters in the URL. How can I capture these parameters and transfer them to the CRM when the lead is being created?
I am getting the data just fine in Bitrix as a lead and i also get the site url which contains something like this “camp_source=PaidSearch&camp_name=TestKWDsExact-TargetCPA&camp_adgroup=&camp_campaignid=16796149813&camp_adgroupid=143793012188&camp_creative=692357034632&camp_matchtype=e&camp_placement=&camp_targetid=kwd-466280669972&camp_network=g&camp_keyword=video%20makers%20in%20mumbai&camp_device=c&camp_extra=&gad_source=1” where i want to send it to bitrix as UTM parameters. Can you help me on this one.
How are the UTM parameters sent? If it’s in the request, you should be able to extract them from the webhook. Chances are you might receive a multipart request. If not, you might be able to use the split() function to parse the string.
If this problem is solved, I recommend you mark it as such and create another topic specifically to address the UTM aspect. Plus, there are a few posts on parsing UTM parameters so one of them might help. If not, ask for help!
L
That said, you
Oh, you wrote this while I was typing my other question. I still recommend you ask it as a separate topic for others to see.
You can use a Text Parser with a regular expression to split the items and use that to populate the CRM. There may be tools within Bitrix that do it also.
If you decode to go the regularexpression route, you can as an AI like ChatGPT or claude to generate the regexp for you and test it in https://regex101.com/ using the ECMAScript parser.
L
@L_Duperval, The reason I wasn’t receiving the full payload was that I had enabled Request Headers, GET Request HTTP Method, and JSON Pass-Through. As a result, I was only getting the Name and Value in the payload.
