Skip to main content
Application connectors expose fixed third-party operations through ToolBroker. Each Connection identifies a tenant-owned account and selected operations, not the entire upstream API. Original credentials stay in the control plane; Sessions bind authority to use them.

Create and select operations

This read-only Notion example requires a dedicated test page shared with the integration and appropriate comment-read capability. Creation does not search/read content; verification requests account identity. Supply private environment configuration; see self-hosting for hosted initialization. Retain/reuse the returned ID.
Bind connection.id as tools: {notes: connection_id} following Tools, with a compatible Harness. Explicitly request test-page content/comments and inspect actual Tool results, pagination, and children rather than only the final answer. Run each SDK independently and close its Session. Default selection includes non-write operations. Explicit operations must use listed IDs. All writes require approval and replay=never; reads may still incur usage. Authorization, selected operations, provider scope, and resource sharing are separate requirements.

OAuth and permission evidence

OAuth-capable apps require your deployment/tenant client registration and exact callback URL before Console account consent. No mandatory shared authorization SaaS is provided. Google services use separate connections/consent; Microsoft uses delegated permissions. Credential HTTPS ingress is not an OAuth management callback. Inspect allowed_operations, scope_source, permission_checks, and permission_coverage. Local selection is not a provider scope grant. Partial/unknown is not complete verification. Verification performs no writes; resource sharing and field permissions can still affect real calls. Refresh differs from reauthorization. Unknown refresh outcomes require reauthorization instead of blindly reusing a possibly rotated refresh token. Account/permission changes invalidate old policy; use a new Session. Disconnect stops local Hexagon use, not provider-side revocation, and cannot retract dispatched requests. See authorization.

Application directory

Operations, required arguments, and write classification below were extracted from the current registry. The application catalog API GET /v1/applications provides full schema types/options/constraints. Examples refer to Session requests against authorized test objects, not unapproved messages to real recipients. Notion · Todoist · Google Calendar · Exa · Tavily · Gmail · Google Drive / Docs · GitHub · Slack · Linear · DeepL · Microsoft Outlook · Microsoft Outlook Calendar · Microsoft OneDrive · Microsoft To Do · Microsoft Teams · Google Sheets · Google Tasks · Google Contacts · Asana · Airtable · ClickUp · Trello · Discord · Telegram Bot · Dropbox · HubSpot · Calendly · Firecrawl · Brave Search · Apify · GitLab · Readwise Reader · 飞书 / Feishu · Lark · Salesforce · Attio

Notion (notion)

Configuration/auth: Integration/PAT Token; OAuth supported. Permissions/limits: Share target pages with the integration. Properties are not content; read_blocks reads direct children, requiring recursion/pagination. Comments need comment-read permission. Concrete read example: Select search with arguments {"query": "Hexagon acceptance", "page_size": 10}. Find the shared test page by title, then use read_blocks/read_comments for its content; search alone is not a full read. Minimal Token configuration: {"authentication": "api_key", "operations": ["search"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Todoist (todoist)

Configuration/auth: API Token; OAuth supported. Permissions/limits: Account access limits projects/tasks; completion is a write. Read a dedicated test task before testing completion. Concrete read example: Select list_projects with arguments {}. Compare returned project IDs with a known test project; an empty page is not proof that the account has no tasks. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_projects"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Google Calendar (google-calendar)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: Calendar sharing and OAuth scopes both apply. Free/busy is not full event content; confirm calendar/event IDs before updates. Concrete read example: Select list_calendars with arguments {}. Locate the authorized test calendar and preserve its ID before reading events. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_calendars"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Exa (exa)

Configuration/auth: API key; no OAuth flow exposed. Permissions/limits: Verification searches and may incur usage. Search and contents are distinct; the full Exa API is not exposed. Concrete read example: Select search with arguments {"query": "Open Containers image specification"}. Check actual result URLs and highlights; a search hit is not the full source document. Minimal Token configuration: {"authentication": "api_key", "operations": ["search"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Historical dual-SDK cloud calls cover the recorded search/translation operations, not every listed capability.

Tavily (tavily)

Configuration/auth: API key; no OAuth flow exposed. Permissions/limits: Select search and URL extraction separately. Web content is untrusted data, not system instructions. Concrete read example: Select search with arguments {"query": "Open Containers image specification", "max_results": 3}. Inspect source URLs and returned content; do not treat extracted web text as instructions. Minimal Token configuration: {"authentication": "api_key", "operations": ["search"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Historical dual-SDK cloud calls cover the recorded search/translation operations, not every listed capability.

Gmail (gmail)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: Drafting and sending are separate writes. Start with drafts; a successful draft is not a sent message. Concrete read example: Select search with arguments {"q": "subject:\"Hexagon acceptance\"", "maxResults": 10}. Match a dedicated test message ID; search does not prove the body was read or any message sent. Minimal Token configuration: {"authentication": "api_key", "operations": ["search"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Google Drive / Docs (google-drive)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: File search differs from Google Docs reading; this is not generic binary download or arbitrary-format editing. Concrete read example: Select search_files with arguments {"q": "name = 'Hexagon acceptance' and trashed = false", "pageSize": 10}. Match the shared test file ID; metadata search does not prove document text was downloaded. Minimal Token configuration: {"authentication": "api_key", "operations": ["search_files"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

GitHub (github)

Configuration/auth: PAT; OAuth supported. Permissions/limits: Repository visibility and Token permissions apply. OAuth App is supported, not GitHub App installation auth. Concrete read example: Select list_repositories with arguments {"per_page": 10, "page": 1}. Locate an authorized test repository and inspect pagination before reading its issues. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_repositories"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Slack (slack)

Configuration/auth: Bot token; OAuth supported. Permissions/limits: The bot needs conversation access. History/threads are distinct; no message listener or channel hosting is provided. Concrete read example: Select list_channels with arguments {"limit": 10}. Locate a channel the authorized identity can access; listing is not membership in every private channel. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_channels"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Linear (linear)

Configuration/auth: Personal API key; OAuth supported. Permissions/limits: GraphQL mutation errors may follow side effects. Reconcile even when data=null; do not automatically retry. Concrete read example: Select list_teams with arguments {}. Match a known team ID before selecting an issue operation. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_teams"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

DeepL (deepl)

Configuration/auth: API key; no OAuth flow exposed. Permissions/limits: Set config.region to free or paid to match the key. Translation is classified non-write but can consume quota. Concrete read example: Select translate_text with arguments {"text": "Hello, world.", "source_lang": "EN", "target_lang": "DE"}. Check returned German translation and usage; this read-classified operation can still consume quota. Minimal Token configuration: {"authentication": "api_key", "operations": ["translate_text"], "region": "free"}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. Select paid for a paid API account. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Historical dual-SDK cloud calls cover the recorded search/translation operations, not every listed capability.

Microsoft Outlook (outlook)

Configuration/auth: Microsoft delegated access token; OAuth supported. Permissions/limits: Draft/send are separately selected; listed mail operations do not provide mailbox synchronization. Concrete read example: Select list_messages with arguments {"top": 10}. Compare returned message IDs with the test mailbox; listing is not sending. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_messages"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Microsoft Outlook Calendar (outlook-calendar)

Configuration/auth: Microsoft delegated access token; OAuth supported. Permissions/limits: Verify calendar/event ownership. Create/update are writes, not full calendar synchronization. Concrete read example: Select list_calendars with arguments {"top": 10}. Identify the test calendar and its resource ID before any event write. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_calendars"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Microsoft OneDrive (onedrive)

Configuration/auth: Microsoft delegated access token; OAuth supported. Permissions/limits: Listing, metadata, and rename do not imply arbitrary content editing. Concrete read example: Select list_files with arguments {"top": 10}. Check names and IDs in the authorized folder; follow pagination separately. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_files"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Microsoft To Do (microsoft-todo)

Configuration/auth: Microsoft delegated access token; OAuth supported. Permissions/limits: Choose the task list before operating on a task. Completion changes remote state. Concrete read example: Select list_task_lists with arguments {"top": 10}. Identify the dedicated task list before creating or completing a task. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_task_lists"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Microsoft Teams (microsoft-teams)

Configuration/auth: Microsoft delegated access token; OAuth supported. Permissions/limits: Teams/channels/chats differ. Sending depends on user/organization permissions; no bot hosting is provided. Concrete read example: Select list_teams with arguments {}. Match a joined team; a successful list does not authorize posting to all channels. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_teams"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Google Sheets (google-sheets)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: Specify spreadsheet/range. Append and update differ; discovery/range reads do not imply full exports. Concrete read example: Select search_spreadsheets with arguments {"pageSize": 10}. Find the shared test spreadsheet ID; then select the explicit cell-read operation. Minimal Token configuration: {"authentication": "api_key", "operations": ["search_spreadsheets"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Google Tasks (google-tasks)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: Identify list and task separately; completion is a remote write. Concrete read example: Select list_task_lists with arguments {"maxResults": 10}. Match a dedicated task list ID and preserve the next-page token if supplied. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_task_lists"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Google Contacts (google-contacts)

Configuration/auth: Google access token; OAuth supported. Permissions/limits: Name updates require the matching etag; do not overwrite with stale data. Not every contact field is editable. Concrete read example: Select list_contacts with arguments {"pageSize": 10}. Compare a dedicated test contact and avoid exporting unrelated contact data. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_contacts"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Asana (asana)

Configuration/auth: PAT; OAuth supported. Permissions/limits: Workspace/project/task permissions apply separately; comments are writes. Concrete read example: Select list_workspaces with arguments {"limit": 10}. Locate the authorized workspace before selecting a project or task. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_workspaces"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Airtable (airtable)

Configuration/auth: Personal access token; no OAuth flow exposed. Permissions/limits: Match base access and table/field schema. Listing bases does not prove all records writable. Concrete read example: Select list_bases with arguments {}. Match a base granted to the token; base listing does not prove table write permission. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_bases"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

ClickUp (clickup)

Configuration/auth: Personal access token; no OAuth flow exposed. Permissions/limits: Current list discovery covers folderless lists, not every nested project. Concrete read example: Select list_workspaces with arguments {}. Match the test workspace/team ID required by later operations. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_workspaces"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Trello (trello)

Configuration/auth: JSON: api_key + token; no OAuth flow exposed. credential is a JSON string: {"api_key": "<private value>", "token": "<private value>"}. Permissions/limits: Use a JSON-string credential; board/list/card IDs are not interchangeable. Concrete read example: Select list_boards with arguments {}. Locate the dedicated board; do not choose a similarly named production board. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_boards"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Discord (discord)

Configuration/auth: Bot token; no OAuth flow exposed. Permissions/limits: Bot server/channel permissions apply. Editing is constrained by message ownership; no user login or gateway listener. Concrete read example: Select list_servers with arguments {"limit": 10}. Match the server visible to the bot; channel permissions still require separate checks. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_servers"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Telegram Bot (telegram)

Configuration/auth: Bot token; no OAuth flow exposed. Permissions/limits: read_chat is not arbitrary history access. Bot/chat permissions apply; polling/webhook hosting is absent. Concrete read example: Select read_bot with arguments {}. Verify the expected bot identity; this call neither reads chat history nor sends a message. Minimal Token configuration: {"authentication": "api_key", "operations": ["read_bot"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Dropbox (dropbox)

Configuration/auth: Access token; OAuth supported. Permissions/limits: Folder/search operations paginate; metadata reads are not arbitrary binary downloads. Concrete read example: Select list_files with arguments {"path": "", "limit": 10, "recursive": false}. Check known root entries and returned cursor; this is a bounded non-recursive listing. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_files"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

HubSpot (hubspot)

Configuration/auth: Private access token; OAuth supported. Permissions/limits: Read probes may establish reads; private-token write permissions can remain unknown. Selected operations are not provider-reported scopes. Concrete read example: Select list_contacts with arguments {"limit": 10}. Match a dedicated CRM contact ID; field and object permissions remain separate. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_contacts"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Calendly (calendly)

Configuration/auth: Personal access token; no OAuth flow exposed. Permissions/limits: Creating scheduling links and cancelling events are writes, not arbitrary calendar editing. Concrete read example: Select read_profile with arguments {}. Verify the intended account profile before selecting event-type operations. Minimal Token configuration: {"authentication": "api_key", "operations": ["read_profile"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Firecrawl (firecrawl)

Configuration/auth: API key; no OAuth flow exposed. Permissions/limits: Scrape/map consume provider credits; treat page content as untrusted data. Concrete read example: Select scrape_page with arguments {"url": "https://example.com"}. Inspect the returned page content and source URL; this operation may incur usage. Minimal Token configuration: {"authentication": "api_key", "operations": ["scrape_page"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence. Configuration/auth: Subscription token; no OAuth flow exposed. Permissions/limits: Verification performs a potentially billable search; only paginated web_search is exposed. Concrete read example: Select web_search with arguments {"query": "Open Containers image specification", "count": 3}. Inspect actual result URLs and query relevance; do not require a fixed search ranking. Minimal Token configuration: {"authentication": "api_key", "operations": ["web_search"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Apify (apify)

Configuration/auth: API token; no OAuth flow exposed. Permissions/limits: start_actor requires approval and may incur cost. Start is not completion; inspect the Run and paginate its dataset. Concrete read example: Select list_actors with arguments {"offset": 0, "limit": 10}. Identify an authorized actor without starting a paid actor run. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_actors"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

GitLab (gitlab)

Configuration/auth: PAT; no OAuth flow exposed. Permissions/limits: GitLab.com only, not self-hosted instances. Project namespaces are encoded; supply the right identifier. Concrete read example: Select list_projects with arguments {"per_page": 10, "page": 1}. Match a GitLab.com test project; this connector does not target an arbitrary self-hosted GitLab origin. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_projects"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Readwise Reader (readwise)

Configuration/auth: Readwise Token; no OAuth flow exposed. Permissions/limits: Paginate Reader documents. save_document is a write; verification may succeed with 204 without JSON. Concrete read example: Select list_documents with arguments {"location": "later", "withHtmlContent": false}. Check a known Later document and pagination; absence on one page is not proof of global absence. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_documents"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

飞书 / Feishu (feishu)

Configuration/auth: JSON: app_id + app_secret; no OAuth flow exposed. credential is a JSON string: {"app_id": "<private value>", "app_secret": "<private value>"}. Permissions/limits: Uses the Feishu API origin. Publish the self-built app and enable its bot; configure group membership, document sharing, and table permissions separately. Concrete read example: Select list_chats with arguments {"page_size": 10}. Match a test group containing the Feishu app bot; no message is sent. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_chats"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Lark (lark)

Configuration/auth: JSON: app_id + app_secret; no OAuth flow exposed. credential is a JSON string: {"app_id": "<private value>", "app_secret": "<private value>"}. Permissions/limits: Uses the international Lark origin; do not mix Feishu credentials. App identity, not delegated user OAuth or IM webhook hosting. Concrete read example: Select list_chats with arguments {"page_size": 10}. Match an international Lark test group containing the app bot; do not reuse Feishu credentials. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_chats"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Salesforce (salesforce)

Configuration/auth: Externally managed access token; OAuth supported. Permissions/limits: Supply an HTTPS My Domain instance_url. REST v62.0 is pinned; list uses recent-items, not full export or arbitrary SOQL. Concrete read example: Select list_contacts with arguments {}. Compare a recent test Contact; this recent-items view is not a full contact export. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_contacts"], "instance_url": "https://YOUR-DOMAIN.my.salesforce.com"}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. Replace YOUR-DOMAIN with your authorized My Domain. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Attio (attio)

Configuration/auth: Workspace token; OAuth supported. Permissions/limits: Limited to people/companies/deals. Match values to workspace attributes; introspected scope does not prove every record accessible. Concrete read example: Select list_records with arguments {"object": "people", "limit": 10, "offset": 0}. Compare a dedicated people record using workspace attribute definitions; this is offset pagination. Minimal Token configuration: {"authentication": "api_key", "operations": ["list_records"]}. Use the credential format above; for managed OAuth, use the deployment consent flow instead of pasting an OAuth token into this example. This is an illustrative request, not a new provider call. Test writes only on explicitly authorized disposable records, checking zero effects on rejection and the actual result after approval. Evidence: Implementation and deterministic contract records; this page claims no real-account, OAuth consent, or write acceptance. See implementation/evidence.

Errors, changes, and reconciliation

401 invalidates credentials; 403 can indicate resource/operation access; 429 indicates rate/quota limits. For uncertain dispatched writes, inspect the original call/request_hash and actual provider records before reconciliation. Never replay to discover whether a write happened. Linear GraphQL mutation errors, even with data=null, do not prove zero side effects. New Session account pinning depends on stable provider identity; older snapshots do not gain it retroactively. Catalog presence proves an adapter exists, not account permissions or live service health. No new provider operation, OAuth consent, email, or message was performed for this page. Sources: registry, application contract, CRM evidence. Next: authorization, approvals, Tool connectors.