Install
$ agentstack add skill-novuhq-skills-manage-subscribers ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ● Environment & secrets Used
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
Manage Subscribers
Subscribers are the recipients of your notifications. Each subscriber has a unique subscriberId — typically your application's user ID.
SDK Setup
import { Novu } from "@novu/api";
const novu = new Novu({
secretKey: process.env.NOVU_SECRET_KEY,
});
Create a Subscriber
await novu.subscribers.create({
subscriberId: "user-123", // required — your system's user ID
email: "jane@example.com", // optional
firstName: "Jane", // optional
lastName: "Doe", // optional
phone: "+15551234567", // optional
avatar: "https://example.com/jane.jpg", // optional
locale: "en-US", // optional
timezone: "America/New_York", // optional
data: { // optional — custom key-value data
plan: "pro",
company: "Acme Inc",
},
});
Only subscriberId is required. All other fields are optional.
Retrieve a Subscriber
const subscriber = await novu.subscribers.retrieve("user-123");
Search Subscribers
const results = await novu.subscribers.search({
email: "jane@example.com",
});
Update a Subscriber
await novu.subscribers.patch(
{ firstName: "Jane", data: { plan: "enterprise" } },
// subscriberId
"user-123"
);
Delete a Subscriber
await novu.subscribers.delete("user-123");
Bulk Create
Create multiple subscribers at once. 500 subscribers can be created in one request.
await novu.subscribers.createBulk({
subscribers: [
{ subscriberId: "user-1", email: "alice@example.com", firstName: "Alice" },
{ subscriberId: "user-2", email: "bob@example.com", firstName: "Bob" },
{ subscriberId: "user-3", email: "carol@example.com", firstName: "Carol" },
],
});
Topics
Topics are named groups of subscribers. Use them to send notifications to multiple subscribers at once.
Create a Topic
await novu.topics.create({
key: "engineering-team",
name: "Engineering Team",
});
Add Subscribers to a Topic
await novu.topics.subscriptions.create(
{ subscriptions: ["subscriberId-1", "subscriberId-2", "subscriberId-3"] },
"engineering-team-topic"
);
Remove Subscribers from a Topic
await novu.topics.subscriptions.delete(
{ subscriptions: ["subscriberId-1", "subscriberId-2"] },
"engineering-team-topic"
);
List Topics
const topics = await novu.topics.list({
});
Delete a Topic
await novu.topics.delete("engineering-team-topic");
Trigger to a Topic
See [trigger-notification](../trigger-notification/) for topic trigger examples.
await novu.trigger({
workflowId: "project-update",
to: { type: "Topic", topicKey: "engineering-team-topic" },
payload: { message: "Sprint review at 3pm" },
});
Subscriber Credentials
Set channel-specific credentials for push and chat integrations.
FCM Push Token
await novu.subscribers.credentials.update(
{
providerId: "fcm",
// use integrationIdentifier if there are multiple fcm type active integrations
integrationIdentifier: "fcm-abc-123",
credentials: { deviceTokens: ["fcm-device-token-here"] }
},
"subsriberId-1"
);
APNS Push Token
await novu.subscribers.credentials.update(
{
providerId: "apns",
// use integrationIdentifier if there are multiple apns type active integrations
integrationIdentifier: "fcm-abc-123",
credentials: { deviceTokens: ["apns-device-token-here"] }
},
"user-123"
);
Common Pitfalls
subscriberIdis YOUR user ID — it bridges your system to Novu. Use a stable, unique identifier from your database.- Subscribers are auto-created on trigger — if you pass a full subscriber object in
towhen triggering, Novu creates the subscriber if it doesn't exist. But explicit creation gives you more control. - Subscriber data is per-environment — dev, staging, and production have separate subscriber records.
- Topics must exist before triggering — create the topic and add subscribers before sending to it.
- Deleting a subscriber doesn't delete their notifications — existing notifications remain in the system.
- Adding non existent subscriber to topic - if non existent subscriber is added to topic, it is not autocreated in that environment and hence not added to the topic. Always create subscribers before adding into the topic
References
- [Subscriber CRUD Examples](./references/subscriber-crud-examples.md)
- [Topics Examples](./references/topics-examples.md)
- [Credentials Examples](./references/credentials-examples.md)
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: novuhq
- Source: novuhq/skills
- License: MIT
- Homepage: https://novu.co
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.