You can now control when your notifications are sent with our Delivery Window feature! Set specific time ranges for delivery, handle multiple timezones seamlessly, and ensure messages are sent exactly when you want.

It's not time to debug your automation workflows. You can run test events, view data diff between nodes, quickly validate nodes at-a-glance. We also added a GET Profile node top help you dynamically fetch any Courier profile.

The Message Tags as a Template Setting feature enables users to tag their messages directly from the Notification Template. When messages are sent, these tags are parsed and added to the metadata tags field. This allows messages to be filtered in the inbox or through the Messages API using the specified tags.

The webhook payload for outbound messages included an empty tags object when tags were specified in the send request via metadata.tags. This issue was resolved, and the tags object was ensured to reflect the provided metadata.tags accurately.

Courier's POST `/profiles/:user_id` (`profiles.create()`) endpoint would accept an empty profile object, return a `{SUCCESS: true}` but not create the profile. This endpoint was updated to mimic the other endpoints and allow an empty profile to create a user.

The Message Tags as a Template Setting feature enables users to tag their messages directly from the Notification Template. When messages are sent, these tags are parsed and added to the metadata tags field. This allows messages to be filtered in the inbox or through the Messages API using the specified tags. The feature is accessible under a feature flag, which requires activation by contacting courier support or the account team.

Courier's POST /profiles/:user_id (profiles.create()) endpoint would accept an empty profile object, return a {SUCCESS: true} but not create the profile. Other endpoints and methods (like .identify() would allow for creating a profile with an empty object. This endpoint was updated to mimic the other endpoints and allow an empty profile to create a user.

The webhook payload for outbound messages included an empty tags object when tags were specified in the send request via metadata.tags. This occurred regardless of the presence of tag data, as demonstrated by an empty tags: {} array in the payload. This issue was resolved, and the tags object was ensured to reflect the provided metadata.tags accurately.

Customers experienced a 404 error when using the Send Again feature on undeliverable notifications for ad-hoc sends that included a fan-out (lists, tenants, array of profiles, audiences). The endpoint was rewritten to address this problem and now successfully supports re-queuing ad-hoc list messages.

Customers experienced a 404 error when using the Send Again feature on undeliverable notifications for ad-hoc sends that included a fan-out (lists, tenants, array of profiles, audiences). The Send Again feature would work for the full original message but would fan out and re-send to all recipients. The endpoint was rewritten to address this problem and now successfully supports re-queuing ad-hoc list messages.

Messages sent with a delay were initially not visible in the logs UI or through the API, even though a request ID was provided. The visibility problem was resolved with recent changes that created first-class request entities and stored them alongside messages, allowing delayed messages to appear correctly in the logs and API responses.

We added archive APIs to our iOS, Android, and React Native SDKs, allowing you to build a swipe left to remove from the Courier Inbox. Enable your users to declutter their inboxes and keep only the notifications they want to save for later.

Fixed miscellaneous errors with the switch node, including access to deeply nested data. This issue has been fixed.

Digesting a Send API feature allows business and enterprise customers to aggregate frequent transactional messages into scheduled digests without requiring code changes. Admins in Courier link notification templates select a Linked Digest Template and set schedules for sending aggregated messages by configuring digests in the Preferences Editor.

The tenants page in the Database tab did not persist changes made to the JSON fields, although the changes were saved and could be retrieved via the API and used in notifications. This has been fixed.

Implemented a feature to handle ThrottleException errors more effectively using SES's sendRawEmail function. Previously, a 400 status with ThrottleException would not trigger retries, potentially disrupting email delivery processes. With the new update, such errors now throw a retryable provider error to ensure more robust and resilient email sending

We've updated our notification pipeline to catch ThrottleException thrown by AWS SES in the case the SES account has reached its thresholds. This is now a retryable error, and notifications will automatically be retried with an exponential backoff.

Invoke automation steps failed when null values were found in optional fields.

Courier Inbox websockets experienced issues with users with 100+ active connections. Toasts and live messages were not delivered to those users. This has been resolved.

For some customers, analytics sparklines were not appearing. For the customers affected, they should now start seeing usage analytics for the template on their Asset Page

Courier iOS 4.0+ SDK is live! 🙌. This upgrade includes access to every low-level API, better handling of user states, increased reliability, and avoiding race conditions.

We have revamped automation based on usage and user feedback with quality-of-life enhancements and new functionality. Automation Workflows 3.0 is fully compatible with previous versions, and current Automations will continue using the 2.0 user interface.

Courier Android 4.0+ SDK is live! 🙌 This upgrade includes access to every low-level API, better handling of user states, increased reliability, and avoiding race conditions.

Our Template Designer now supported Click Action for Firebase and Apple Push Notification Service templates. This feature allows developers to define specific actions triggered when recipients clicked on their notifications and create deep links using variables.

The XSS inbox variable vulnerability allows malicious code to be executed within an inbox notification when the message is opened if the code is included as part of a data variable. This contrasts with directly placing the same code in the inbox template, which renders the code without executing it. Please upgrade your inbox to version 6.2.1.

We resolved the issue where introducing a delay object in the request caused the cancel endpoint to return a 404 response. This fix ensures that cancellation requests are processed correctly even when no messages exist yet.

When editing an Automation on a slow network, a race condition could make the canvas save a blank draft; this issue has been fixed.

When creating a new automation, we resolved an issue where the data object in automation templates was incorrectly nested within the recipient object. This bug caused disruptions in data processing and automation workflows. The fix ensured that data objects were nested properly, improving the reliability and efficiency of automation templates.

The Courier Preferences Center is available for Flutter, React Native, iOS, and Android platforms. Implementing in your mobile application will allow your users to customize their delivery preferences seamlessly.

Throw on Variable Not Found (Beta) is a feature in Courier that prevents messages from being sent if required variables are not provided, ensuring error-free communication. This feature, which can be toggled on from the notification template settings, checks variables after all conditionals are evaluated, and operates at both the preview and message log stages.