Connections & Access

Connections & Access

• Connections and approvals → First-use flow for integrations and approving actions.

• Integrations & connections → Supported integrations and how they are authorized.

---

Connections and Approvals

AI Employees often rely on external integrations and require user approval before performing certain actions. This section outlines how connections are established and how approvals work.

Rule	Details
First-use flow (chat)	When an AI Employee is prompted in chat to use an integration for the first time, Motion prompts the user to connect the service (e.g., Google Calendar, Slack). The connection is then available for reuse.
First-use flow (skills)	When configuring a skill that uses a third-party service, Motion requires the integration to be authenticated before the skill can run.
Approval before write operations	AI Employees cannot create, edit, or delete data in Motion or integrated services without user approval. Approvals may be required each time or persist depending on workspace settings.
Connection scope	Integrations are authorized at the workspace level, not the individual level. All AI Employees in the workspace share the same configured connection.
Third-party blocks	If a skill uses a third-party block, the AI Employee runs it through the configured connection. The action succeeds or fails depending on the permissions of that connection.
Revoking connections	Workspace admins can revoke or update integrations at any time. Once revoked, dependent skills and actions will fail until reconnected.

Integrations & Connections

AI Employees rely on integrations to act across external systems. Connections define which third-party services are available and under what permissions.

Feature	Details
Supported integrations	AI Employees can connect to workspace-enabled services such as Google Calendar, Slack, Microsoft Teams, Zoom, email providers and many more. Supported services expand as new blocks and skills are added.
Workspace-level connections	Integrations are authorized at the workspace level. Once connected, all AI Employees in that workspace can use the integration.
Connection ownership	The integration uses the account that authenticated it during setup (e.g., a shared service account or an admin’s account).
First-use behavior	When a skill or chat request calls for an unconnected service, Motion prompts the user to authenticate the integration. The connection persists for future use.
Third-party blocks	Skills that depend on third-party services (e.g., sending a Slack message) always execute through the configured connection. If the connection lacks permissions, the action fails.
Revocation	Workspace admins can revoke or update integrations at any time. Revoking immediately disables all dependent AI Employee actions until reconnected.