Provider probes

What this feature is for

Provider probes are purpose-built checks for credentials, auth endpoints, webhook delivery, deployment providers, email, analytics, and other connections. They test provider-specific success conditions instead of sending a generic ping. 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

A connected provider, the minimum credential scope it requires, and a test-safe target such as a channel or test endpoint.

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 the provider, review the requested fields, save the connection, and run the probe. Open the fix guidance when a check fails and rerun after the provider-side correction.

1. Open the feature from the dashboard outcome hub.
2. Choose the app and environment that match the decision you are making.
3. Run or save the configuration, then wait for the evidence state to settle.
4. Assign the next action to an owner before leaving the page.

Read the evidence

The result records pass, warning, or failure, a safe error code, and timing or response evidence where the provider supplies it. 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

Never paste a production secret into a browser log or commit it to source. Rotate exposed credentials and reconnect with the smallest scope that supports the check.

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

Connect provider probes to Alerts for delivery, Activity for history, and Deploy when a provider is on a release-critical path. 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.