Skip to main content
Kortix’s notification system keeps users informed about important events like task completions, payment updates, and system alerts. The system is powered by Novu and supports multiple delivery channels.

Notification Channels

Kortix supports three notification channels:

Email Notifications

Email is the primary notification channel:
  • Task completion updates
  • Payment confirmations and failures
  • Referral invitations
  • Welcome emails
  • Credits low alerts

Push Notifications

Mobile push notifications via Expo:
  • Real-time task updates
  • Urgent alerts
  • System notifications

In-App Notifications

Browser-based notifications:
  • Activity feed updates
  • Non-urgent reminders
  • Feature announcements

Notification Types

The system supports various notification workflows:

Task Completion

Notify users when their agent tasks complete:
Task notifications are suppressed if the user is actively viewing the conversation. This prevents unnecessary interruptions.

Task Failed

Alert users when tasks encounter errors:

Payment Notifications

Inform users about payment events: Payment Succeeded:
Payment Failed:

Credits Low Alert

Warn users when credits are running low:

Welcome Email

Greet new users with a welcome message:

Referral Invitation

Send referral codes to invited users:

User Presence Detection

The system checks if users are actively viewing content before sending notifications:
This prevents sending redundant notifications when users are already engaged.

Managing Notification Settings

Get User Settings

Response:

Update Settings

Response:

Push Notification Setup

Register Device Token

Register a device for push notifications:
Response:

Unregister Device Token

Response:

Novu Integration

Kortix uses Novu for notification orchestration:

Workflow Trigger

Supported Workflows

  • welcome-email: New user onboarding
  • task-completed: Task finished successfully
  • task-failed: Task encountered an error
  • payment-succeeded: Payment processed successfully
  • payment-failed: Payment processing failed
  • credits-low: Account credits below threshold
  • promotional: Marketing and announcements

Admin Notifications

Admins can trigger custom notifications:

Broadcast Notifications

Send notifications to all users:

Template Variables

Payloads support variable substitution:
Example:

Webhook Handler

Receive webhook events from Novu:

Account Info Retrieval

The service fetches user details from Supabase Auth:

Best Practices

Always check if users are actively viewing content before sending notifications. This prevents notification fatigue.
  • Email for important updates and receipts
  • Push for time-sensitive alerts
  • In-app for low-priority updates
Include direct links to relevant content in notifications. Users should know exactly what to do next.
Before going live, test all notification workflows to ensure correct delivery and formatting.
Use Novu webhooks to track notification delivery and failures. Address issues promptly.

Environment Configuration

Notifications are currently only enabled in staging mode:
This restriction will be removed in production deployments.

Troubleshooting

Notifications Not Sending

  • Check Novu setup: Ensure Novu API key is configured
  • Verify workflow: Confirm the workflow exists in Novu
  • Check user email: Ensure the account has a valid email
  • Review logs: Look for errors in notification service logs

Push Tokens Not Working

  • Verify provider: Ensure using “expo” for Expo push notifications
  • Check token format: Expo tokens follow the pattern ExponentPushToken[xxxxx]
  • Test registration: Manually register a test token and verify

Duplicate Notifications

  • Check presence service: Ensure presence detection is working
  • Review workflow triggers: Verify workflows aren’t triggered multiple times
  • Check Novu deduplication: Configure deduplication in Novu if needed

API Reference

Endpoints