An integration connects an external system to an agent deployment or to Salambo’s operational data.

​
Integration types

TypeUse
Runtime APICall an agent from an application, script or service
Communication channelConnect Slack or Microsoft Teams to an agent
Provider credentialAllow the hosted worker or sandbox to call a model or external service
Observability exportSend runtime traces to an OTLP HTTP receiver
Deployment automationDeploy agent source from CI

​
Common request flow

​
Integration ownership

Before setup, decide:
  • which workspace owns the integration;
  • which agent deployment receives work;
  • who owns the external application or bot;
  • where credentials are stored;
  • whether credentials belong in the worker runtime or sandbox;
  • which external hosts are required;
  • how credentials are rotated and revoked;
  • which run evidence proves the integration is healthy.

​
Standard verification

Every integration should prove:
  1. External authentication succeeds.
  2. The intended workspace and agent are resolved.
  3. A run and response are created.
  4. Provider or extension execution completes.
  5. The response returns to the external system.
  6. Activity and Diagnostics contain the expected sanitized lifecycle evidence.
For failures, locate the stage first: 
external delivery
  -> authentication
  -> admission
  -> provider
  -> sandbox
  -> response delivery
Then use the integration guide and run diagnostics for that stage.