A reusable library of tenant-owned OAuth connections. Fire Slack, email, calendar, Sheets, or any future integration — in parallel with your AI agent workflows, with zero shared credentials and zero UI rebuilds.
Every capability below ships in production today. Expand each card to see the implementation.
Build once. Attach anywhere.
Every connector is a named, pre-configured operation with its parameters saved. Build a 'Send WhatsApp Confirmation' definition once, and every restaurant on your tenant attaches it with one click.
Tenant-owned accounts. Zero shared credentials.
Each tenant brings their own Google Workspace, Slack, or HubSpot account. Sageion never sees a password — only an OAuth token, encrypted per-tenant, in its own Secrets Manager namespace.
New connectors ship without any UI changes.
Every operation describes its own parameter schema. The admin's post-trigger editor generates the form from that schema. When we ship Slack or Stripe tomorrow, they appear instantly — no frontend deploy required.
Separate stack. Separate IAM. Separate secrets.
The connector handler runs on its own Lambda, its own API Gateway, its own SQS queue with DLQ, and its own IAM role. OAuth credentials never mix with tenant data. Credential rotation is one CloudFormation deploy.
Every provider below is a first-class operation. The admin's post-trigger editor auto-generates its form from the operation's schema.
append_rowAppend row to sheetlist_spreadsheetsList spreadsheetslist_tabsList sheet tabssend_asSend email from connected Gmailcreate_eventCreate calendar eventpost_messagePost message to channelsend_dmSend direct messagesend_templateSend template messagesend_mediaSend media messagecreate_payment_linkCreate payment linkrefund_paymentRefund a paymentcreate_contactCreate contactcreate_dealCreate dealany_http_endpointAny HTTP endpointThe tenant admin clicks Connect Google (or Slack, or any future provider). PKCE, state, audience, and issuer are all verified automatically.
{Prefix}/sageion/oauth-token/... — encrypted, tenant-scoped, never shared.The admin builds a named connector definition — e.g. "Send WhatsApp confirmation" — and fills in its parameters from the auto-generated schema form.
Attach the definition to any chain node or leadgen form. It fires to a separate SQS queue with its own DLQ, in parallel with the main flow.
The connector stack runs on its own deployment — separate IAM, separate secrets, separate queue. OAuth credentials never mix with tenant data.
60-second timeout, narrow IAM, dedicated execution role. Cannot access AutoBot's data except through read-only paths.
Provider credentials live at {Prefix}/sageion/oauth-provider/*. Tenant tokens live at {Prefix}/sageion/oauth-token/*. Never shared.
With a dedicated DLQ. Failures retry 5 times, then archive to DLQ with 14-day retention — visible to operations, never to the end user.
The connector can read -AutoBotData and -ScopeAttachments to verify ownership. It can never write to either.
Every connector is a schema-driven operation — adding a new one never requires an admin UI change. Tell us which provider you need, and it ships in the next release.