ActionNovuUpdated May 2026

How do I identify a Novu subscriber?

Short answer: Drop the "Novu → Identify Novu Subscriber" action anywhere in your workflow, map the inputs from upstream nodes, and publish.

Use this action All 3 Novu actions

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.

2 Google Sheets triggers

HubSpot → Novu

18 HubSpot triggers

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 workflow pauses on the failed node, the error message is captured in the run log, and you can retry the run with one click. Auto-retry policies are configurable per workflow with exponential backoff up to 5 attempts.

Does Identify Novu Subscriber support batch operations?

Yes. Run Identify Novu Subscriber inside a Loop node to process arrays. Tiny Command handles Novu's rate limits automatically so you don't have to throttle manually.

More actions