Added the ability to set relative delays and batch windows in workflows. Previously, delays were fixed or dynamic, with the time difference always being based on the current time. With this update, you can now define delays relative to a future timestamp, often provided by your trigger payload.

For instance, send a reminder 30 minutes after a task's due time or send feedback 5 minutes after an event or webinar.

Fixes and Improvements:

• In Inbox drop-in popover component, we fixed scrollbar causing empty padding UI issue in macOS when Show Scroll bars: Always is enabled.
• In Inbox drop-in popover component, action menu popup of last notification item was getting cropped. We have fixed this issue.
• In Inbox drop-in popover component, in mobile view actions menu icon (3 dots icon) only appears on touching notification. After the bugfix, the actions menu icon will appear on all notifications in mobile view by default, removing extra touch interaction.

Previously, when triggering workflows in nested object hierarchies (where one object subscribes to another), notifications would automatically fan out up to two levels—sending notification to object, its direct subscribers, and child object subscribers.

Now, you have full control over how deep the fan-out should go. You can now set the depth in the recipient payload, defining how far the workflow should propagate to fetch subscriptions.

🔹 Depth 0 → Notify only the object’s channels (e.g., Slack team, shared inbox).
🔹 Depth 1 → Notify the object’s channels + direct subscribers.
🔹 Depth N → Expand deeper into hierarchical subscriptions as needed.

"recipients": [
  {
    "object_type": "teams",
    "id":"finance",

    //optional parameter to define subscription fan-out depth in workflows
    "$object_subscriptions_query": {
      "depth": 0
    }
  }
]

You can use this to build Escalation Workflows or Tiered Customer Support Notifications, send notification to a shared slack channel or customer support queue first and then escalate to individual users in case of no response in a given time duration.

Fixes and Improvements:

• [SDK] Object methods and User APIs to fetch user and their subscription exposed in Java SDK
• Added support to trigger multi-lingual templates in broadcast

We've introduced a new setting in batch processing: Flush First Item in Batch. Previously, batches were only sent once the batch window closed. Now, this setting allows the first trigger to flow past the batch immediately while subsequent triggers are batched within the specified time window.

This will help you to build leading debounce logic in workflow, where users are notified about critical updates like anomaly alerts immediately, while batching rest of the alerts and sending them at regular intervals until the issue is resolved.

You can find this option in batch -> advanced configuration.

We’ve added handlebars helpers to seamlessly handle JSON strings in the template editor:

• jsonParse - Converts a JSON string into an object, making it easier to apply conditions or use JSON strings in merge tags.
• jsonPath - Fetch data corresponding to a path within a JSON object. Works well with jsonParse to directly access nested data in JSON string without block helpers.

Fixes and Improvements:

• Opened up merge tag input to support handlebars helper in email merge tags.
• Added support for handlebars helper in display condition.

You can now trigger a workflow when a user enters or leaves a list. Use this in the Wait Until node to stop reminders or dynamically route users in a workflow on list updates. Earlier, you could achieve the same by enabling event tracking on list updates. Now, you can simply add this logic in workflow without making any changes in list.

This will help you build workflows on user lists like, send series of activation notifications to users who didn't interact with the product in last 30 days and stop sending when they become active again.

Fixes and Improvements:

• [SDK] We have exposed object management methods in Node SDK

Happy to announce a major update in our Inbox SDK. Now, you can directly export and embed Inapp feed component and seamlessly create Fullscreen or Side sheet Inbox experience.

What’s New?

✅ Enhanced Security – We've replaced HMAC authentication with stateless JWT authentication for better security.

✅ Drop-in components – You can now quickly build an inbox, including fullscreen and side sheet feeds, by directly importing UI inbox components that are available in our SDK.

✅ Bring your own toast – If you plan to use toast notifications, you have full flexibility to choose any toast library you prefer, allowing you to fully customize the notification experience.

These updates offer greater flexibility, security, and customization — giving you full control over your in-app notification experience.

If you are on the older SDK version, we recommend you to move on the new version as all future developments will be done on the new SDK.

We’re excited to introduce Interaction Observer support in the Inbox, enabling smarter tracking of notification seen state. Now, notifications will be automatically marked as "seen" when they come in user's scroll view.

We’ve done a major revamp to our Broadcast logging and monitoring, designed to give you greater control and transparency over your broadcast executions.

Here’s what’s new:

• Real-time Execution Tracking: Monitor broadcast operations as they happen, ensuring you stay informed every step of the way.
• Step-by-Step Debugging: View detailed execution logs for each step of your broadcast, helping you pinpoint errors and resolve issues faster.
• Advanced Filters: Quickly locate specific broadcasts with filters for tenant, list ID, broadcast slug, idempotency key, and status. Easily identify and analyze failure logs.
• Detailed Broadcast Summaries: Access a comprehensive summary of each broadcast run directly from the listing page, similar to workflow execution logs.

We’ve added Athena to our list of database connectors, enabling you to sync and create dynamic user lists directly from your S3 database. Since Athena can be set up on top of S3, it’s an excellent way to consolidate data from multiple sources and run queries on the unified dataset without the need for complex ETL pipelines.

With this update, you can invoke a workflow from within another workflow. This is useful when the recipient list or data context changes between steps in a workflow.

A common use case is escalation workflows—for example, if a team member doesn't take action within a set timeframe, the workflow escalates the issue and notifies their manager.

This simplifies complex workflows and supports smooth transitions between related processes, enabling more efficient automation management.