I had created a scenario with a Webhook trigger from a Jotform form. The Webhook received the JSON payload from Jotform as 1. rawRequest. The JSON Parser was mapped to receive the rawRequest and the whole scenario was set up and working correctly until I hit the Gmail connections limit (too many Draft Email modules) so I had to split my scenario into two. Jotform cannot conditionally send the payload to only one of the two new scenarios. So, I want to send on the 1. rawRequest to either one of the two new scenarios using an intermediary Webhook and two HTTP Modules. Basically, the new Webhook needs to accept the 1. rawRequest and send it on (without alteration) to either one of the two scenarios using a filter on each HTTP Module, so that each scenario receives the 1. rawRequest intact. That way, I don’t need to remap my two scenarios. Whatever configuration I seem to try doesn’t work. It is always received in the other scenario as the full list of fields, which the JSON Parser cannot parse. I hope someone can point me in the right direction. Thank you in advance.
Jotform Webhook Filter.blueprint.json (32.1 KB)
Hey Tony,
can you show some screenshots of the setup demonstrating what the issue is? Also, why a webhook and not the built in Watch Submissions module? Also also - can you show the error message you are getting when creating the drafts?
Hi Stoyan,
Please see attached.
The Gmail error message I was receiving was the ‘too many connections’ error. My original scenario had more than 15 Gmail modules. Unfortunately, with Make, all branches are activated even if only 1 Gmail module was going to be used. I currently use Zapier for this workflow, but wanted to migrate it to Make. With Zapier, only the relevant path is activated, so it doesn’t trip the Gmail connections error.
rawRequest1 – This is now showing the webhook on my intermediate scenario. The rawRequest JSON is received from Jotform and I just want to pass it through to my two scenarios intact.
rawRequest2 – This was the configuration of the HTTP modules.
rawRequest3 – This is how it arrives in my scenario, with all fields visible (it’s parsed the rawRequest JSON). I wanted to pass the rawRequest JSON through a JSON Parser, because all of the variables in my scenario were linked to the results of the JSON parser. It means that I have to remap all of variables.
I used a webhook rather than the Jotform Watch Submissions module because I understood them to be basically the same.
From the screenshots it looks like you are sending it forward, so what is the issue on the other end?
I don’t want it parsed. I want to pass through the rawRequest JSON so that I can parse it in my ParseJSON module, because all of the field mappings are linked to the output of the JSON Parser