@alter-ai/slack

Install npm install @alter-ai/sdk @alter-ai/slack.

Construct SlackIntegration(app, { grantId }) with an Alter App client. All 80 operations use immutable contract 2026-10-28. OAuth and managed-secret/API-key grants use the same binding and controls when the provider supports that credential type. Requests are authorized, validated, and routed by the backend. Await call.wait() to handle immediate results and approvals, then decode with result.bodyJson(). This distribution contains only this provider's native types and response schemas.

Public API reference includes every operation's input/output fields and both SDK examples.

Resume after a process restart

Persist the pending call's approvalId (TypeScript) or approval_id (Python) in your durable job record. After restarting, construct a fresh provider client:

const resumed = await provider.resume(savedApprovalId);
const result = await resumed.wait();
const body = result.bodyJson();

resumed = await provider.resume(saved_approval_id)
result = await resumed.wait()
body = result.body_json()

The backend supplies the stored provider, operation and immutable contract version. The provider package verifies provider/version and applies that operation's validator and fault handling. Mismatches raise ManagedOperationError with managed_approval_contract_mismatch or managed_approval_operation_mismatch. The ID yields a union of operation outputs; TypeScript callers can narrow the call by resumed.operation. No operation or version is accepted from the caller.

Generic app.integrations.resume(id) preserves raw response access and exact-number decoding; use the provider package for its response validator. Both use the existing approval poll's proxy:execute or approvals:read permissions and app/agent isolation. Resume also works after execution while the result is retained. Denial, expiry, execution failure and result purging retain the existing approval errors. Resume never resubmits the request. Raw approvals or missing stored identities fail with managed_approval_identity_unavailable.

Connect with a bot token

A workspace that installs its own Slack app can store that app's Bot User OAuth Token (xoxb-…) in Alter as a Slack managed secret instead of completing OAuth Connect consent. Pass that managed secret's grant ID as grantId (TypeScript) or grant_id (Python). The same methods, validation, policy and approvals apply, and the token can call only what its Bot Token Scopes allow, in the channels the bot belongs to. The Slack managed secret guide lists the setup steps.