We’re excited to introduce a powerful new capability in SuprSend: Objects. Objects allow you to manage complex user relationship and notify user groups without identifying individual recipients in your trigger. Ideal for building scalable pub/sub and subscription alerting without having to maintain event to subscriber mapping in your database. You can directly map object-user subscription mapping in SuprSend and SuprSend can efficiently fan-out notifications to thousands of users simultaneously.

What You Can Do with Objects:

• Send notifications to non-user entities like group emails, Slack channels, or shared inboxes (e.g., a Notion feed). Ideal for SaaS applications sending account-level alerts (e.g., anomaly notifications) to shared channels. Objects can have it's own channels and preferences to handle this usecase.
  
  
• Group users by topic or subscription and send them alerts without having to call individual recipients in the trigger. A good example could be SaaS applications managing notifications for end-users, where recipient relationships are coming from a different system, and notification triggers or notification calls are coming from a different system which doesn't have information of the users subscribed to that trigger.
  
  
• Maintain hierarchical user relationship with nested object subscription. For example, sending announcements to all the entire team of customer while sending invoice related alerts to finance team. You can handle this by creating object for finance team and then adding it as subscriber to customer object.

Objects can be easily tested from platform with all all object related actions available on SuprSend console. You can programatically manage objects from your codebase using rest API calls. Support for SDKs coming soon...

If there's any usecase in object that you think is missing and needs to be solved, please reach out to our support.

You can now compare datetime fields in workflow conditions. This lets you compare two timestamps where values can be:

• Variable – computed from workflow input data
• Static – a fixed timstamp (e.g. 2024-01-01T00:00:00Z)
• Relative to current timestamp – E.g. - "now" or "now+30d" (current timestamp +/- interval). Current timestamp is calculated at node runtime and is timezone aware.

The UI for multi-channel and smart routing nodes has been revamped to clearly display how the final list of channels is determined. Now, you get clear visibility into how requested channels in the trigger, override channels, and user and tenant preferences are factored together to compute the final channel list.

To enhance security and transparency, we’ve introduced Audit Trail to help you monitor and track actions happening on your SuprSend console. You can use this to keep track of unwanted or malicious actions in your account. This initial release logs critical account actions along with location and actor details (team member performing the action). You can also filter by team member (actor), specific action or timestamp.

Audit logs are available for enterprise users and have customizable retention period. You can find it in account settings.

Added support for customizing the header component in inbox SDKs.

• @suprsend/react-inbox

You can now add a custom component to the right side of the header in the inbox popup. This replaces the "Mark all as read" text with any JSX you provide. You can even include custom icons, such as settings or preferences, in your JSX and use them to navigate users to specific pages. For an example, refer to https://docs.suprsend.com/docs/react-customize-inbox#adding-custom-header-component.

• @suprsend/web-inbox

In web-inbox, you can add an extra icon beside the "Mark all as read" button at the top of the inbox popup using headerIconUrl. You can also execute custom logic when this icon is clicked using headerIconClickHandler. This feature is useful for cases like displaying settings or preferences icons, which, when clicked, take users to the respective settings or preferences pages. For more information, refer to the documentation at https://docs.suprsend.com/docs/embeddable-inbox#customising-inbox.

With the growing number of workflow nodes, we understand that designing the optimal workflow logic can be tricky. That’s why we’ve built out a library of the most-requested, complex workflow samples to make things easier. Now, when you create a new workflow, you can pick from these pre-built samples right within the platform. We’ll continue adding more samples over time—if you have specific use cases, feel free to share them with us at [email protected], and we’ll add them in the library!

As part of our ongoing efforts to maintain a robust and up-to-date platform, we've made the following deprecations:

1. Legacy FCM API Support

Due to Google's shutdown of the legacy Firebase Cloud Messaging (FCM) API, we have removed support for this feature. We strongly recommend migrating to the V1 version of the API that we currently support.

For more information, please refer to: Firebase Cloud Messaging Migration Guide

2. Xiaomi Push Service

Following Xiaomi's discontinuation of their push service outside mainland China, we have removed support for this feature.

For more information, please visit: Xiaomi Developer Documentation

We appreciate your understanding and cooperation as we continue to improve our services. If you have any questions or concerns about these changes, please don't hesitate to contact our support team.

We have revamped subscriber listing page to include relevant information upfront and also, added advanced filtering options on email, phone, active channels, channel count for an entity, and more.
All filters are powered by auto-complete search and selectable options, providing you easy access to available filtering options.

We’re excited to announce a major update to the platform experience with autocomplete in all subscriber search fields. Whether you’re in logs, on the subscriber page, or within testing flows, you can now receive suggestions for existing users without needing to type the full keyword. Autocomplete suggestions are available for distinct_id, email, and phone fields in subscriber profiles.

This update introduces improvements to action button functionality, enhancing the flexibility and customization options for developers.

New Features:

• Custom Click Handlers: Action buttons now support custom click handlers, allowing developers to execute custom logic when a button is clicked.

This update significantly expands the capabilities of action buttons in the Inbox React SDK, providing developers with more tools to create rich, interactive inbox experiences.