50skills Product News

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.

If you want to make sure a specific portal is locked and only accessible to your employees or certain groups within your company, we recommend looking at using SSO authentications for your portal.

Each portal now has a new security option: "Azure (SSO) Log in". If you enable this, only managed AD users can access the portal.

You might need some help from IT implementing this, so if you are looking to make your employee / supervisor portal more secure, definitely look at this feature!

The employee portal has become a staple in many companies using journeys. This is where employees can find everything they need, from benefit requests to signing up for the company bowling trip after work.

Since the birth of this feature we have received a lot of feedback and improvement requests, and we have listened.

This is why we have released the following improvements and new features to the portal.

Update #1 - Multiple portals

You can now create multiple company portals – perfect for different teams, brands, or use cases.

Update #2 - Password protection

If you don't feel comfortable having the portal open, you can now add a password which users are required to give to enter the portal.

Update #3 - Portal layout

In the initial version, users had no control over the layout and ordering of the items in the portal. To help with this we have added a drag and drop option so you can have the portal the way you want.

Update #4 - Custom links

You can now add links on your portal that are not connected to Journeys but instead re-direct the user to any site you want. This means if you have a form in another system then journeys e.g. Microsoft Forms or Typeform, you can re-direct the user there.

Update # 5 - Portal statistics

Users can now find usage data on their portals. You can view data for all portals or cherry pick one of them to see data information for such things as:

• Views
• Clicks on external forms
• Clicks on custom links
• Number of live external forms
• Number of live custom links

Additional improvements

We did add some other minor improvements such as:

• Users can now add external forms to portals from within the portal management
• In the main navigation bar, users can now see a list of portals and the settings section instead of just one portal
• Easier to copy the portal URL for sharing with quick copy buttons

One of the most used feature in our product is the field mapping modal where you map information in to actions.

We have significantly changed this feature in order to help with reducing clicks and spending time on doing repetitive tasks.

Example:

When mapping data from the traveller or another action in the workflow, in the old version you would have to keep re-opening the field mapping modal and finding the data that you wanted to add, now this is in a persistent side-panel so you never leave the field mapping configuration mode!

See it here in action:

Why is this feature useful?

• Easier to map data: Users would have a lot of clicks and re-opening the modal to map data, it got tiresome very quickly
• Easier to work with in large journeys: Users can now quick search for data, collapse and hide data that is irrelevant