I’ve created a scenario for uploading and updating invoices from Salesforce via Make.com to Quickbooks.
It works by taking the outbound message from Salesforce (an XML webhook) when the invoice (object) is edited, parsing the XML, and processing it in to the relevant line items to create the Invoice.
The issue I have is that if I edit two objects at once (for example, during a report when you can edit multiple at once), Salesforce is showing me that 2 webhooks are being fired, but it seems that Make.com is only receiving one of these.
Does anyone know if there are any limitations to Make.com receiving webhooks, or if I’ve done something wrong?
Hi @Rutter, is it actually only receiving one webhook? Or just one per run?
There’s a couple ways to check this.
You can turn off your scenario, then fire the webhook from Salesforce. Then manually “Run Once” in your scenario. Then run it again and see if it processes another webhook successfully.
You can go into your Webhook module settings in your scenario and change the maximum number of results to something greater. Then trigger the scenario and see if there are two bundles coming through.
Hi!
Thanks so much for your reply, they were both great ideas.
So I turned the scenario off, then ran it with 3 objects, and looking at the webhook it’s only had one delivered.
So it seems that when I make changes within Salesforce to more than two records, the Webhook that is sent combines multiple invoices in to a single XLM array.
Does anyone know how I can break down the array to make multiple invoices?
Last one on this.
From what I can see, it’ll be best if we can somehow split the XML in to three bundles, then run the scenario for each bundle.
Does anyone know if that’s possible?
I’d take a look at the Iterator under the Flow Control module. If your data is structured as an array, you’ll be able to pop that Iterator on as the second module and then the rest of the scenario will run for each bundle individually.
Otherwise, take a look at the XML module and the parsing functionality.
Hi, yeah, I’ve already got an iterator to build the array for the invoice to generate.
And I’ve also had to use the XML parse to break out my initial bundle.
Thank you, thank you, thank you!
So I’ve been playing around with this for sometime, and you were right.
Running an Iterator after the XML parse then breaks the single bundle in to multiple bundles.
I’ve updated the rest of the scenario to take it’s data from that iterator, and it works perfectly.
thanks once again
Hi Chris, I’m actually looking to implement this flow as well. I’m wondering, why didn’t you use the Salesforce module in Make? It has a trigger to watch new or updated objects. I’d appreciate any insight. Thanks!
