Data Routing Using Conditional Logic

Routing Logic uses conditional logic to help you customize the way that you handle and process your submissions, giving you more control once a user has submitted your form. Email Logic works with Notification Emails, Confirmation Emails, URL Redirects, and 3rd Party Integrations.

Note: The only fields eligible for Routing Logic are Dropdown Lists, Event fields, Checkboxes, Number fields, and Radio buttons

Notification/Confirmation Emails

Setting up Routing Logic on your Notification Emails, you can quickly route forms to different people in your organization. You can direct submissions based on the user's responses. i.e. if a user selects "Sales" on your contact form, only members of your Sales team will receive a notification.  

Email Logic for Confirmation Emails is perfect for customizing who receives emails after submitting and which message they receive.  For instance, the confirmation email you send can have different messaging depending on which option the end user chooses.

Submit Actions

Routing Logic can be used in very powerful ways to redirect users after they have submitted their form using different types of Submit Actions. You can use Routing Logic to show different custom messages, similar to the Confirmation Emails, or you can use it to redirect to an external URL or to PayPal.


Redirecting to an external URL or to a payment integration is great for order forms with multiple payment types. You can set up a field that has multiple payment types options (PayPal, Credit Card, Check) then use routing logic to redirect users accordingly.


A common example of this would be if you wanted to provide your end users the option to pay via Check or through a Payment processor using their credit card.  In this scenario you can redirect credit card paying users to your payment processor to complete the online payments and another redirect action (a custom message) for users paying via Check.



- There is no "rollback" option in the integrations.  If someone has an Authorize.Net charge first and MailChimp second, assuming Authorize.Net passes and MailChimp fails, the submission fails but the credit card was already charged.

- If you change the text of an option that triggers the Data Routing you will need to re-save the Submit Action to update the Data Routing.


Was this article helpful?
15 out of 30 found this helpful