Why do APIs/webhooks run before Pipelines?

Question

I'm doing some testing on an app and noticed functionality based on APIs/webhooks was completing its task well before the pipeline was triggered. The pipeline trigger was a field on a form, so when I saved the form both the API/webhook and the pipeline should start. Why does it take longer for the pipeline to start? I'm asking because I'm thinking of deploying a process whereby this order matters. If the were reversed, and the pipeline fired first, the webhook wouldn't run. Will it always be the case that pipelines will be slightly slower to trigger and run than APIs and webhooks?

Thanks,

------------------------------
Daniel Johnson
------------------------------

markshnier__you · Answer

A native Webhook will always Trigger instantly and much quicker than Pipelines. A Webhook just fires while a Pipelines needs to fire up a complex engine.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

danieljohnson2 · Answer

Hey Mark,Thanks for the reply. Do you think there's any possibility in the future of Pipelines being trigger first? Sounds like you don't.------------------------------Daniel Johnson------------------------------

markshnier__you · Answer

A pipeline can fire a web hook. So if you need to have things firing in sequence then they should all be put into the pipeline and then the pipeline will run them in sequence.

------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------

danieljohnson2 · Answer

In a perfect world where legacy users aren't expecting a particular result from the webhook that's in place, I'd agree with you. But I'm liable to have a revolt on my hands if I slow this one down. They click a button, the page refreshes and shows the change. If I put that behind a Pipeline, the page would refresh and load before the Pipeline runs. So, I would end up with a bunch of users asking me why their button doesn't work anymore, and am I sure it's working?&nbsp;Anyway, thanks Mark!------------------------------Daniel Johnson------------------------------

jimharrison · Answer

Hi Daniel,You're dealing with concurrency. You can do this by setting the filter for the Webhook to be set by the Pipeline.1. add a checkbox field (we name ours with "Trigger" in the name and then comment which recipe it triggers).2. The last step in the Pipeline is to update the Trigger field for the record.3. The filter in the Webhook is set to run when the Trigger field changes from false to true.additional options:make a scheduled process go through and un-check the trigger. Form rules to un-check a trigger that is checked are also good, in cases where the Users are doing something before the check box is reset. Make another Pipeline that runs after the Webhook when the trigger check box is false.Problems:One record is fine for one change.Grid Edit, import from csv, more than one record you have to play with using %repeat on% in the Webhook.Philosophically the Webhook is the last "Step" in the Pipeline. A lot of testing and planning are recommended in order to understand the results before deploying or the potential for making data salad is exponential. Good luck, interested to know your results.Jim HarrisonPortland, OR------------------------------Jim Harrisontransparency = knowledge + understanding : The Scrum Dudes------------------------------

Forum Discussion

Why do APIs/webhooks run before Pipelines?