ActionNovuUpdated September 2026
How do I identify a Novu subscriber?
Short answer: You can identify novu subscriber in Novu by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the Novu Identify Novu Subscriber action to a workflow, map its 5 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Inputs
The fields this action accepts.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Subscriber ID subscriber_id | string | Required | The Subscriber ID assigned by Novu. Find via the corresponding list/search operation in this app. Use the exact ID, not a name or label. |
Email email | string | Optional | The email address. Used as the recipient or identifier depending on context. |
Phone phone | string | Optional | Phone number in E.164 format (with country code, no spaces). |
First Name first_name | string | Optional | Contact's first (given) name. |
Last Name last_name | string | Optional | Contact's last (family) name. |
Sample request
{"subscriber_id": "{{trigger.subscriber_id}}","email": "e.g. user@example.com","phone": "e.g. +14155551234","first_name": "e.g. Jane","last_name": "e.g. Doe"}
Returns
{"data": {"_id": "sub_abc","email": "jane@x.com","subscriberId": "user_123"}}
Use these fields in downstream nodes for routing, logging, or error handling.
Triggered by
Apps that pair well as the trigger for Identify Novu Subscriber.
Any of these apps can fire this action as part of a workflow.
FAQ
Questions about Identify Novu Subscriber.
What does the Identify Novu Subscriber action do in Novu?
Upserts subscriber identity with email, phone, push tokens, preferences. Required before triggering notifications targeting this subscriber.
What inputs does Identify Novu Subscriber require?
Required: Subscriber ID. Every input accepts a static value or a variable from any upstream node in your workflow.
Can I use dynamic inputs from earlier workflow nodes?
Yes. Any field on this action can pull values from upstream nodes, whether that's a form response, a trigger payload, an AI output, or a lookup result.
What happens if Novu returns an error?
The run history shows the failed step with its input and the error message Novu returned, so you can fix the input and run the workflow again. Automatic retries are built into HTTP steps only, where you can also set your own retry count and delay.
Does Identify Novu Subscriber support batch operations?
Run Identify Novu Subscriber inside a loop to process each item in an array. TinyCommand does not throttle calls for you, so for large arrays add a Delay step if you need to stay within Novu's rate limits.
More actions
Other Novu actions.
Action
List Novu Subscribers
Paginated subscriber list. For sync workflows mirroring subscriber base or for inventory.
ActionTrigger Novu Notification
Fires a configured Novu workflow for a subscriber with payload data. Novu fans out across email/SMS/push/in-app per the subscriber's preferences and the workflow's channel steps.