QoS Support for Webhooks?

Consider a scenario where you have a incoming webhook defined, and you don’t necessarily want to process jobs in sequential order…

Instead, consider each job has a priority label like “High” or “Low”.

Then, when processing jobs, focus on always processing “High” priority jobs first, then “Low” priority jobs when the “High” queue is empty.

Is there any way to implement such a feature in an existing Make.com scenario?

Depending on where the webhook is coming from, you may be able to add a parameter with priority = high or low (or a number) then add them to a datastore instantly, but have another scenario pulling all high priority tasks, and when that’s empty, pull low priority.

Not sure the exact requirements here.

2 Likes