You can now control who can submit external forms and when they close. Journeys uses company-level roles to control who can access settings, navigation areas, and administrative actions across your company account.

These roles ensure that users only see and interact with the parts of the platform they have permission to use.

There are three roles:

Admin -> Full access to everything, including billing, security settings, and member management

Editor -> Can build and manage journeys and workspaces, but can't touch sensitive company-level settings like billing or security

Contributor -> A focused role for people who need to work within journeys but don't need access to configuration or admin features

Roles are assigned when inviting a new member or by editing an existing one from the Members page.

Navigation automatically adjusts based on the role, contributors and editors simply won't see sections they don't have access to.

There's also a safety guard built in: you can't demote the last Admin in your organization.

You can now control who can submit external forms and when they close.

Use this to:

• Open forms only during specific enrollment periods
• Automatically close event registrations at a set time
• Limit submissions per traveller or overall capacity
• Display a custom message when the form is closed

Under the External form settings you'll find a new Access & Scheduling section with four options:

Close date -> Set a specific date and time when the form stops accepting submissions

One submission per traveller -> Prevent duplicate submissions by restricting to one per email address

Total response limit -> Cap the total number of submissions allowed

Custom closed message -> Write a message travellers will see once the form is no longer accepting responses

Our AI Navigator has a set of new capabilities.

Portal link — Navigator can now look up and share the portal link where an external form lives, so you don't have to go find it yourself.

Example

Update journey title -> You can now ask Navigator to rename the journey directly from the chat.

Image previews -> When you upload an image in the Navigator chat (for example, to reference a design or screenshot), it now shows a preview with the file name instead of a blank placeholder.

Document template previews -> When Navigator is picking a document template to use in a step, you can now preview the template inline before it gets added to the journey.

Setting up integrations just got a lot faster. You can now import an OpenAPI (Swagger) specification directly, paste the URL or upload the file, and Journeys will automatically create your integration endpoints from it.

For each endpoint it finds, the importer will:

• Detect the authentication method required (API key, Bearer token, Basic auth, etc.)
• Generate request and response fields with variable suggestions already mapped
• Extract the server URL and handle path parameters automatically

If your organization uses Microsoft 365 or Google Workspace to send email, you can now authenticate your custom SMTP domain using OAuth2 instead of an app password.

Many organizations have disabled app passwords as a security policy, which previously made it difficult to use a custom sending address. OAuth2 solves this, authentication goes through your provider's standard authorization flow (a quick browser popup), and Journeys handles token refresh automatically in the background.

To set this up, go to Settings → Email domain, add or edit your SMTP domain, and choose OAuth2 as the authentication type.

As our system has grown a lot, the old side panel for adding actions became harder to navigate, especially with more integrations and endpoints.

We’ve redesigned it from the ground up.⚡

What’s improved with this feature:

• 🗂 Better organization – Everything now has a clear structure.
• 🔎 Powerful search – Quickly find an integration or even a specific endpoint.
• 📈 Built to scale – Handles growing integrations much more gracefully.
• 🤖 Easier AI Agent creation – Creating new AI Agents is now more intuitive.

The new modal is faster, cleaner, and much easier to work with, especially for complex journeys.

You can now see and manage your journey’s publish history directly in the journey builder.

Every time you publish a journey, a version is saved. date

With Versioning, you can:

• 🕒 Review previous versions
• 🔍 Compare what changed (actions added, modified, or removed)
• 🔁 Restore an older version, if needed

Why this matters

• Made changes to your onboarding flow and something didn’t work as expected?
• Need to see what the journey looked like before a recent update?

With Versioning, you can quickly go back, review the differences, and restore a previous setup, without rebuilding anything manually.

You’ll find Version history inside thee three dot options in the top right corner of your journey builder.

More control. Less stress. 😊

You can now control which dates users can select when filling out forms that include a Datepicker field.

With Datepicker Restrictions, form builders can:

• Disable paste to ensure users select a date using the calendar.
• Block future dates, useful when collecting information about past events.
• Restrict specific date ranges so only valid dates can be chosen.

This helps improve data accuracy and prevents users from submitting invalid dates.

Example use cases:

• Sick leave registration – Prevent employees from selecting future dates.
• Timesheets – Restrict entries to the current payroll period.
• Onboarding forms – Ensure start dates fall within a defined hiring window.
• Incident reporting – Allow only past dates to ensure reports reflect actual events.

Form builder POV: Form recipient has to select a first workday but the datepicker is disabled for all past date

Person filling out POV: All paste dates can no longer be selected

These restrictions make your forms more reliable and easier to validate, while guiding users to submit the correct information.

You can now enrich the forms sent in a "Send form" action with dynamic data from previous steps in the journey. This makes it easy to personalize forms with things like the recipient’s name, company, or any other data you’ve already collected, fewer manual steps & better completion rates.

When the person receives the form and opens it, the data is populated with workflow information like shown here below.

We really hope you like this feature, it has been brewing for some time and has definitely been the most requested feature for a long time now. 🍵

You’re no longer limited to one sender email per company!

You can now configure multiple email domains, addresses and choose which one to send from when building journeys. Perfect for teams managing multiple brands, regions, or use cases.

Additionally, when configuring "Send email" actions in the journey builder, you can now select from what e-mail entity you want to send the e-mail from.