Why do APIs/webhooks run before Pipelines?
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 ...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendA 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
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
- 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__YouA 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
------------------------------- 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?
Anyway, thanks Mark!
------------------------------
Daniel Johnson
------------------------------
