​

Steps and flows

A flow splits the card into at least two and at most 12 steps. Use it for checklists, guided updates, qualification, and approvals.

​

Enable steps

1. Click an empty area so Card settings appear.
2. Find Steps.
3. Choose Enable steps.

Card Studio creates two steps and automatically enables Back, Continue, and Submit. The step indicator is turned on as well.

​

Edit the steps

For each step you can:

• change the step name;
• move it up;
• remove it, as long as at least two steps remain;
• mark required input fields;
• add a visibility rule.

Add steps up to the limit of 12. Step names can be up to 60 characters.

​

Assign building blocks to steps

Select a building block and use Shown on step:

• All steps shows the building block as shared content;
• a specific step shows it only there.

When you are on a step in the canvas, new building blocks are normally added to the active step. Check this setting if content shows up in the wrong place.

​

Automatic navigation buttons

When the setting is on, the runtime adds the buttons automatically:

• Back on steps after the first visible step;
• Continue on steps before the last visible step;
• Submit on the last visible step.

Turn off automatic navigation if you want to build your own buttons with flow actions. In that case, make sure there is a complete path forward and back; otherwise the user can end up on a step with no navigation.

​

Step indicator

Show step indicator on the card displays the progress. Turn it off on very compact cards, or in flows where the step names are already clear from the content.

​

Required fields and validation

Mark the input fields that must be filled in on each step. Continue, forward jumps, and Submit validate:

• the step’s required fields;
• format and limit rules for inputs shown on the step;
• shared input fields shown on all steps.

Backward navigation is unrestricted. Submit only works from the last visible step.

​

Conditional steps

A step whose visibility rule is false is skipped. The rule can use form answers, record data, the selected record, and other dynamic values. Make sure at least one step is always visible. When jumping forward, every visible step being passed is validated.

​

When the flow is submitted

Under When the flow is submitted, you can add the same action types as on a button. The actions run only once, on the transition to a validated submitted state. A typical submit sequence is:

1. update one or more HubSpot properties;
2. create a task or call an external system;
3. show a success message;
4. optionally open a link at the end.

​

Remove all steps

Choose Remove all steps to make the card single-page again. Step references are cleaned up automatically, but review your building blocks and flow actions afterwards. Actions like “go to next step” are only valid on a card with a flow.