G
Knowledge / Intranet

Guru AI Integration

Connect Guru to BeforeQuery for grounded AI answers and agent actions across Knowledge / Intranet.

Connect Guru
What is it?

About Guru

Guru is one of the Knowledge / Intranet platforms BeforeQuery connects to. Once linked, the platform's data becomes a first-class source for grounded AI answers and a target for policy-gated agent actions — the same identity, approval, and audit-log guarantees every other integration ships with.

Setup

How to connect Guru

  1. Step 01

    In the BeforeQuery dashboard, go to Integrations → Knowledge / Intranet and select Guru.

  2. Step 02

    Sign in to Guru with an account that has permissions to grant BeforeQuery the Knowledge / Intranet scopes required.

  3. Step 03

    Confirm the connection. Guru is now available as a source and action target for every playbook in your workspace.

Explore

Related integrations

A
Airtable

Airtable is one of BeforeQuery's Knowledge / Intranet integrations. Connect it once and every agent in your workspace can read, reason over, and act on Airtable data with your policies + audit trail.

C
Coda

Coda is one of BeforeQuery's Knowledge / Intranet integrations. Connect it once and every agent in your workspace can read, reason over, and act on Coda data with your policies + audit trail.

D
Document360

Document360 is one of BeforeQuery's Knowledge / Intranet integrations. Connect it once and every agent in your workspace can read, reason over, and act on Document360 data with your policies + audit trail.

How BeforeQuery uses Guru

What the agent does with your Guru connection

  • 01

    Index every Guru page, article, and space into the Knowledge Base for grounded AI answers.

  • 02

    Auto-sync on Guru updates so answers reflect the latest published content.

  • 03

    Respect Guru space + page permissions — sensitive knowledge stays scoped.

  • 04

    Draft new Guru content from playbooks — meeting notes, policy updates, incident post-mortems file directly into the right space.

Use cases

What teams actually do with the Guru integration

Grounded Q&A from Guru

Employees ask "how do we handle X?" — BeforeQuery answers from the exact Guru page that documents it, with a link to the source. Faster than opening Guru and searching manually; more accurate than a stale mental model.

Content freshness monitoring

BeforeQuery flags Guru pages that answer FAQs but haven't been touched in > 6 months, or that contradict other pages, or that get low click-through from search. Docs team gets a triage list, not a "everything is stale" panic.

Meeting notes to Guru

From a transcript or meeting recording, BeforeQuery drafts structured notes (decisions, action items, follow-ups) and files them into the right Guru space with correct tags + attendees. Author confirms, publishes.

Answer questions grounded in Guru

Employees and customers ask Guru-related questions in Slack, Teams, or the widget — BeforeQuery answers with the exact Guru record shown alongside the response. No context switching, no "log into Knowledge / Intranet to check" round-trips.

Guru — Frequently Asked Questions

Common questions about connecting BeforeQuery to Guru.

Yes. Retrieval respects the asking user's Guru permissions; users only see answers from pages they can already open. Permission changes propagate on next sync (typically < 5 min).
Standard OAuth 2.0 where Guru supports it, otherwise API-key or bearer-token auth. Credentials are stored encrypted at rest (AES-256-GCM) per workspace, never shared across customers, and rotated on request. The connection is scoped to the least-privilege set of scopes each playbook needs — you approve the scope list on install.
No. Your Guru data feeds only your workspace's own agents and answers. Nothing is used to train a shared model, and nothing crosses workspace boundaries. Bring-your-own-model is available on Enterprise if you want to pin inference to your own OpenAI / Anthropic / self-hosted deployment.
Yes. Every Guru integration is scoped at install time — you pick which resources, users, or record types are visible. You can further restrict per-playbook: a single playbook only touches the specific Guru objects it needs. Scope changes take effect on the next sync.
Every write is logged with the acting user, the playbook that fired it, the exact operation, the target entity IDs, and the timestamp — all in the immutable audit log. Writes are rehearsable in simulation mode against a copy of live data before they touch Guru for real.

Ready to connect Guru?

Start free. No credit card required. Connect your first integration in under 5 minutes.

Get started free