Berserk Docs
Integrations

Integrations

Configure notification destinations, MCP tools, and source control connections

Open Settings → Integrations to create, edit, or test a named connection. Alerts and workflows reference the connection name, keeping credentials out of their definitions. Connection secrets are encrypted at rest and are not returned in connection summaries.

Choose a kind, give it a recognizable name, complete its fields, and save. When editing a webhook, leave its URL blank to keep the stored URL. The Test action sends a real probe for notification connections; choose a test destination before using it.

Slack

Choose Slack webhook and enter an incoming webhook URL for the intended Slack channel or direct-message destination. Select the saved connection in an alert's notification channels or a Slack workflow step.

Include chart in alert messages is enabled by default. It adds a PNG chart to alert notifications when notification image access is configured for your installation. Clear the checkbox to send alerts without charts through this connection. It does not add charts to arbitrary workflow messages or connection test probes.

Slack must be able to fetch each image from its own servers. A URL that works only on your laptop, behind sign-in, or over a VPN is insufficient. See Slack chart image access for setup and testing.

Discord

Choose Discord webhook and enter the webhook URL for the destination. Use the saved connection in alert notification channels or a Discord workflow step. The connection test posts a short message. The Slack chart setting does not apply to Discord.

Generic webhooks

Choose Generic webhook and enter the HTTPS endpoint that should receive JSON POST requests. Use a webhook workflow step to define the JSON body. The test sends a small JSON message with a text field; it does not exercise your workflow's complete payload.

Outbound webhook URLs are validated against Berserk's network access restrictions. A blocked destination is reported as an error.

PagerDuty

Choose PagerDuty, select US or EU, and enter the service's 32-character Events API V2 integration key. The form explains where to find this key. Leave it blank when editing to retain the stored key.

Select the connection in alert notification channels or a PagerDuty workflow step. Alert recovery resolves the incident. Configure repeat paging and escalation in PagerDuty.

SMTP

Choose SMTP and configure the relay host, port, TLS mode, sender address, and optional username and password. Leave the password blank when editing to retain it. Berserk must be able to reach the relay from the UI service.

The connection test asks for a recipient address and sends a real email. Configure recipients on the notification or email step.

Custom MCP servers

Choose Custom MCP server, enter the server URL, and select its authentication mode: no authentication, Basic, token/custom header, or OAuth. Complete the matching credentials and any additional headers. For OAuth, use the redirect URI shown in the form when configuring the provider.

Use the form's validation and tool discovery controls to check the server and choose which tools are enabled. These connections provide external tools; they are separate from outbound alert notification destinations.

Source control

GitHub, GitLab, and Forgejo connections configure the provider URL, allowed repositories, and whether the integration is enabled. Enter repositories as owner/name, one per line. Provider-specific fields configure OAuth applications, GitHub App installations, and webhook signing.

Connect account credentials separately in Source access. That is also where you test an execution identity. Saving the shared integration configuration does not authenticate every user to the provider.

Managing connections

Editing a connection updates the configuration used by subsequent deliveries. Turning off Slack charts does not remove images from messages already sent.

Connections referenced by definitions cannot be deleted through the normal delete operation. Remove those references first. Tests verify the connection itself; trigger a test alert to verify evaluation, message formatting, chart access, and deep links together.

On this page