Currently, no.
Do you mean that you have an external tool which needs to track doc changes in Fibery?
What actions is this external tool going to take if it could know that there are pending changes (but not know what those changes are until the debounce window is over)?
Do you mean that you have an external tool which needs to track doc changes in Fibery?
What actions is this external tool going to take if it could know that there are pending changes (but not know what those changes are until the debounce window is over)?
From my tests, the updated content is available immediately in the API, but it may take a bit (10-15 minutes) for History API to register the update.
I have an AI tool that accesses filesystem copy of the Fibery account, as well as other sources of data that we use (for example articles we work on, or current state of operations). This tool works with all the data on a local filesystem rather than via MCP - each integration has its own folder. From my (potentially wrong) observations MCPs make data less accessible for the model than Grep/Glob tools.
At the moment AI Tool works great with Fibery, but sometimes misses the very latest updates on the documents due to History API debounce. Considering the limited volume of changes, I would like to fetch currently edited documents repeatedly after a tiny delay to ensure that documents stay up to date.
Are there plans to expand this to work in relation fields and to allow filtering by field values?
I would use that hundreds of times some days! I am already loving the in:... shortcut.