Slack
Post messages, read history, react, and resolve users on behalf of each user.
Every connector resolves a credential that belongs to one user, encrypts it at rest, classifies what flows through it, and writes an audit record for the call. Adding an integration never changes that contract.
Post messages, read history, react, and resolve users on behalf of each user.
Channel messages, chats, and meeting context under delegated permissions.
Read threads and send mail as the signed-in user, never a shared mailbox.
Guild channels, messages, and member lookups for community agents.
Schedule meetings and pull recordings and transcripts.
Conversations, contacts, and notes for support agents.
Programmable SMS and voice with per-tenant credentials.
Bot messaging, chat history, and file delivery.
Issues, pull requests, reviews, and repository contents.
Merge requests, pipelines, and project issues.
Issues, cycles, and project state for engineering agents.
Issue search, transitions, and comments across projects.
Error groups, stack traces, and release health.
Incidents, escalation policies, and on-call schedules.
Metrics, monitors, and log search for operational agents.
Repositories, pull requests, and pipeline runs.
Deployments, environment variables, and project state.
DNS records, zones, and edge configuration.
Send, receive, and delete queue messages.
One-time and recurring schedules for AWS targets.
Pages, databases, and block content with per-user access.
Availability, event creation, and invitee management.
Read and append rows without handing the model a service account.
Tasks, projects, and assignments across workspaces.
Boards, lists, and cards for lightweight workflows.
Tasks, custom fields, and space hierarchy.
Records, views, and schema across bases.
Space search, page contents, and structured updates.
Scheduled events, invitees, and availability windows.
Boards and items for collaborative planning agents.
Tasks, projects, and due dates for personal agents.
Accounts, opportunities, and SOQL under the rep’s own permissions.
Contacts, deals, and pipeline stages.
Tickets, macros, and customer history.
Deals, activities, and contact timelines.
Leads, modules, and records across the Zoho suite.
Warehouse queries bounded by the caller’s role, not a shared admin key.
SQL warehouses, jobs, and catalog metadata.
Events, funnels, and feature flag state.
Event queries, cohorts, and retention reports.
Property reports, dimensions, and audience data.
Saved questions, dashboards, and dataset queries.
Looks, explores, and modelled business metrics.
Text, forms, and tables extracted from documents.
File search, contents, and sharing under delegated scope.
Folder listing, file contents, and shared links.
Enterprise content with retention and classification intact.
Parameterised reads against a scoped role, never raw superuser SQL.
Collection queries and aggregations under a bounded user.
Tables and storage buckets with row level security respected.
List, read, write, copy, and delete objects with scoped IAM keys.
Customers, subscriptions, and payment intents. Writes stay read-confirmed.
Invoices, expenses, and chart of accounts.
Bank transactions, contacts, and reconciliation state.
Card transactions, budgets, and expense receipts.
Balances, transfers, and multi-currency accounts.
Orders, products, customers, and coupons on each merchant’s own store.
Shipments, rates, labels, voids, and package tracking.
Products, inventory, sales, manufacturing, and purchase orders.
Orders, acknowledgements, shipping updates, items, and inventory.
Dropship purchase orders, ship notices, inventory, and catalog.
EDI transactions, history, and shipping label batches.
Orders, catalog, FBA inventory, listings, and finances.
Audiences, campaigns, and send performance.
Orders, products, and customer records.
Transactional sends, domains, and delivery events.
CMS collections, items, and publish state.
Users, groups, and application assignments.
Tenant users, roles, and connection configuration.
Project vulnerabilities, licences, and fix advice.
Secret reads through a lease, with the audit trail preserved.
A connector client exposes an authenticated proxy. You keep the same credential resolution, encryption, and audit path while calling a route that has no typed tool yet, so an unmodelled endpoint never forces a plaintext token into your own code.
await client.proxy({
method: 'POST',
path: '/api/v2/anything',
body: { ... }
})Declare the auth method, the Zod input and output schemas, the OAuth scopes each tool needs, whether it reads or writes, and how its payload is classified. The runtime handles credential resolution, validation, redaction, and metering.
Requests from teams in the access queue decide what gets built next.