Connect external systems to a workspace.
Declare each external system as an integration definition: a driver, typed configuration, and a credential sealed on the host. Feeds bring its rows into collections, outbound rules send or submit records, and automations call it with ctx.request. Workspace policies still apply when apps or agents use the data.
One definition per external system: its driver (HTTP, SQL Server, WhatsApp, email, Telegram, Slack, Discord, WeChat or calendar), typed configuration, and credentials sealed on the host, never in workspace code.
Bring an external account’s rows into one collection, pulled on a schedule or pushed by the driver. Each page commits with its cursor in one statement, and the fields your team edits are never overwritten.
Send a message or submit a command for each committed record, once any approval is through. Each send is keyed so it happens once, and its delivery status reads on the record.
Call an instance with ctx.request or send through it with ctx.send. Each request is journalled, so a retried run does not repeat it.
Let approved users work through web chat, WhatsApp, or Telegram under workspace policies.
When there is no native connector
A system with an HTTP API or a SQL Server database connects through a definition on the http or sqlserver driver: feeds read from it on a schedule, outbound rules submit commands to it once per record, and automations call it with ctx.request. If neither is possible, map the remaining manual handoff before deciding whether browser automation is appropriate.