Skip to main content

Smart Push Notification Workflow Action (Client Portal)

The Smart Push Notification workflow action lets you send personalized push notifications to registered Client Portal users, with optional redirection to Communities or Courses.

Updated over 3 months ago

Who This Is For / When to Use

Use Smart Push Notifications if you want to:

  • Notify Client Portal users about updates, reminders, or new content

  • Drive engagement back to Communities or Courses

  • Send timely, personalized messages triggered by workflows

Only registered Client Portal users can receive Smart Push Notifications.

What Is Smart Push Notification

Smart Push Notification is a workflow action that sends real-time push notifications to:

  • The Client Portal mobile app

  • Supported browsers

Each notification supports:

  • A customizable title

  • A message body (up to 300 characters)

  • Dynamic personalization using placeholders

  • Redirection to Communities or Courses

How to Add Smart Push Notification to a Workflow

  1. Go to Automation > Workflows.

  2. Open an existing workflow or click Create Workflow.

  3. Click + Add Action.

  4. Search for Smart Push Notification.

  5. Select Smart Push Notification.

How to Configure Smart Push Notification Fields

After adding the action, configure the following required fields:

Title

  • Enter the notification title.

  • Supports personalization placeholders.

Example:
Welcome {{contact.first_name}}!

Message Body

  • Enter the main notification message.

  • Maximum length: 300 characters.

  • Supports placeholders and emojis.

Example:
Hi {{contact.first_name}}, check out the latest update waiting for you.

Redirection

  • Choose where users are redirected when they tap the notification.

  • Supported destinations:

    • Communities

    • Courses

Save and Activate the Workflow

  1. Click Save Action.

  2. Test the workflow using a sample contact.

  3. Publish and activate the workflow when ready.

Best practice: Always test before activating to confirm personalization and redirection behavior.

What the User Receives

When the workflow is triggered, the contact receives a push notification similar to the example below:

Example Use Case: Community Update Notification

Goal: Notify users about a new Community post.

Configuration:

  • Title: New Community Update!

  • Message Body:
    Hi {{contact.first_name}}, there’s a new post waiting for you in the community.

  • Redirection: Communities

Result:
Users tap the notification and are taken directly to the Community page.

Important Limitations

  • Notifications are sent only to registered Client Portal users.

  • Contacts without Client Portal access will not receive notifications.

  • Images are not supported inside push notifications.

  • Notifications rely on user browser or app notification permissions.

Best Practices

  • Keep titles short and action-oriented.

  • Use personalization to improve open rates.

  • Avoid sending multiple notifications in short timeframes.

  • Test with real Client Portal users before full rollout.

Common Questions

Can I use placeholders in Smart Push Notifications?

Yes. You can use placeholders such as {{contact.first_name}} and {{contact.last_name}} in both the title and message body.

What is the character limit for the message body?

The message body supports up to 300 characters.

Where can users be redirected?

Users can be redirected to:

  • Communities

  • Courses

Who receives Smart Push Notifications?

Only contacts who are registered Client Portal users.

Can I use emojis?

Yes. Standard emojis are supported in both the title and message body.

Did this answer your question?