What’s new?

We’ve launched a common integration experience for workflow actions and triggers. Integration-powered steps now show the required fields upfront, guide users to connect the right account without having to leave the workflow, and support multiple connected accounts where available.

How it works

When an integration is not connected, the action or trigger panel now shows a connect banner and a preview of the fields in a locked state. Clicking Connect your account opens the integration setup in a new browser tab, so users can complete the connection without losing their workflow setup. Once connected, the fields unlock and the selected account appears directly in the action or trigger.

How to use it

• Open an integration-powered action or trigger in a workflow.
• Click Connect your account if no account is connected.
• Select the connected account and configure the fields.

Why we built it

Previously, users often discovered missing integrations only after saving a workflow, with little guidance on how to fix it. They also couldn’t see what fields or options an integration supported before connecting an account, which made it harder to evaluate actions from scratch. This update reduces setup errors, keeps users inside their workflow context, and makes integration-powered actions easier to understand and adopt.

Simple examples

• A user opens a Typeform action from a workflow template. They can now see all the available fields in this integration as a preview which can be updated after connecting their account.
• A user opens a Slack action with multiple connected accounts. They choose the right account from the account dropdown, and the available connections reload for that account.

Additional Notes

• Available field options now now appear as a preview before an integration is connected.
• If a connected account is removed or becomes invalid, the step returns to a locked connection-required state.
• Some apps load fields step by step after connection, based on earlier selections if it requires fetching information to load.
• Dynamic fields that depend on the selected account may reset when the account changes.

Preview

What’s new?

We’ve launched a common integration experience for workflow actions and triggers. Integration-powered steps now show the required fields upfront, guide users to connect the right account without having to leave the workflow, and support multiple connected accounts where available.

How it works

When an integration is not connected, the action or trigger panel now shows a connect banner and a preview of the fields in a locked state. Clicking Connect your account opens the integration setup in a new browser tab, so users can complete the connection without losing their workflow setup. Once connected, the fields unlock and the selected account appears directly in the action or trigger.

How to use it

• Open an integration-powered action or trigger in a workflow.
• Click Connect your account if no account is connected.
• Select the connected account and configure the fields.

Why we built it

Previously, users often discovered missing integrations only after saving a workflow, with little guidance on how to fix it. They also couldn’t see what fields or options an integration supported before connecting an account, which made it harder to evaluate actions from scratch. This update reduces setup errors, keeps users inside their workflow context, and makes integration-powered actions easier to understand and adopt.

Simple examples

• A user opens a Typeform action from a workflow template. They can now see all the available fields in this integration as a preview which can be updated after connecting their account.
• A user opens a Slack action with multiple connected accounts. They choose the right account from the account dropdown, and the available connections reload for that account.

Additional Notes

• Available field options now now appear as a preview before an integration is connected.
• If a connected account is removed or becomes invalid, the step returns to a locked connection-required state.
• Some apps load fields step by step after connection, based on earlier selections if it requires fetching information to load.
• Dynamic fields that depend on the selected account may reset when the account changes.

Preview

Conditional Visibility is now more flexible and easier to manage with support for layouts and value-based conditions.

👀 What is new?

• Visibility Rules for Layouts

Apply conditional visibility to entire layouts instead of configuring each element individually. Layouts now include a dedicated Visibility tab alongside Edit, with support available in HighRise as well.

• New Value-Based Operators

Added IS EMPTY and IS PRESENT operators for more dynamic conditions. All custom fields — including attachment fields — are now supported in the conditional visibility dropdown.

Example Use Cases

Show a “Download Invoice” button only when an attachment field IS PRESENT

Hide a personalized greeting when first_name IS EMPTY

⭐ Impact

• Eliminates repetitive rule setup across multiple elements
• Enables cleaner handling of empty or missing field values
• Allows entire sections to hide gracefully
• Makes Conditional Visibility significantly more powerful while preserving existing behaviour

👷 How to Use

1. Select any layout or element inside the email builder.

2. Open the Visibility tab.
3. Choose the field you want to evaluate.
4. Select a condition:

IS/ IS NOT and IS EMPTY/ IS PRESENT

5. Set the required value (if applicable) and save.

Conversation Logs for Contact Preference Updates

We’ve added support for logging contact-level preference status updates directly on the Conversations surface.

With this release, any communication preference update triggered either by the contact or by a user will now be captured as a conversation log. This helps teams get better context around preference changes without needing to move away from the conversation view.

What’s New

1. Preference status updates are now logged in Conversations.
2. Logs are created for updates triggered from both:

• the contact’s end
• the user’s end

This is a contained release and part of an ongoing series of improvements to enhance visibility and traceability across contact and conversation workflows.

Benefits

Teams can now easily view preference-related updates directly in Conversations.

This adds to the visibility layer already available in the Contacts module.

Users get better context on preference changes without switching between multiple surfaces.

Preference updates become easier to track, improving operational clarity and follow-up actions.

Coming Soon

We’re also working on more holistic visibility with the upcoming launch of filters on the Contact Listing page.

What's new

The Wait action has been completely redesigned with a new intent-based UI, recurring schedules, and AI-powered setup.

New intent-based card selection.

The old dropdown has been replaced with a card selection screen that asks "What should the contact wait for?" Users now pick their intent first, then configure — no more hunting through nested dropdowns to find options like "Wait for a contact reply."

Recurring wait schedule.

Set up recurring waits with weekly, monthly, or yearly frequency. Weekly supports specific days and times (e.g., every Sunday, Tuesday, Wednesday at 9 AM). Monthly supports a specific day or nth weekday. Yearly supports renewals, holidays, and annual check-ins.

Wait for a specific date — single-step setup.

Previously required two separate actions (Set Event Start Date + Wait). Now it's one step — pick a fixed date or pull from a custom field directly inside the Wait action.

Seconds as a wait unit.

Time delay now supports seconds, enabling rapid-fire sequences with two- or three-second pauses between actions.

Dynamic wait duration.

Wait durations can now be set dynamically using the custom value picker. Pull the duration from a custom field, contact field, or any supported variable instead of hardcoding a value.

Grouped wait types.

Related wait types are now grouped under single cards to reduce clutter. For example, "Wait for a contact action" now includes trigger link clicks and email events in one place. Appointment and service booking waits are similarly unified.

Contextual option reordering.

The card selection screen adapts to context. When Wait follows a Send action (SMS, Email, or WhatsApp), "Wait for the contact to reply" automatically surfaces as the first option.

Wait AI. A new CTA at the top of the Wait action lets users describe their desired wait behavior in natural language. The AI Builder agent generates a configured Wait action card that can be added directly or refined through conversation.

Why this matters

Wait was one of the highest support ticket drivers in Workflows. Two issues accounted for the bulk: users not realizing that waiting until a specific date required a separate "Set Event Start Date" action, and "Contact Reply" being buried under the CRM Events dropdown while Time Delay was the default. The new single-step date setup and intent-based card layout with contextual reordering directly eliminate both pain points.