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.

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.

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.

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

👀

• 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 and 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

Hide a personalized greeting when first_name IS

⭐

👷

and

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.

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

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.

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

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

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."

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.

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.

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

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.

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.

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.

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.

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.

AUP block notification emails will now be sent to:

OR

If no Agency Owner or Sub-account Admin is available, the system will send the email randomly as a fallback mechanism.

We’ve enhanced the existing Facebook contact merge functionality to now support Facebook Lead Form submissions in addition to Messenger conversations :rocket:

Previously, the setting:

Merge Facebook contacts by name : supported contact merging only for Facebook Messenger conversations.

With this enhancement, the functionality has now been expanded and split into two dedicated settings under:

The available options are now:

This enhancement allows users to independently control merge behavior for Messenger-based contacts and Facebook Lead Ads submissions

We received multiple customer requests to support merge functionality for Facebook Lead Ads submissions, especially in scenarios where leads may not always contain consistent phone numbers or email addresses.

With support for name-based matching for Lead Form submissions:

Additionally, separating Messenger and Lead Form merge behaviors into dedicated settings provides better flexibility, clarity, and control for users managing Facebook contact deduplication workflows.

We’ve rolled out new customization improvements for Marketing Audit Report widgets, giving you more control over how your lead capture forms appear to visitors.

You can now customize:

Supported fields include:

Marketing audit widgets are commonly used as lead magnets across websites, landing pages, ads, and outbound campaigns.

Until now, field copy was fixed and couldn’t be tailored to different audiences or campaign goals.

With this update, you can now:

For example:

The next phase of widget improvements will focus on:

These improvements help make Marketing Audit widgets more flexible, customizable, and conversion-focused for different business needs.

We’ve added keyboard shortcut support to the Product Details Page for smoother image navigation when Open Lightbox zoom is enabled.

Customers can now:

The lightbox also auto-focuses when opened, so shortcuts work immediately without needing an extra click. Arrow keys will no longer scroll the page behind the popup.

The AI Agent action now supports Update Custom Value as a built-in tool. The agent can evaluate context during execution and write directly to custom values inside a sub-account — replacing complex If/Else trees that previously required dozens of branches and actions.

Workflows that previously needed branching logic for every possible condition — day-based schedules, formatted dates, rolling promo codes, context-aware values — now resolve in a single agent step. Less maintenance, fewer actions, faster execution, and lower complexity across your automations.