Integration

Integrations

BaseLLM sends important events to Slack, Teams, email or your own systems through a webhook. Connections are added from the Catalog tab on the panel's Integrations screen; workflows use the same connections.

Connection types

ConnectionTypeAuthentication
SlackNotificationIncoming Webhook or Bot Token (chat.postMessage)
Microsoft TeamsNotificationWorkflows webhook
Email (SMTP)NotificationUsername and password, or none
HTTP webhookAutomationURL and optional signature

If you give the webhook a signing secret, every request carries an x-ffm-signature: sha256=… header; the receiver checks the body with HMAC-SHA256 and the same secret. Secrets are stored encrypted.

Every event also carries an x-ffm-delivery-id header and the same value as deliveryId in the body. A failed send is retried with the same id, so if the receiver already processed that id it can ignore the repeat.

Events

Each connection picks the events it receives.

EventWhen it is sent
Secret blockedWhen an API key or password is caught in a request
Policy decisionWhen a limit, budget or personal data rule blocks a request
Operational errorWhen a provider doesn't respond or the fallback model fails too
Approval requestedWhen a workflow or tool call needs approval
Approval decidedWhen an approval request is approved or rejected
Audit recordWhen an admin action is written to the audit log

To avoid a flood of messages, set a cooldown per channel and project: none, 1 min, 5 min, 15 min, 1 hour or 24 hours. Within the cooldown only the first event is sent.

Delivery and retries

An event that fails with a temporary error is retried for about 3 hours: after 30 s, 2 min, 10 min, 30 min and 2 hours. Counting the first send, that is at most 6 attempts. Permanent errors are not retried: a missing address or channel, an invalid bot token, and 4xx answers other than 408, 425 and 429.

Module and license

The Integrations module can be turned off under Settings › Modules. When it is off or not in the license, no events are sent to connections. SIEM export does not depend on this module and has its own license feature.