# Accurate OAuth connection results instead of popup guesses

> The dashboard now asks the server how each connect attempt ended, so failed or abandoned connections no longer count as success.

Oct 6, 2026. Topics: Integrations. https://www.generalinput.com/changelog/2026-10-06-oauth-connect-outcomes

Connecting an integration from the dashboard, or from a connect card in chat, now reports what actually happened. The server records how every connect attempt ended, and the dashboard waits for that answer instead of inferring it from the sign-in popup.

Before this change, the dashboard learned the result through a message from the popup. The browser security policy both the dashboard and the API send cuts that link, so the message often never arrived, and the fallback treated a closed-looking popup as success. In practice, failures and abandoned popups counted as connected, and a chat connect card could resume a specialist with no credential at all.

### How it works

- **One attempt, one record.** Starting a connection returns an attempt ID alongside the sign-in link, for every kind of OAuth connection.
- **A status check.** The dashboard checks the attempt every second until it's completed (with the new credential), failed (with its error), or expired after 10 minutes.
- **Owner-only.** Only the member who started an attempt can read it.
- **Security headers unchanged.** We kept the strict browser policy and moved the source of truth to the server.

### Also shipped

- New integrations: DocuWare, with a new-document trigger, and TalentLynk, with a campaign-status trigger.