Tips for faster scenario execution

These are all questions primarily dependent on the Google API response.

You will need to experiment. Benchmarking has not been conducted yet.

However, the more critical question is: why is the duration significant? Do you have a time-sensitive automation? If so, nocode solutions will not be the most performant. Raw code will consistently be faster.

This is important because the webhook functions as a form handler. Once a user submits the form, they must wait for the webhook's execution to complete before it can respond with a redirect to the correct webpage.

I don’t think that callin.io is suited for near real-time operations. If you insist on using a no-code solution, you could try to integrate callin.io with other tools. For example, the Glide platform lets you build apps based on sheets. callin.io provides a connector (Glide Integration | Workflow Automation | Make). Please take this as an example; I have no ties to Glide, but you could use Glide to quickly build the front-end that saves data to a sheet (in real-time) and then use callin.io to perform an action in the background with the collected data.

You might consider delegating processing to a separate scenario using a webhook, and then relaying the response back. This is akin to parallel processing, but if you place the webhook response at the conclusion of a lengthy scenario, the user experience might not be optimal.

Another interesting approach, and more intensive TBH that effectively parallelizes work between 2 platforms effectively.

Hi,

Great topic!

Can you show us your current scenario with Google Sheets?

Excellent suggestion…thank you. I do that with a number of repetitive automations and I believe the referring scenario doesn’t wait for a webhook response if I don’t specify one within the webhook.

Here is one of many I’ve created:

Screenshot 2022-09-23 1509141415×579 78.6 KB

If the items below (marked with red question marks) represent search steps, you could perform a single search that retrieves all rows and then create an array from that. This would eliminate the need for your second Sheets search. You can then use the map function to extract the data for each subscription.

image1539×806 63.8 KB

This is a comparable setup to one I developed a few weeks ago. It reduced the runtime by 25 times.

image2160×623 53.4 KB

image757×835 39.6 KB

Thanks for getting back to me. Could you tell me what the module on the left, labeled "Get all contractors," is called? I don't recognize that icon. Also, are you available for hire?

Thanks again. I’ve implemented your suggestions and identified several operations that can be executed via webhooks. These don't require return responses, allowing them to run in parallel without impacting the performance of their parent scenarios. I've also adjusted the order of some modules, placing any operations that don't need to complete before sending a redirect after that redirect has been sent.

Further performance improvements could likely be achieved by storing data in arrays rather than making multiple requests to Google Sheets.

However, I'm curious if utilizing data stores instead of Google Sheets would also boost speed. I've done some experimentation, but I'm encountering an issue because searching data stores doesn't return the count of found bundles, which is crucial in certain scenarios like the one depicted here:

Capture1602×1211 86.4 KB

callin.io support suggests using an aggregator to count the bundles. While this approach could work for the aforementioned situation, in other cases, I need to loop through the returned bundles.

Would data stores offer better performance? Additionally, is there an alternative method to determine the number of bundles returned?

Yes, absolutely. Data stores are significantly faster because they function as a native object.

Regarding the bundles returned, could you please provide an example output from a search data store? I believe

Certainly.

I've set up a straightforward test scenario. Here's what can be selected in another module or filter within an iteration of the results:

And here is the output from the search itself:

Alternatively, presented in JSON format:

json
[
{
"key": "thesignpolice@gmail.com",
"data": {
"Email": "fsbobacker@gmail.com",
"First Name": "Vacant",
"Full Rec": false,
"Sandy": false,
"With Bar": false,
"Clear": false,
"Large": false,
"Shore": false,
"Deep": false,
"Nearest Shopping": "N/A",
"Max Shopping Distance": 100,
"Property Type": "Vacant Land",
"Max Price": 10000000,
"Min Beds": 0,
"Min Baths": 0,
"DateSubscribed": "2022-10-13T20:44:00.000Z",
"NumAlerts": null,
"NumListings": null
}
},
{
"key": "fsbobacker@gmail.com",
"data": {
"Email": "thesignpolice@gmail.com",
"First Name": "Home",
"Full Rec": false,
"With Bar": false,
"Clear": false,
"Large": false,
"Shore": false,
"Deep": false,
"Nearest Shopping": "N/A",
"Max Shopping Distance": 100,
"Property Type": "Home",
"Max Price": 10000000,
"Min Beds": 0,
"Min Baths": 0,
"DateSubscribed": "2022-10-13T20:40:00.000Z",
"NumAlerts": null,
"NumListings": null,
"Sandy": false
}
}
]


Hi,

Yes, I offer professional callin.io services. Please send me a direct message if you'd like to learn more.

Thank you