CommunityHire an ExpertSign Up
ActionsSend Notification
Actions

Send Notification

Notify users of your published app from a workflow, as a browser push notification, in the app's notification inbox, or both.

Send Notification

Applies to: Send Notification 1.0.0, 1.1.0

Send notifications to your app users directly from a Softr Workflow. Notify users about new messages, status changes, task assignments, or any other event — as a push notification in their browser, in the app’s notification inbox, or both.

Overview

Version history

  • Changed in 1.1.0: renamed from Send Push Notification to Send Notification, with a choice of channels.

The Send Notification action is a native Softr feature that lets you notify one or more specific users of your published app. It delivers through two channels:

  • Push — appears in the user’s browser or device notification center, even when they’re not actively using your app. Ideal for time-sensitive updates.
  • In-app (1.1.0 and later) — appears in the notification inbox inside your app, next to comment and mention notifications. It waits there until the user reads it, even if they weren’t online when it was sent.

Each notification includes a title, body, and an optional URL to open when the user clicks it.

Prerequisites

Before using the Send Notification action in a Workflow, enable the channel(s) you want to use in your app:

  1. Open your Softr app and go to Users → Notifications.
  2. For Push, enable push notifications for the device type(s) you want to support — Desktop, Mobile, or both. Use Permission prompt to customize the message that asks users to allow notifications.
  3. For In-app, turn on In-app notifications. Use Notification inbox to customize the inbox button and texts — see Notification Center.
  4. Publish your app.

Once push is enabled, users who visit your published app will be prompted to allow notifications in their browser. Only users who have granted permission will receive push notifications from your workflows.

In-app notifications need no permission from the user: a recipient sees them in the inbox after logging in to your app.

Settings

FieldDescription
AppThe published app whose users will be notified. Defaults to the current app.
Channels (1.1.0 and later)Where to deliver the notification: Push, In-app, or both. A new step has both selected.
User emailOne or more users to notify. Recipients must be users of the selected application. Map a user email from an earlier workflow step, or provide multiple emails separated by commas.
Notification titleThe notification heading (displayed in bold). Keep it short and clear.
Notification body (optional)The notification message text. Describe what happened or what action is needed.
Open URL on click (optional)The page to open when the user clicks the notification. Only URLs that start with your app’s domain are accepted. Defaults to your app’s home page if left empty.

Key Benefits

  • Instant delivery: Push notifications appear in the user’s browser or OS notification center in real time.
  • Nothing gets missed: In-app notifications stay in the inbox until the user reads them.
  • No email required: Reach specific users directly without sending an email.
  • Clickable deep links: Drive users to a specific page or record by setting a URL in the notification.
  • Native to Softr: No third-party service or API key required — notifications are built into Softr.

Example Use Cases

Use CaseDescription
Task assignmentNotify a user when a new task is assigned to them in your project management app.
Status change alertAlert a customer when their order or support ticket status is updated.
New message or commentLet users know when someone replies to their post or leaves a comment.
Approval requiredPrompt a manager to review and approve a pending request.
Deadline reminderSend a reminder before a due date using a scheduled workflow trigger.

How to Add a Notification Action to a Workflow

  1. Open your Softr workspace and go to Workflows.
  2. Create a new workflow or open an existing one.
  3. Add an action step, select Softr Apps, then choose Send Notification.
  4. In the Settings panel on the right, pick the App and Channels, then configure the User email, Notification title, Notification body, and optionally Open URL on click.
  5. Map dynamic values from earlier steps (e.g., use the triggered user’s email as the recipient, or the record name in the notification body).
  6. Test the action using the Testing tab — for push, make sure at least one user has subscribed to notifications in your published app.
  7. Turn on your workflow.

Versions

Steps created with an earlier version of Send Notification keep working. The Applies to line at the top of this page names the versions the page covers. An item marked with a version applies from that version on; everything else applies to every version of the page. A Version history block under a heading lists what changed for that part.

VersionWhat changed
1.1.0Renamed from Send Push Notification to Send Notification. Adds Channels (Push, In-app); a new step has both selected. A 1.0.0 step opened in the builder is upgraded to 1.1.0 with Push only, so it keeps sending exactly what it did before — add In-app to also reach the inbox.
1.0.0The first version, as Send Push Notification: push only.

Use these docs with your AI tools

An AI agent can read this documentation directly. You do not need an account or an API key. Everything here is public and read-only.

Query these docs via MCP

Recommended

Add this server to Claude, Claude Code, Cursor, Mistral, or any tool that supports MCP. Your agent can then search Softr Documentation documentation and read it in full, instead of answering from memory.

https://docs.softr.io/mcp
  • searchFind the passages that answer a question.
  • fetchRead one page in full, as Markdown.
  • list_pagesSee every page in this documentation.

Query these docs over HTTP

The same tools also work as plain web requests. Use this for scripts, or for any tool that does not support MCP. There is one endpoint per tool. Arguments go in the query string, and the answer comes back as JSON.

https://docs.softr.io/api/docs/search?query=custom+domain

Read the OpenAPI description. It is built from the same definitions as the tools, so it always matches what the endpoints do.

Read these docs as Markdown

Add .md to any page URL to get its Markdown source. You can also send the headerAccept: text/markdown to the page URL itself.

To read the whole documentation in one file, open llms-full.txt. For a short index of every page, open llms.txt.