This powerful feature allows you to override standard submission routing and direct submissions to a different destination when specific conditions are met.
Important: Submission destination field rules take precedence over all other submission routing settings.
What Are Submission Destinations?
A submission destination defines where submission data is sent after a user completes a gate.
Common destinations include:
Marketing automation platforms
CRMs
Webhooks
Other POST form endpoints
Other configured integrations
Routing Priority
When configured, a submission destination field rule will always take precedence over other routing settings.
The routing order priority is:
Submission Destination Field Rule
Overridden Form Submission Destination in Form Type
Default Submission Destination
If a submission destination is set by a field rule, Formulayt will use that destination regardless of any other routing configuration.
When Would You Use This?
Submission destination field rules are particularly useful when you need different submission behavior without creating additional form types.
Example 1: Gate-Specific Routing
One of the most common use cases is overriding routing for a specific gate while continuing to use a shared form type.
Your standard Contact Us gates submit to your primary CRM.
However, for a specific campaign, one gate needs to send submissions to a different system.
Rather than creating a new form type, you can:
Continue using the existing form type
Create a submission destination rule for one of the fields used on the gate
Route only that gate's submissions to the alternative destination
This helps maintain consistency while allowing exceptions where required.
Example 2: Country-Based Routing
Your organization normally sends all submissions to:
CRM 1
However, submissions from users in Germany need to be sent to:
CRM 2
You can create a rule based on the Country field:
If Country = Germany
and configure the rule to update the submission destination to CRM 2.
All other submissions where the Country field is present will continue to be sent to CRM 1.
This allows a single gate to support multiple routing requirements without creating duplicate gates or form types.
Example 3: Customer-based routing
Your organization normally sends new prospect submissions to your marketing automation platform (MAP).
However if a user is already known to be a customer, you may want their submissions to be sent directly to your CRM instead.
You can create a rule based on the relevant customer status field:
If Customer Status = Customer
And configure the rule to update the submission destination to your CRM
Known customers will then be routed to the CRM, while other submissions will continue to be sent to the MAP.
This can be useful when you want submissions from existing customers to follow a different process from those of prospects.
How to Configure a Submission Destination Rule
Open the field you wish to use as the trigger.
Create or edit a field rule.
Configure the rule conditions.
Select Update Submission Destination as the rule action.
Choose the destination that submissions should be sent to when the rule conditions are met.
Save your changes.
Once the rule conditions are satisfied, submissions will be routed to the selected destination.
Important: You do not need to add the rule to every field used on the form. By adding the rule to a single field this will submit the entire gate to the new destination.
Important Considerations
Because submission destination field rules override all other routing settings, we recommend:
Carefully testing all routing scenarios before publishing changes
Documenting any gate specific routing overrides
Reviewing rules regularly to ensure submissions continue to reach the correct destination
Important: Take care when creating multiple submission destination rules, particularly when rules are applied to different fields. If two or more rules that specify different submission destinations are triggered at the same time, either destination could be applied. This means your routing may not be consistent. Make sure your rules are configured so that conflicting submission destination rules cannot trigger at the same time. This is especially important when multiple teams manage gates and form types.
Best Practices
We recommend using submission destination rules when:
Routing depends on user selections
A single gate requires different routing from the standard form type
You want to reuse existing form types while supporting multiple destinations
Avoid using submission destination field rules when a simpler default routing configuration would achieve the same result.
Summary
Submission destination field rules allow you to dynamically control where submissions are sent.
Key points to remember:
Submission destination field rules override all other routing settings
They take precedence over both specific form routing and default submissions
They are ideal for complex or gate specific routing requirements
They allow you to reuse form types without creating unnecessary duplicates
Used correctly, submission destination field rules provide a flexible and powerful way to manage submission routing across your Formulayt account.
Looking to send submissions to two destinations? See Secondary Form Submissions for more information.
Not sure whether to use Submission Destination Field Rules or Secondary Submission URLs? See When to Use Submission Destination Field Rules vs Secondary Submission URLs for guidance.