Skip to main content
Contact Support

Form Logic vs. Step Logic: What’s the Difference?

Ryan J.
Updated

When building powerful, dynamic workflows in Streamline, both Form Logic and Step Logic help you customize the user experience and automate your processes intelligently. While they may seem similar at first glance, each serves a different purpose—and understanding how and when to use them can take your workflows from basic to brilliant.

 

This article breaks down the key differences between Form Logic and Step Logic, how each one works, and when to use them.

 

 

Overview: Quick Comparison

Feature Form Logic Step Logic
Used In The form builder The workflow builder
Controls Visibility of fields or sections Which steps in a workflow are triggered
Trigger Based On Answers to previous form fields Form submission data or field responses
Best For Tailoring the form experience for users Automating what happens after a form is submitted
Logic Types Show/hide logic for individual fields or sections Conditional branching for steps in a workflow
Icon Indicator LOGIC icon on form fields/sections Visible logic branches within the step layout

 

What is Form Logic?

 

Form Logic is used within a form to show or hide certain fields or sections based on user responses. It helps tailor the form experience in real time, so users only see what’s relevant to them.

 

Key Use Cases:

 

  • Displaying a comments field if the user gives negative feedback.
  • Hiding billing fields unless a user selects a paid option.
  • Showing additional inputs only when a checkbox is selected.

 

How it works:

  1. Select a field or section in the Form Builder.
  2. Click the Logic tab and choose + Add Logic.
  3. Set conditions based on other fields’ values.
  4. Logic can be set to trigger on all or any matching rules.

 

Pro Tip: Form Logic only affects what users see on the form—it does not change what happens after the form is submitted.

 

 

What is Step Logic?

 

Step Logic is used in the workflow builder to control what happens after a form or workflow step is submitted. These logic steps act as decision points, branching your workflow based on form responses or other conditions.

 

Key Use Cases:

 

  • Sending different email notifications based on user input.
  • Assigning follow-up tasks to different teams based on a dropdown selection.
  • Skipping unnecessary steps when certain conditions aren’t met.

 

How it works:

 

  1. Drag a Logic Step from the Utilities section into your workflow.
  2. Place it between or after other steps where branching should occur.
  3. Click Edit Step to configure your rules using "AND"/"OR" conditions.
  4. Add a Fallback branch for situations where no rules are met.

 

Pro Tip: Step Logic is perfect for post-submission automation—it determines what actions your workflow should take based on submitted data.

 

 

When to Use Each

 

Use Case Use Form Logic Use Step Logic
Show or hide fields based on user responses ✅ Yes ❌ No
Customize what happens after a form is submitted ❌ No ✅ Yes
Route submissions to different people ❌ No ✅ Yes
Display dynamic sections within the form ✅ Yes ❌ No
Trigger follow-up actions based on form inputs ❌ No ✅ Yes

 

Tips for Using Logic Effectively

 

Use Form Logic to keep your forms clean, relevant, and user-friendly.

 

Use Step Logic to make workflows smarter and more efficient after the form is submitted.

 

If you’re not sure where logic belongs, ask: “Does this happen during the form experience, or after submission?”

Related articles

Comments

0 comments

Article is closed for comments.