Notifications
Get told when an account disconnects, a lead replies with interest, a campaign finishes or a payment fails, in the app, by email and in Slack.
GraphKit tells the right people when something needs attention. Every notification appears in the bell, can be sent by email, and can be posted to Slack channels your team already watches.
Notification types
| Type | When | Who can receive it | Email by default |
|---|---|---|---|
| Account disconnected | A connected account lost its connection. | Members who can see accounts | Yes |
| Reconnect required | The network asks the account owner to sign in again. | Members who can see accounts | Yes |
| Account restricted | The network restricted an account; its campaigns are paused. | Members who can see accounts | Yes |
| Campaign finished | Every lead of a campaign reached a final state. | Members who can see campaigns | No |
| Campaign paused | A campaign was paused. | Members who can see campaigns | No |
| Positive reply | A lead replied and the reply was classified as interested. | Members who can read that conversation | No |
| Approval needed from Kit | Kit, the AI agent, prepared an action that needs a person to approve it. | Members who can edit campaigns | Yes |
| Billing issue | A payment failed and the subscription is past due. | Organization members who can see billing | Yes |
| Webhook endpoint disabled | A webhook endpoint failed every delivery for 7 days and was turned off. | Members who manage webhooks | Yes |
Who receives a notification follows the same roles as the rest of the app (see Team and roles). Agency owners and managers receive the notifications of every client workspace.
Positive replies respect inbox privacy. A reply in a private conversation reaches only people with access to private conversations, and a member scoped to some accounts hears only about those accounts. See Inbox.
The bell
The bell sits at the bottom of the sidebar, next to your name. A coral badge shows how many notifications you have not read. Open it to:
- See notifications newest first, grouped by day, with the workspace each one came from.
- Select one to open the page it is about (the account, the campaign or the conversation). Opening it marks it read.
- Mark one read, archive it, or mark everything read.
- Switch to Unread to see only what is left.
The bell checks for new notifications every 30 seconds. If you lose access to a workspace, its notifications disappear from your bell.
Your preferences
Open Settings → Notifications (or Notification settings at the bottom of the bell). For each type, choose:
- In app: whether it appears in your bell.
- Email: whether you also get an email.
Preferences belong to you and apply in every workspace you are a member of. Changing them does not affect your teammates. Email notifications use the sender of your account emails; on a white-label domain they carry your agency's brand.
Slack
Post notifications to a Slack channel so the whole team sees them. Each channel has its own list of notification types, so you can send positive replies to #wins and account problems to #ops.
You need a role that manages webhooks (client admin or an agency role) to add channels to a workspace. Open Integrations and find Slack notifications.
Connect with Add to Slack
When the server has a Slack app configured, select Add Slack channel, choose the notification types, then Add to Slack. Sign in to Slack, pick the channel and approve. You return to GraphKit with the channel connected.
Connect with an incoming webhook URL
- In Slack, create an app for your workspace.
- Turn on Incoming Webhooks and select Add New Webhook to Workspace.
- Pick the channel and copy the URL. It looks like
https://hooks.slack.com/services/T…/B…/…. - In GraphKit, select Add Slack channel, paste the URL, choose the notification types and save.
- Select Send test to check that the message arrives.
GraphKit accepts only Slack incoming webhook URLs and stores them encrypted. After you save, the list shows the channel name or a masked URL, never the full secret.
Routing
A channel with every type checked receives every notification, including types added in the future. Uncheck types to narrow it. Change the selection later from the channel's menu: Choose notification types.
Organization-wide channels for agencies
Agency owners and managers can add channels that receive notifications from every client workspace, plus billing issues. Open Notification settings from the bell while in the agency section, or go to the organization's Notifications page. Each message names the workspace it came from.
Workspace channels and organization-wide channels can be used together. A notification posts once to each matching channel.
What a Slack message contains
The title, a short description, the workspace name and the notification type, with an Open button that links to the page in the app. A colour bar shows the severity. Messages never mention GraphKit, so white-label clients see only their own workspace.
Delivery and retries
Email and Slack deliveries are queued when the notification is created and sent by a background worker.
- A failed delivery is retried with exponential backoff: about 1, 3, 9, 27 and 81 minutes apart, up to 6 attempts in about 2 hours. When Slack asks GraphKit to slow down, GraphKit waits as long as Slack asks.
- After the last attempt the delivery is marked failed for good. Open the channel's Delivery log to see every delivery, its error, and Replay it.
- If Slack reports that the webhook was removed or the channel archived, the channel is disabled immediately. After 10 failed attempts in a row, it is disabled too. The reason is shown on the channel and written to the audit log. Fix the problem, then choose Enable.
- A channel that is paused or disabled receives nothing until it is enabled again.
Set up the Slack app (self-hosting)
Add to Slack needs a Slack app registered for your GraphKit server. Without one, teams paste incoming webhook URLs instead.
- Create an app at api.slack.com/apps (From scratch).
- Under OAuth & Permissions, add the redirect URL
https://<API_URL>/api/app/oauth/slack/callback, using your server'sAPI_URL. - Add the bot token scope
incoming-webhook. GraphKit asks for no other scope and stores no bot token: Slack returns the chosen channel's webhook URL, and GraphKit keeps only that, encrypted. - Under Manage Distribution, allow public distribution if teams outside your own Slack workspace will install it.
- Copy the client ID and client secret to the server environment:
SLACK_CLIENT_ID=1234567890.1234567890
SLACK_CLIENT_SECRET=…Restart the API and the worker. The Add to Slack button appears in the Add Slack channel dialog.
API
The app API exposes the bell (GET /api/app/notifications, POST /api/app/notifications/read, POST /api/app/notifications/{id}/archive), preferences (GET and PUT /api/app/me/notification-preferences) and channels (/api/app/workspaces/{workspaceId}/notification-channels and /api/app/organizations/{organizationId}/notification-channels). See the API reference.
To receive raw events in your own systems instead, use webhooks: account.disconnected, message.received and the other webhook events carry the full data.
GraphKit Autopilot
An optional add-on in which Kit runs your outbound for a workspace, from finding and researching prospects to answering the replies you allow, inside the limits you set.
Analytics and client reports
What every metric counts, how to filter and export analytics, the agency overview, and read-only report links for clients.