I’ve been doing a bit of a silly dance with bubble trying to get a faster response to Shopify webhooks, and seen a couple of solutions that I didn’t like the sound of, as well as coming up with my own solution that I absolutely despise.
My workaround for the issue of bubble workflows running long before responding is to schedule an asynchronous backend wf for the fastest response (nothing new, suggested regularly on the forum). The issue you then have is data formatting, since bubble only allows you to send structured data using detection or field by field in params, an absolute nightmare on large calls. This can be circumvented by saving to the db, but I always resent having to do this so it’s my last resort in most cases.
With those conditions factored, I am now:
listening for webhook > scheduling wf for a speedy 200 > scheduled wf triggers internal api connector call > api connecter hits final endpoint mimicking a webhook with the raw body text
This works, my response times to Shopify are now down to ~300ms which is acceptable, but I absolutely hate it and it’s quite time consuming. Does anybody else have a better workaround that doesn’t involve db usage or a faas solution? It feels like the “return 200 when condition is not met” function was designed to handle exactly this, but I couldn’t get it working and the docs are a little lacklustre.