I’m building a Bubble admin flow for Crankflo and want Bubble to stay the clean UI layer while an external system handles tasks, proof and approvals.The pattern I am considering:- Bubble creates or updates a work item through the API Connector.- Crankflo assigns an executor and stores proof.- Bubble shows status and lets a user approve retry or next action.- A webhook updates Bubble when the external workflow changes.For Bubble builders, would you keep Bubble as the source of truth and mirror status out, or treat the external system as source of truth and sync back into Bubble? Any API Connector or webhook patterns that have worked well for this?
I think that if you use an external proof system, this is the one that should be the source of truth. Is this system have an API, you may consider fetching data from it,