Docs › Integrations › Claude

Claude

Use NotiLens with Claude to get notified when your AI agent starts, completes, errors, or needs input — via webhook or the SDK.

Overview

What This Integration Does

Any system that can send HTTP webhooks can integrate with NotiLens. When your app triggers an event, NotiLens receives it and notifies you instantly.

Works with custom apps, AI agents, internal tools, CRMs, scripts, and third-party platforms.

Why NotiLens

Why Use NotiLens for Custom Integrations?

Centralize alerts from all your systems. Receive only meaningful notifications, delivered instantly to one place.

Setup

How to Set Up a Custom Webhook

1. Create a Custom Topic in the NotiLens App

  1. Select Custom Integration in the NotiLens app.
  2. Set a Topic and Description that matches your use case.
  3. Copy the generated Webhook URL.

Sample webhook URL:

https://hook.notilens.com/webhook/<topic_id>/send

2. Send Events from Your Application

  1. Trigger an HTTP POST request when an event occurs.
  2. Use the NotiLens webhook URL as the endpoint.
  3. Send data in JSON format.
  4. Include relevant event details in the request body.
Sample JSON payload:

{
  "title": "Server Alert",
  "message": "CPU usage exceeded 80% for more than 5 minutes.",
  "type": "alert",
  "event": "cpu_high",
  "image_url": "https://example.com/images/alert.png",
  "open_url": "https://dashboard.example.com/servers/123",
  "meta": {
    "server_id": "srv_123",
    "threshold": 80,
    "current_usage": 92.5
  },
  "is_actionable": true
}

You can send events from backend services, serverless functions, automation tools, or scripts.

3. (Optional) Configure a Secret Key

  1. Generate a secret key in your application.
  2. Open the webhook settings in the NotiLens app.
  3. Paste the secret key to enable signature verification.
  4. Save the changes.

Using a secret key helps ensure requests are coming from a trusted source.

Payload

Webhook Payload Format

Send a POST request with a JSON body using the following keys. Only title and message are required.

Key Required Type Default Description
title Yes string Short heading for the notification
message Yes string Main notification content or description
type No string info Notification category (for example: info, success, warning, error, important)
event No string Logical event identifier (for example: build.failed)
image_url No string (URL) Public image URL to display in the notification
open_url No string (URL) URL opened when the notification is clicked
meta No JSON Additional structured data in JSON format for internal use or debugging
is_actionable No boolean Whether the notification should be treated as actionable (for example, requires user attention)

All requests must use Content-Type: application/json. Invalid payloads will be rejected.

Events

Example Custom Events

Event Description Use Case
build.failed Build or deployment failed Engineering alerts
payment.received Payment successfully processed Revenue tracking
user.signup New user registered Growth monitoring
error.critical Critical system error Incident response
task.completed Background task finished Workflow visibility
← Previous SDK & CLI