Skip to main content
Start with the result you need. Connect can inspect the library, read public documentation and investigate packages beyond it.

​
What to include in your request

  • Work: the read, update, message or other result you need.
  • Resources: relevant repositories, channels, documents or databases.
  • Account: the workspace or service account to use.
  • Audience: who should receive or see the result.
  • Lifetime: one task or continuing access.
A service name, URL or remembered package name can help the investigation. You can also describe the task without choosing the integration yourself.

​
How a selection is made

The agent compares the available operations with the request, checks configuration and account prerequisites, and selects a concrete package and version. Code validates the package, dependencies and host requirements. The host presents the installation and access for review. A service can offer multiple integration routes. Choose the route that exposes the required operations and fits your deployment. For an existing account connection, reuse its authorized operations when they meet the task. See ask for an integration for the user flow and discovery tools for the API.