Different connections do different jobs

An email connection may let a colleague send a message or preview mailbox items. An API gives software a defined way to request data or perform supported actions. A webhook delivers a supported event to another service so that a workflow can respond.

These capabilities are not interchangeable. A data preview does not imply a continuous two-way synchronisation, and access to one action does not imply access to every record or mailbox.

Set up the connection deliberately

  • Confirm which plan includes the connection.
  • Identify the provider account and administrator approval needed.
  • Choose the permissions and actions required for the job.
  • Test the supported flow before relying on it with customers.

For example, an organisation can approve Microsoft access before each colleague consents to their own mailbox connection. Shared organisation approval and individual mailbox access serve different purposes.

Check the practical scope

Before choosing an integration, ask which objects, fields and actions it supports, how failures are handled and whether another service needs configuration. Keep a clear owner for credentials and provider-side app settings.

HOW THIS RELATES TO ATLAS

In the current workspace

Atlas provides plan-gated SMTP, Microsoft 365, Salesforce and webhook setup. Microsoft consent and service credentials are required. Salesforce currently supports discovery and bounded extraction/staging flows, not continuous two-way sync.

Explore the product

Atlas feature scope reviewed 17 October 2026. Plan availability and connection setup apply.