Instant Queries

Instant Queries is a caching layer built into the Blue API that serves frequently-accessed records back in milliseconds. It’s enabled automatically on Pro and Enterprise plans — no client changes required.

What it does

When your app, the API, an integration, or an automation requests records, the response is cached briefly. Subsequent identical requests are served from cache instead of hitting the database. In Blue’s rollout testing, 82.6% of requests hit the cache and returned in ~8ms on average — roughly 6× faster than an uncached query.

This benefits any read path that asks for the same data within a short window: a board re-rendering after a navigation, an automation iterating over a list, a dashboard chart refreshing, a webhook handler enriching a record.

Where it applies

Instant Queries serves:

• Record queries through the GraphQL API
• Reads from public webhooks and the MCP connector
• The web and mobile apps when fetching records you’ve already seen recently
• CLI and SDK reads

Writes — creating, updating, deleting records, posting comments — always go to the live data path, so you never see stale results immediately after your own changes.

Cache invalidation

The cache is write-through: any change to a record (a field edit, a comment, an automation update) invalidates the cache for that record immediately. The next read sees the new state.

This means you don’t have to think about stale data in normal use — the cache is transparent.

Behavior

• Available automatically on Pro and Enterprise plans. Free and lower tiers continue to hit the database directly.
• No code changes required — the same GraphQL queries you already make are accelerated.
• Cache hit / miss does not affect query semantics. The shape of the response is identical either way.
• API rate limits still apply per the API documentation. Instant Queries reduces latency, not your quota.