🇪🇸 Español 🇬🇧 English 🇧🇷 Português

Node: Notify Person

How to use the Notify Person node to send an in-app alert to a workspace member about a board task.

Jul 11, 2026

The Notify Person node sends an in-app notification to one or more members of the workspace about a task (item) on a Board. It's how you automatically alert the right person when something happens to a card, instead of relying on someone checking it manually.

When to use it

  • In workflows triggered from Boards, when you need to alert an item's owner about a change (upcoming due date, status change, new assignment, etc).
  • When the team uses a "Person" column to assign owners and you want to notify whoever is assigned on each item, without hardcoding a fixed user.

Requirements

  • The workflow must run with a board item in context.
  • The recipient(s) must be members of the same workspace the workflow runs in; users outside the workspace are filtered out automatically.

Configuration

  • Fixed person (user_id): a specific workspace member, picked from a list.
  • …or pull the person from a column (from_column_id): a "Person" type column on the board; whoever is assigned in that column for the item gets notified. You can combine both — the fixed person AND whoever is in the column both get notified.
  • Message (message, required): the notification body. Supports variables like {{item.name}}.

Example

On a Projects board, a workflow fires when an item's due date is approaching. The Notify Person node uses from_column_id pointing at the "Owner" column with the message: "{{item.name}} is due today and isn't marked Done yet." Whoever is assigned on each card gets the alert automatically, regardless of who that is.

Tips

  • If no recipients resolve (empty column, or a user that no longer exists), the node is skipped without breaking the rest of the flow.
  • Pair it with date conditions (date_time) to build due-date reminders.

Troubleshooting

  • Notification never arrives: confirm the configured user (or whoever is assigned in the column) is an active member of the workspace — users outside the workspace get nothing.
  • "empty message": the Message field was left blank; it's required.
Was this helpful?

Related articles