V
Comms / Collaboration

Valley AI Integration

Connect Valley to BeforeQuery for grounded AI answers and agent actions across Comms / Collaboration.

Connect Valley
What is it?

About Valley

Valley is one of the Comms / Collaboration 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 Valley

  1. Step 01

    In the BeforeQuery dashboard, go to Integrations → Comms / Collaboration and select Valley.

  2. Step 02

    Sign in to Valley with an account that has permissions to grant BeforeQuery the Comms / Collaboration scopes required.

  3. Step 03

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

Explore

Related integrations

AS
Acuity Scheduling

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

A
Adobe

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

A
Amazon

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

How BeforeQuery uses Valley

What the agent does with your Valley connection

  • 01

    Deliver AI answers inside Valley — no context switching to a separate tool.

  • 02

    Read + respond to Valley messages via bots, DMs, or channel mentions.

  • 03

    Trigger playbooks from Valley events — slash commands, buttons, or specific phrases.

  • 04

    Send targeted, personalized notifications from any playbook into Valley.

Use cases

What teams actually do with the Valley integration

In-channel AI assistant

Employees @mention the BeforeQuery bot in Valley and get grounded answers from your knowledge base right in the thread. Cited sources are one click away. Zero context switching.

Slash-command playbook launcher

Custom slash commands (or Valley-native equivalents) trigger any playbook: /pto to file a leave request, /order-laptop to order hardware, /grant-access to request JIT access. Playbook drives the conversation.

Targeted announcements

A playbook drafts a message, targets it to the right Valley channel or user segment (role, team, tenure), and sends. Recipients get relevant messages; noise stays low.

Answer questions grounded in Valley

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

Valley — Frequently Asked Questions

Common questions about connecting BeforeQuery to Valley.

No. The bot only reads messages it's directly addressed in (DMs, @mentions, replies to its own messages). Ambient channel traffic is invisible unless a playbook is explicitly configured to watch a channel.
Yes. Per-channel and per-workspace scoping is standard. Enterprise Grid customers can scope to specific enterprise-level workspaces or teams.
Standard OAuth 2.0 where Valley 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 Valley 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 Valley 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 Valley 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 Valley for real.

Ready to connect Valley?

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

Get started free