Skip to main content

Notify Member Action

A Member Notify (Send Notification) action sends an in-app, SMS, or email notification to a specific team member when an event occurs in your workspace. Use it to alert staff to escalations, form submissions, task completions, and other workflow milestones that require human attention.

How it fits together: "Member Notify" is an Action type in Gravity Rail. Attach it to a workflow task as an entry action — when a member enters the task, the notification fires automatically. The notification is delivered on whichever channels the target team member has enabled in their notification preferences.

When to Use Member Notify​

Use caseWhy Member Notify
Escalation alertsNotify a specific clinician or supervisor when a patient escalates to human review
Record follow-upAlert a care coordinator when a patient's intake record is created
Priority queue routingNotify the VIP team lead when a high-priority member enters a task
Scheduled check-insUse with a Routine to remind team members to follow up
Role-specific handoffTarget a specific staff member by ID when a workflow reaches a handoff step

Member Notify vs. Notification Rules: Notification rules are configured in workspace settings and fire automatically on escalation events (e.g., when the AI calls talk_to_human). Member Notify actions give you explicit, programmable control — you decide exactly which event, which condition, and which team member, and you compose the notification message yourself. Use notification rules for automatic escalation coverage; use Member Notify actions for workflow-specific or event-driven alerts.

Prerequisites​

  • A workflow with at least one task (see Workflows)
  • For a Member recipient, the target team member must be a workspace member with a profile in Gravity Rail
  • For a Teams channel recipient, an Apps Admin must have approved the channel on the workspace's Teams notifications page (see Teams notifications)
  • For SMS or email delivery, the target Member needs a valid contact method and the corresponding channel enabled in their notification preferences.

Steps​

1. Open your workflow​

Navigate to Workflows and open the workflow you will use. If you don't have one yet, create a new workflow and add at least one task.

2. Navigate to the Actions page​

Go to Actions in your workspace.

3. Create a new action​

Click New Action.

4. Configure the trigger​

Set the trigger to match the event that should fire the notification. Common triggers:

TriggerUse case
Task EnteredNotify when a member reaches a specific workflow step
Data Record CreatedNotify when a record is created
Data Record UpdatedNotify when a record field changes
Member UpdatedNotify when a member's profile changes

Select the specific task, data type, or workflow relevant to your trigger.

5. Select "Member Notify" as the action type​

In the action type dropdown, select Member Notify. The notification configuration form will appear.

6. Choose who receives the notification​

Under Send To, nothing is selected until you choose. Pick one:

A teammate you choose: Choose a team member from the list. The notification always goes to this person, whichever patient or member the event is about. Use this for staff alerts — on-call staff, supervisors, or care coordinators.

The Member this event is about (in a Journey step: The Member in this Journey): The notification goes to the Member the event concerns. For a Journey or Workflow, that is the enrolled Member, who may be a patient. If the event has no Member of its own, it goes to the Member associated with whatever started the event. A record event for a record that has no owner is the exception: nothing is sent. Write the message for that person — never staff-only wording.

To alert staff, always choose a teammate. "The Member this event is about" can be a patient.

An approved Teams channel (shown when an Apps Admin has approved at least one channel on the Teams notifications page): Choose the channel. There is no message or subject to write: the channel gets one short card saying a notification is waiting, with one Open Gravity Rail button — to the event's Chat when there is one, otherwise the event's record when there is one, otherwise the workspace. Personal unsubscribes and mutes do not silence it; an Apps Admin removes a channel's approval on the Teams notifications page. See Teams notifications. If you switch back to a Member recipient before saving, your message and subject come back.

Older setting: Actions created before this choice existed may show "Older setting: this notification goes to the Member associated with whatever started the event." That Member can be a patient on some events and a staff member on others. The action keeps working as it always has, but you must choose a recipient before you can save a change to it.

7. Write the notification message (Member recipients)​

Skip this step for a Teams channel: it has no Message field. For a Member recipient, in the Message field, enter the notification text. The field starts empty — there is no default message, because the right wording depends on who receives it. This is a template — you can use {{variable}} syntax to personalize the content. Variables describe the event (for example, {{member.name}} is the Member the event is about), whoever receives the notification:

Hi {{member.name}}, a patient has completed their intake and is waiting in the queue.

The message is rendered using the same template system as other action types. See Template Variables below.

This form has no Subject field: the email keeps its default subject, Notification from <workspace>. To set a custom subject, use the API or CLI and pass the optional subjectTemplate parameter (see Creating a Member Notify Action below). It is a template too, using the same variables and permission rules as the message; if it is omitted, blank, or renders empty, the default subject applies.

8. Optionally add conditions​

If you want the notification to fire only under certain conditions (e.g., only during business hours, or only for VIP members), add a CEL expression in the Conditions field. The Developer CEL reference lists variables and functions by event context:

"high-priority" in member.labels && is_business_hours

Leave the conditions blank to fire on every matching event.

9. Optionally set a delay​

If you want the notification to fire after a delay (e.g., escalate only if no response in 2 hours), enable the delay option and set the duration in hours, minutes, or seconds.

10. Save the action​

Click Save. The action is now active and will fire when the trigger conditions are met.

Template Variables​

Use {{variable}} syntax to personalize notification messages:

VariableExample ValueNotes
{{member.first_name}}"Jane"
{{member.middle_name}}"Q"Empty string ("") when the Member has no middle name
{{member.last_name}}"Smith"
{{member.name}}"Jane Q Smith"
{{member.id}}42Safe to include in logs/messages
{{member.form_data.SLUG.FIELD}}Custom Data Type valuesReplace SLUG with your Data Type slug
{{task.name}}"Intake Review"
{{assistant.name}}"Care Bot"

Healthcare compliance note: Avoid including PHI (patient names, health details, phone numbers) in notification messages that may be delivered via SMS or email. Use member IDs and task names instead, and link recipients back to the Gravity Rail app for full context.

For the full list of available variables, see Template Variables.

Notification Delivery​

This section covers Member recipients. A Teams channel gets only the fixed card described in step 6, whatever anyone's preferences are.

A Member's notification is delivered on channels based on two factors:

  1. The target member's notification preferences — which channels they have enabled (SMS, email, in-app)
  2. Their contact details — they must have a phone number for SMS, and an email address for email delivery

Default preferences for workspace members:

ChannelDefaultNotes
SMSEnabled
EmailDisabled
VoiceDisabledChannel toggle exists; voice call delivery is not yet implemented (planned for a future release).
In-appAlways

Members can be updated individually in Members → Edit → Notifications, or in bulk via CSV import. See Notification Preferences.

If a channel is disabled or contact details are missing, delivery on that channel is silently skipped. The in-app notification is recorded unless the recipient has unsubscribed from this notification (for example with Manage / unsubscribe from this notification in its email). The recipient sees it in the app only if they sign in (see below).

Where the recipient sees it in the app​

The in-app notification appears in the recipient's Notifications pane, opened from the sidebar bell, on the This workspace tab in the workspace that sent it, and on the All tab across workspaces. The pane shows the last 30 days. It is unread until they open it or mark it read, and it counts toward the badge on the bell. The row shows your message. When the notification is about a record, selecting the row opens that record if the recipient has permission to view it; otherwise the row stays in place and says "You don't have permission to view this item." Only the recipient sees the notification; other team members do not, whatever their role.

When the event happened in a Chat (for example a Chat event, or a record an Agent saved during a Chat), selecting the row opens that Chat instead, again only if the recipient may see it. A record saved any other way, such as through the API, keeps opening its record. This adds no link to the SMS or email text: those contain exactly the message you wrote, so a patient recipient never receives a staff app link you did not write.

If an Apps Admin has chosen your organization's Bot to send this workspace's notifications in Teams, a recipient who linked their Teams account to the Bot also gets a short Teams message with an Open Gravity Rail button to the same place. It never includes your message. See Teams notifications.

A team member who never signs in (no login) has no in-app Notifications; they receive the notification only on SMS or email. Muting a workspace (Mute this workspace) also hides the notifications sent in it. Notifications sent before this feature was released do not appear in the pane.

The same applies to a Send Notification step in a Journey.

Example Scenarios​

Escalation alert on task entry​

Scenario: Notify the on-call coordinator when a patient enters the "Escalation" task.

  • Trigger: Task Entered → "Escalation" task
  • Target member: On-call coordinator (specific member ID)
  • Message: A patient needs immediate attention. Review the conversation in Gravity Rail: {{member.name}} (ID: {{member.id}})
  • Condition: (none — all escalations notify)

Record follow-up​

Scenario: Notify a care coordinator when a patient's intake record is created.

  • Trigger: Data Record Created → "Intake" Data Type
  • Target member: Assigned care coordinator (specific member ID)
  • Message: New intake record created. Member ID: {{member.id}}. Review in Gravity Rail.
  • Condition: (none)

High-priority escalation with delay​

Scenario: Notify a supervisor if no response after 30 minutes.

  • Trigger: Task Entered → "Awaiting Response" task
  • Target member: Supervisor
  • Message: No response in 30 minutes for member {{member.id}}. Please review.
  • Delay: 30 minutes

Business-hours-only alert​

Scenario: Only notify staff during business hours; after-hours escalations are handled separately.

  • Trigger: Task Entered → "Escalation" task
  • Target member: Day-shift lead
  • Message: Escalation received for member {{member.id}}.
  • Condition: is_business_hours

Member Notify vs. Notification Rules​

Member Notify ActionNotification Rule
Configured inActions pageSettings → Escalation → Notification Rules
TriggerAny event type (task, record, message, etc.)AI escalation (tool.escalate) only
Message contentCustom templateSystem-generated (escalation context)
ConditionsCEL expressionsWorkflow scope only
Delay supportYesNo
Use forWorkflow-specific alerts, record notificationsGeneral escalation coverage

Use both together: set up notification rules as a safety net for all AI escalations, and add Member Notify actions for specific workflow steps that need targeted, customized alerts.

API Reference​

Member Notify actions are created via the Event Rules API.

Base URL: https://api.gravityrail.com/api/v2/w/{workspace_uuid}

Creating a Member Notify Action​

POST /event-rules
Content-Type: application/json

{
"objectType": "task",
"eventType": "task:execute",
"taskId": 123,
"actionType": "member:notify",
"actionParams": {
"recipientMode": "specific_member",
"memberId": 42,
"messageTemplate": "Patient {{member.id}} has entered the escalation queue. Please review."
},
"name": "Notify coordinator on escalation",
"active": true
}

Requires automations:admin scope.

actionParams fields for member:notify:

FieldTypeRequiredDescription
subscriptionIdintegerNoAudience reference returned by a saved Action. Reuse it when keeping that recipient. Do not combine it with recipientMode, memberId or sendToOwner.
recipientModestringNo, with subscriptionId or an older recipient formshared_destination posts the fixed card to the approved channel destinationId (no messageTemplate or subjectTemplate). specific_member sends to memberId. target_member sends to the Member the event is about (for a Journey or Workflow, the enrolled Member); if the event has no Member of its own, the Member associated with whatever started it; if there is none, or the event is for a record with no owner, nothing is sent.
memberIdintegerWith specific_memberID of the team member to notify. An ID alone retains the older specific-recipient form. Not allowed with target_member or subscriptionId.
destinationIdintegerWith shared_destinationAn approved Teams channel from GET /notification-destinations. Not allowed with any Member field.
messageTemplatestringYes, except for a channelThe notification message, not blank. Supports {{variable}} template syntax. Not allowed for a channel.
subjectTemplatestringNo (not for a channel)The email notification's Subject line. Supports the same {{variable}} syntax and permission rules as messageTemplate. Omitted or blank keeps Notification from <workspace>.
sendToOwnerbooleanNo (older actions)Older setting, still accepted: sends to the Member the event's execution runs as, which is not an owner lookup and can be a patient. Cannot be combined with recipientMode or subscriptionId.

Saving the Action binds its audience. API responses return subscriptionId and messageTemplate; recipient fields remain accepted when creating an Action or choosing a different recipient. Reuse the returned reference for a message-only edit. A recipient can unsubscribe from this Action without permission to edit it.

objectType values:

ValueTrigger scope
taskTask Execute events
memberMember-level events (member updated)
data_recordData Type record events (record created, record updated)

eventType values for Member Notify:

ValueDescription
task:executeA Workflow Task runs its configured Actions
data_record:createdA Data Type record is created
data_record:updatedA Data Type record is updated
member:updatedA member's profile is updated

For the full Event Rules feature reference, see Actions.

List Member Notify Rules​

GET /event-rules/search?actionType=member:notify

Requires automations:read scope.

Update a Rule​

PUT /event-rules/{event_rule_id}
Content-Type: application/json

{
"actionParams": {
"recipientMode": "specific_member",
"memberId": 42,
"messageTemplate": "Updated: patient {{member.id}} needs review."
}
}

Requires automations:admin scope.

Permissions​

ActionRequired Scope
View Member Notify actionsautomations:read
Create, edit, or delete Member Notify actionsautomations:admin
Update member notification preferencesmembers:write

Tips​

  • Use member IDs in messages, not names — Member names are PHI in healthcare contexts. Referencing {{member.id}} and linking to the app keeps messages compliant.
  • Check preferences before go-live — If a team member has SMS disabled, they won't receive SMS notifications. Verify preferences in Members → Edit → Notifications before relying on a new rule.
  • Combine with conditions for precision — Add CEL conditions to avoid notification fatigue. For example, only notify for high-priority members or during staffed hours.
  • Use delay for escalation ladders — Chain multiple Member Notify actions with increasing delays to escalate through a chain of contacts (5 min → coordinator, 15 min → supervisor, 30 min → manager).
  • Test with a test member — Create a test member with your own phone number and email, then run a test conversation to verify the notification fires correctly before enabling for real members.
  • Check action logs — Failed actions appear in the action execution log with an error code. Common errors: target_member_not_found (member ID is wrong or the member was deleted), no_event_member (the action sends to the Member the event is about, and this event had none), no_target_member (an older action with no recipient set).
  • Notifications — Configure escalation-based notification rules and understand how delivery channels work
  • Notification Preferences — Per-member SMS, email, and voice opt-in settings
  • Actions — Full list of action types and how to build event-driven automations
  • CEL Expressions — Write conditions to control when actions fire
  • Routines — Schedule automations to run on a recurring basis
  • Template Variables — Full variable reference for personalizing messages