Connect your private Stack Overflow for Teams instance and BeforeQuery indexes its questions and answers. Internal Q&A your engineers already wrote becomes retrievable through chat, search, and every deployed surface — with citations back to the original thread.

​
Prerequisites

  • A Stack Overflow for Teams instance and its team slug (the identifier in your team URL).
  • A Stack Overflow for Teams API access token with read access (create one from your Teams account settings).
  • A BeforeQuery workspace owner role.

​
Data ingested

One question, one document:
  • Question URL on your team site, and its title
  • Tags
  • The question body
  • The accepted answer, where the question has one
Questions with no accepted answer are still indexed — the question text alone often matches how the next person asks it.

​
Set up the connector

1

Create an API token

In Stack Overflow for Teams, generate a personal access token that can read your team’s questions and answers.
2

Add the source

In the dashboard, open Knowledge Base → Sources → Add source and choose Stack Overflow. Enter your team slug and paste the API token, then click Add.
3

Verify in the Playground

After the first sync completes, ask a question you know is answered in your Teams instance and confirm the citation links back to the Q&A thread.

​
Connection settings

​
Keeping content in sync

Stack Overflow re-syncs every hour — there is no schedule to configure, and Sync on the source’s page runs one now if you cannot wait. Only changed content is re-embedded. See Sources Overview.

​
Troubleshooting

  • Sync fails with an auth error? The token was revoked or lacks read scope — issue a new one and update the source.
  • Internal Q&A leaking into public surfaces? Mark the resulting documents restricted, or isolate the source in an internal-only source group that public client keys can’t access.