Why connection strategy matters
An agent job is only as reliable as its app connections. If the required app is missing or expired, validation and deployment stall until the connection issue is dealt with.
The safest public claim boundary here is not a generic guide to every auth method on the internet. It is the actual product flow: auth gaps, current connect actions, verified connection status, and reconnect handling when a connection expires.
Connection steps
1. Let the plan tell you what is missing
Start with the workflow, not the integrations page. If the builder needs an app before validation or deploy can proceed, it will surface that as an auth gap.
That keeps connection work tied to the actual workflow instead of connecting tools you may not use.
2. Use the current in-product connection flow
Connect apps from the builder or from the integrations screen. The current product flow is designed to confirm whether the connection actually completed before you treat the app as ready.
3. Verify the app is ready before deploy
After the popup or connection flow finishes, make sure the app is actually connected. Do not move on just because the auth window opened.
4. Reconnect when an app needs attention again
If an app later needs reconnect work, treat that as an operational issue instead of pushing ahead. The safe public claim is simply that app connections can need attention again, and you should confirm the app is ready before you rely on the agent.
5. Keep the connected-app list aligned with the job
Once the agent is live, the connected apps shown on the agent should still match what the plan needs. If an app is no longer used, remove that dependency from the plan instead of letting the connection sprawl.
Connection surfaces
| Surface | Use it for | What it tells you |
|---|---|---|
| Builder auth gaps | See which apps block validation or deploy | Shows exactly what the current agent job still needs |
| Connect actions | Open the current connection flow for that app | Helps you connect and verify instead of guessing |
| Integrations screen | Review current connected and disconnected apps | Gives you one place to reconnect or confirm status |
| Connection status and reconnect prompts | Act when a live connection needs attention again | Tells you an app needs attention before you rely on it again |
Best practices
- Start from the workflow. Connect only the apps the current plan actually needs.
- Use the current in-product flow. Let the app open and verify the connection instead of treating auth as a manual side task.
- Verify after connecting. A popup opening is not the same thing as a completed connection.
- Reconnect when an app needs attention.Confirm the app is ready again before you rely on the agent.
- Keep claims precise. Stay with the connection and reconnect flow the product currently proves.
Frequently asked questions
How do I know what apps I need to connect?
The builder shows auth gaps when an agent job needs a connection before validation or launch can continue. Start there instead of guessing.
Where can I connect apps?
Use the connect actions inside the builder when a plan has auth gaps, or connect apps directly from the integrations screen in the app.
What happens if a connection expires or breaks?
Treat it as reconnect work inside the product. The safe public claim is that an app can need attention again after the first connection, and you should confirm the app is ready before relying on the agent.
Can one agent use more than one connected app?
Yes. The plan can include multiple connected apps when the workflow needs them, but each app should be connected and verified before deployment.