Connections
Manage the providers and credentials that make your real customer path work.
Manage the providers and credentials that make your real customer path work.
What this feature is for
Connections is the credential and provider setup surface for Stripe, Supabase, auth, deploys, email, analytics, alerts, and other integrations. The important distinction is that PreFlight stores the observation alongside the app, release, provider, or customer path it belongs to. That context is what turns a signal into an operational decision.
Before you open it
The provider account, least-privilege credential, target app, and a decision about test versus production mode.
Use a real app in the workspace and start with the smallest useful scope. A narrow, representative check gives you a stronger baseline than connecting every environment and every provider at once.
Run the workflow
Choose a provider, enter only the requested fields, save, run its purpose-built probe, and rotate or disconnect when the relationship changes.
- Open the feature from the dashboard outcome hub.
- Choose the app and environment that match the decision you are making.
- Run or save the configuration, then wait for the evidence state to settle.
- Assign the next action to an owner before leaving the page.
Read the evidence
A connection records provider identity, check status, last verification, and safe error details without exposing the secret again. A green state means the configured assertion passed at the recorded time. It does not claim that every unconfigured path is healthy. A warning is a useful lead; a failure should have a concrete owner and a verification run.
When the result is not healthy
A successful credential check does not guarantee the downstream customer behavior. Add a journey, custom check, or payment test where the provider participates in a larger flow.
Do not erase the failed result after fixing the underlying system. Keep the history, rerun the check, and link the new passing evidence to the deployment or incident that caused the change. This gives the team a useful before-and-after record.
Use it with the rest of PreFlight
Use Connections with Provider probes, Audit, Revenue, and Health. Outcome hubs are deliberately connected: Audit finds risk, Deploy decides whether to promote, Health watches the running system, Revenue verifies the money path, Growth manages discoverability, and Trust publishes safe proof. Use the related links below to move between those decisions without losing context.