|
/ Documentation /Integrations/ Conditional Logic with Integrations

Conditional Logic with Integrations

Feature Overview

SureForms now offers advanced Conditional Logic for Integrations, allowing you to control exactly when an integration should run. Whether you’re sending data to HubSpot, MailPoet, Webhooks, CRMs, Email tools, or any other supported integration, this feature ensures that actions are triggered only when your defined conditions are met.

By basing conditions on form field values, you gain precise control over automation and can streamline workflows significantly.

Key Benefits

  • Targeted Execution: Trigger integrations only when needed, reducing unnecessary actions.
  • Customizable Logic: Set conditions that match your specific workflow requirements.
  • Improved Efficiency: Prevent redundant or irrelevant data from being sent to your external tools.

Logic Matching Modes

Before setting conditions, choose how your logic should behave:

Any

The integration will run if at least one of the conditions is satisfied.

All

The integration will run only when all defined conditions are satisfied.

This flexibility allows you to configure simple OR-based rules or more advanced AND-based rules depending on your use case.

Conditional Operators

SureForms provides a comprehensive set of operators to define your logic:

  • Is: Triggers when the field value exactly matches the specified value.
  • Is Not: Triggers when the field value does not match the specified value.
  • Is Greater Than: Triggers if the value is greater than the specified number.
  • Is Greater Than or Equal To: Triggers when the value is equal to or greater.
  • Is Less Than: Triggers if the value is less than the specified number.
  • Is Less Than or Equal To: Triggers when the value is equal to or less.
  • Starts With: Triggers when the field value begins with the specified text.
  • Ends With: Triggers when the field value ends with the specified text.
  • Contains: Triggers if the field value includes the specified text.
  • Does Not Contain: Triggers when the field value does not include the specified text.
  • Regex: Triggers based on a matching regex pattern (ideal for advanced text validation).

How It Works

Defining Conditions

You can create one or multiple conditions by selecting a field, choosing an operator, and entering the comparison value.

Integration Execution

An integration fires based on:

  • Your selected matching mode (Any / All)
  • Whether the submitted field data satisfies your defined conditions

If the logic is not satisfied, the integration will be skipped automatically.

Use Cases

Here are a few scenarios where Conditional Logic for Integrations can be highly effective:

1. Send data to HubSpot only when a lead qualifies

Matching Mode: Any / All

Conditions:

  • Lead Status equals “Hot Lead”
  • Budget is greater than 50000

Outcome: The integration sends data to HubSpot only when the lead matches your qualification criteria.

2. Add a subscriber to MailPoet only when they opt in

Matching Mode: All

Conditions:

  • Newsletter Opt-in equals “Yes”
  • Consent Checkbox equals “Accepted”

Outcome: The subscriber is added to your MailPoet list only when they have explicitly opted in.

3. Trigger a webhook only for specific submission types

Matching Mode: Any

Conditions:

  • Form Type equals “Booking Request”
  • Selected Plan does not equal “Free”

Outcome: The webhook triggers only for premium or request-type submissions.

4. Sync data to your CRM only when it meets segmentation rules

Matching Mode: All

Conditions:

  • Company Size is greater than 10
  • Industry equals “Healthcare”

Outcome: The entry is pushed to your CRM only for valid business leads.

5. Send email notifications only for high-priority messages

Matching Mode: All

Conditions:

  • Support Category equals “Urgent”
  • Issue Severity is greater than 3

Outcome: Notifications are sent only for critical support requests.

6. Route entries to different integrations based on scoring

Matching Mode: AnyConditions:

  • Score is greater than 80
  • Score is less than 80
  • Score equals 0

Outcome: Depending on the score, entries are routed to:

  • HubSpot for high scores
  • MailPoet List B for mid scores
  • Webhook (support team) for zero scores

7. Filter survey or feedback data before sending

Matching Mode: All

Conditions:

  • Rating is less than 3
  • Feedback contains “refund”

Outcome: Only negative or refund-related feedback is forwarded to the relevant team/tool.

8. Prevent incomplete or unwanted data from syncing

Matching Mode: Any

Conditions:

  • Email contains “@example.com”
  • Phone Number equals empty

Outcome: Entries with invalid or placeholder contact details are excluded from sync.

9. Send e-commerce entries only when purchase criteria are met

Matching Mode: All

Conditions:

  • Order Total is greater than 1000
  • Product Category equals “Premium”

Outcome: Only high-value premium purchases are sent to the integrated tool.

10. Automatically route entries to the correct team

Matching Mode: Any / All

Conditions:

  • Department equals “HR”
  • Department equals “Sales”
  • Department equals “Technical”

Outcome: Entries are routed to the HR email, CRM, or webhook endpoint depending on the department selected.

Was this doc helpful?
What went wrong?

We don't respond to the article feedback, we use it to improve our support content.

Need help? Contact Support
On this page
Scroll to Top