Notification Channels

Mockarty supports sending notifications through external messaging services — Telegram, Slack, Discord, Microsoft Teams, and others. This allows users to receive real-time alerts about test results, fuzzing findings, agent task completions, and system events directly in their preferred messenger.

Architecture

The notification system uses a two-level model:

1. Admin configures system-wide notification channels (e.g., “Corporate Slack”, “Telegram Bot”)
2. Users connect to available channels and configure which events they want to receive

Additionally, the AI agent can use system channels to send notifications without requiring users to provide credentials.

Supported Channels

Admin Setup

Adding a Channel

1. Go to Admin Panel → Notification Channels
2. Click Add Channel
3. Select the channel type
4. Fill in the configuration (follow the setup hints shown for each type)
5. (Optional) Set Namespace — leave empty to make the channel global (visible in every namespace) or enter a specific namespace name to scope it. The field is safe to change later via update.
6. Click Save
7. Use Test button to verify connectivity

Updating a Channel (secrets-safe)

When editing an existing channel, you don’t need to re-enter tokens, webhook URLs, or other sensitive fields — the UI sends an empty string for fields you leave blank and the server keeps the previously stored value for them. Only fields you actively fill in get overwritten. This lets you rename a channel, flip its enabled state, or move it between namespaces without ever exposing its secrets again.

Admin audit log

Every admin-initiated channel change is recorded in the audit log (visible in Admin Panel → Audit Log). Three action codes identify the events:

Secret fields (bot tokens, webhook URLs, passwords) are never written to the audit log — only the public metadata is captured. Use this log to trace who configured a channel, when it was disabled, or which admin removed a target that stopped receiving alerts.

Channel Configuration Examples

Telegram

1. Open Telegram, find @BotFather
2. Send /newbot, follow the prompts to create a bot
3. Copy the bot token (format: 123456789:ABCdef...)
4. In Mockarty Admin → Channels → Add → Telegram:
   • Bot Token: paste the token
   • Bot Username: @YourBotName (optional, for display)
5. Save and enable

Users will connect by clicking a deeplink that opens the bot in Telegram.

Slack

Option A: Bot Token (recommended for DMs)

1. Go to api.slack.com/apps → Create New App
2. Add Bot Token Scopes: chat:write, users:read.email
3. Install to workspace, copy the Bot Token (xoxb-...)
4. In Mockarty: paste as Bot Token

Users enter their Slack email to receive DMs.

Option B: Incoming Webhook (channel-level)

1. In Slack App → Incoming Webhooks → Add New Webhook
2. Select a channel, copy the URL
3. In Mockarty: paste as Webhook URL

Discord

1. In Discord: Server Settings → Integrations → Webhooks → New Webhook
2. Select a channel, copy the webhook URL
3. In Mockarty: paste as Webhook URL

No per-user binding needed — messages go to the channel.

Microsoft Teams

1. In Teams channel: click ... → Workflows
2. Select “Post to a channel when a webhook request is received”
3. Follow the setup wizard, copy the webhook URL
4. In Mockarty: paste as Webhook URL

Note: Legacy Office 365 Connector URLs are being retired. Use Workflows (Power Automate) webhooks.

PagerDuty

1. In PagerDuty: Services → select service → Integrations tab
2. Add Integration → Events API v2
3. Copy the Integration Key
4. In Mockarty: paste as Integration Key (routing_key)
5. Optional: set Severity — one of critical, error, warning, info (defaults are applied per event type if omitted)

OpsGenie

1. In OpsGenie: Teams → select team → Integrations → Add integration → API
2. Copy the API Key
3. In Mockarty: paste as API Key
4. Select Region — us (api.opsgenie.com) or eu (api.eu.opsgenie.com). Using the wrong region causes silent delivery failures.

Testing a Channel

After saving, click the Test button on any channel to send a test notification. For channels that require a recipient (Telegram, Slack), you’ll need to provide a chat ID or email.

User Setup

Connecting to Channels

1. Go to Settings → My Notification Channels
2. Available channels configured by admin are listed under Available Channels
3. Click Connect on the desired channel

Telegram Connection

1. Click Connect on the Telegram channel
2. A deeplink opens – click it to go to the bot in Telegram
3. Press Start in the bot chat
4. Connection is confirmed automatically

Slack Connection

1. Click Connect on the Slack channel
2. Enter your Slack workspace email
3. Mockarty resolves your Slack user ID and sends DMs directly

Webhook Channels (Discord, Teams, etc.)

These are channel-level — click Connect and you’re done. All users connected to the same channel receive the same messages.

Notification Preferences Matrix

After connecting, configure which events trigger notifications:

Use checkboxes in the preferences matrix to enable/disable each event per channel. Event IDs above are the canonical identifiers emitted on the EventBus and used by the template engine.

AI Agent Integration

The AI agent (notifier sub-agent) can send notifications through system channels without credentials:

1. list_system_channels — returns available channels with IDs
2. send_via_channel — sends a notification through a channel by ID

Example agent interaction:

User: "Send a summary of today's test results to Slack"
Agent: [calls list_system_channels → finds Slack channel]
Agent: [calls send_via_channel with channel_id, title, text]

The agent can also use direct tools (send_slack, send_telegram, etc.) with explicit credentials if system channels are not configured.

Without AI Agent

The notification system works entirely without the AI agent:

• Automatic notifications: Events (test completions, fuzzing findings, etc.) trigger notifications through the EventBus → Channel Dispatcher pipeline
• User preferences: Control which events go where via the preferences matrix
• Admin broadcasts: Admin can test channels directly from the admin panel

API Endpoints

Admin API

Delivery reliability

Every channel dispatch is logged to channel_delivery_log with a status that progresses through pending → delivered, or pending → retrying → dead_letter after exhausting max_retries. The admin UI under Notification Channels → Delivery Log gives you two views:

• Dead Letter – deliveries that have used up all retries. You can requeue any entry with one click to send it back through the retry worker.
• Retry Queue – deliveries currently waiting for their next retry attempt, sorted by next_retry_at.

A leader-only background worker picks up due retries, applies exponential backoff, and moves the row to dead_letter once retry_count >= max_retries.

Per-event message templates

The dispatcher renders every notification through an override-aware template engine. Lookup order is (most specific → least specific):

1. (eventType, channelType, lang) – fully-specific override
2. (eventType, channelType, "") – any language
3. (eventType, "", lang) – any channel
4. (eventType, "", "") – any channel, any language
5. Built-in default shipped with the code

Templates use Go text/template syntax and have access to the raw event payload ({{ .Payload.fieldName }}), the resolved title ({{ .Title }}), body ({{ .Body }}), and deep link ({{ .Link }}).

Manage overrides from Notification Channels → Message Templates in the admin UI, or directly via the /api/v1/admin/channel-templates endpoints.

User API

See Also

• Webhooks & Callbacks – Mock-level webhooks for HTTP, Kafka, and RabbitMQ callbacks
• Integrations Guide – Integration tokens, resolver nodes, runner agents, and CI/CD
• Administration Guide – User management, namespaces, and system configuration
• API Reference – Full REST API documentation