---
title: "Integrations"
description: "An integration in BRAIAN by AETERION is a scoped connection to a system a company already runs — SAP, Microsoft 365, Salesforce, ServiceNow, Slack, PostgreSQL, Snowflake, Jira. Connections are created per environment, expose named tools instead of raw credentials, and every call through them is recorded in the audit log."
url: "https://aeterion.tech/en/docs/integrations"
locale: "en"
publisher: "AETERION SA"
---
# Integrations

> An integration in BRAIAN by ÆTERION is a scoped connection to a system a company already runs — SAP, Microsoft 365, Salesforce, ServiceNow, Slack, PostgreSQL, Snowflake, Jira. Connections are created per environment, expose named tools instead of raw credentials, and every call through them is recorded in the audit log.

Source: https://aeterion.tech/en/docs/integrations
Last updated: 2026-09-20

## How do connections work?

A connection holds the credentials and the scope. It publishes named tools, such as sap.invoices.post, which agents may declare. An agent never receives the credential itself, only permission to call a tool.

```bash
braian connection create salesforce \
  --scopes opportunities.read,accounts.read \
  --env staging
braian connection tools salesforce
```

## Supported systems

- **SAP** — Purchase orders, invoices, vendor master records, posting with approval policies.
- **Microsoft 365** — Mail, calendar, SharePoint and Teams content within delegated scopes.
- **Salesforce** — Accounts, opportunities, cases and activity history.
- **ServiceNow** — Incidents, requests and change records.
- **Slack** — Escalation delivery and structured approvals in channel.
- **PostgreSQL and Snowflake** — Read access to operational and analytical data under field-level policies.
- **Jira** — Issues, transitions and comments for engineering and operations processes.

## Custom systems

Systems without a packaged connector are integrated through an HTTP connection that declares its own tools, authentication and rate limits. Custom tools behave like packaged ones: policy-checked, scoped per environment and audited.

> **Write scopes need a policy** — A connection with write scopes cannot be attached to an agent in production until at least one policy governs the writing tools.