Skip to main content

Integrations

The Integrations area is where your team manages connected systems in XY. It is designed to help you see what is already connected, discover new connections, and expand the systems your workflows can use.

Interface Overview​

The current experience centers on three views:

Connected​

Use this view to review the integrations your organization is already using.

This is the best place to:

  • confirm what is active
  • open integration details
  • understand which workflows depend on a given integration
  • revisit configuration when something changes

Discover​

Use Discover to browse what is available for connection in your workspace.

The exact catalog can vary over time, but common categories include:

  • EHR and practice-management systems
  • email
  • cloud storage
  • collaboration tools

Custom​

Some workspaces also support Custom integrations. This gives organizations a path to create and manage integrations beyond the standard catalog.

Search, filtering, and categories​

The integrations experience is designed to help teams quickly answer:

  • What is already connected?
  • What can we add next?
  • Which category does this system belong to?
  • Which workflows depend on this integration?

Typical setup flow​

  1. Open Discover.
  2. Find the system you want to connect.
  3. Complete the connection flow.
  4. Return to Connected to verify the integration is ready.
  5. Use the integration inside a workflow.

Common integration types​

Storage integrations​

Storage connections such as Google Drive and OneDrive are often used as document sources for the Files area and for knowledge-base workflows.

Email integrations​

Email connections are often used for inbox-based workflows, attachment intake, and follow-up actions.

Business-system integrations​

Where a supported native integration exists, workflows can use that connection directly instead of relying on browser automation.

Browser-first systems​

If a system is primarily used through a web interface and does not have a practical native connection, teams can often automate it with the XY Browser Agent.

Best practices​

  • Start with the systems your most important workflows depend on.
  • Connect storage and document sources early if your workflows are file-heavy.
  • Use the least amount of access needed for the job.
  • Revisit your connected integrations as workflows change.