Core concepts.

Workspace

A workspace brings together connections, settings and member access. Before acting, check which workspace you are using.

Connector and connection

A connector describes a service's capabilities. A connection is an authorized account in your workspace. They are different things.

Action and result

A tool has an input schema and a result schema. AI can make mistakes: check the selected account and the consequences of changes.

Tool, endpoint and session

A tool is an action with an input schema and a published identifier. An endpoint is a provider HTTP method with a path, parameters and JSON Schema; it is discovered separately and does not automatically appear among MCP tools. Proxy requests explains calling an endpoint through a connected account.

A session pins the available tool set and execution settings, including TTL, budget and read-only policy. An execution is a separate durable record of an individual call, its state, attempts and result. Neither a session's existence nor acceptance of a request means the provider operation succeeded.

End user

In a server integration, user_id associates actions with an application's end user. It is an opaque reference, not a field for email or personal data. Multiple users of one workspace can have separate accounts for the same service. A shared account is available only with appropriate sharing and ACL settings.