📝 Overview

Improved Manage Fields so you can now see all fields from your form, survey, or quiz — even if those fields don’t have submission data yet.

Previously, Manage Fields only showed fields that had already received data in at least one submission. Now, it also includes fields from the form definition, making it easier to manage columns before submissions come in.

🆕 What’s improved

• Manage Fields now shows all fields from your form, survey, or quiz definition
• New fields are visible even if they haven’t received any submission data yet
• Fields added after earlier submissions will now appear in the available fields list
• Available but unselected fields show up in the Add Fields section

🔍 How to access

1. Go to Sites > Forms, Surveys, or Quizzes
2. Open the three-dot menu for the item you want
3. Click View Submission
4. On the Submissions page, click Manage Columns to view and add fields from the definition, even if they don’t have submission data yet

🎯 Why it matters

• Makes it easier to manage columns before new submissions come in
• Gives you better visibility into all available fields
• Helps you prepare reports and views without waiting for test or live submissions
• Creates a more complete and predictable submissions management experience

📝 Overview

Added gradient background support for buttons in the Form, Survey, and Quiz Builder.

This update gives you more control over button styling by letting you switch between a solid color and a gradient background directly from the button settings.

🆕 What’s improved

• You can now apply a gradient background to buttons
• Choose between solid color or gradient styling
• Supports linear, radial, and angular gradient types
• You can adjust the gradient angle for supported styles
• Add and edit multiple color stops for more customized button designs

🔍 How to access

1. Open the Form, Survey, or Quiz Builder and select a button element.
2. From the button style settings, open the Button Background section. You can then switch from a solid color to a gradient and customize the colors, type, and angle.

🎯 Why it matters

• Gives you more flexibility when styling buttons
• Makes it easier to create more modern and visually dynamic designs
• Lets you customize buttons without needing custom code
• Keeps existing button styles working while adding more design options

👀 What’s New?

• Added a new “Load on user interaction” toggle inside Chat Widget > Chat Window tab > Additional Options.
• When enabled, the chat widget delays loading until the visitor interacts with the website.
• Helps improve initial website performance and reduce unnecessary widget load during page rendering.
• Default behaviour remains unchanged for existing widgets unless the toggle is enabled manually.

👷How It Works:

1. Navigate to Sites > Chat Widget Builder.
2. Open the Chat Window tab of the specific chat widget.
3. Under Additional Options, enable the new “Load on user interaction” toggle.

4. Once enabled:

• The widget will load only after a visitor interaction such as: Scroll, Click or Touch interaction.
• If no interaction happens, the widget automatically loads after a fallback delay (~8 seconds).

5. If the toggle is disabled or not configured:

• The chat widget loads immediately as per existing behaviour.

⭐ Why It Matters:

1. Improves overall website performance by reducing immediate script execution during page load.
2. Helps reduce blocking time and improves user experience, especially on mobile devices.
3. Ensures the widget remains available for genuine visitors while minimising impact on page speed.
4. Gives businesses more flexibility in balancing performance and customer engagement.

📝 Notes:

• Existing widgets will continue using immediate load behaviour unless the setting is explicitly enabled.
• Applicable to customer-facing chat widgets only that are present on any digital property.
• Includes fallback auto-load behaviour to ensure widget availability even without interaction.

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