Product documentation Docs
    • English
    • Deutsch
    • 日本語
    • 한국어
    • Français
  • More Sites
    • Now Community
    • Developer Site
    • Knowledge Base
    • Product Information
    • ServiceNow.com
    • Training
    • Customer Success Center
    • ServiceNow Support Videos
  • Log in

Product documentation

  • Home
How search works:
  • Punctuation and capital letters are ignored
  • Special characters like underscores (_) are removed
  • Known synonyms are applied
  • The most relevant topics (based on weighting and matching to search terms) are listed first in search results
Topics are ranked in search results by how closely they match your search terms
  • A match on the entire phrase you typed
  • A match on part of the phrase you typed
  • A match on ALL of the terms in the phrase you typed
  • A match on ANY of the terms in the phrase you typed

Note: Matches in titles are always highly ranked.

  • Release version
    Table of Contents
    • Now Platform capabilities
Table of Contents
Choose your release version
    Home New York Now Platform Capabilities Now Platform capabilities Flow Designer Flows Create a flow Create a flow with an inbound email trigger Allow multiple triggers to process an inbound email

    Allow multiple triggers to process an inbound email

    • Save as PDF Selected topic Topic & subtopics All topics in contents
    • Unsubscribe Log in to subscribe to topics and get notified when content changes.
    • Share this page

    Allow multiple triggers to process an inbound email

    Configure Flow Designer to allow an inbound email to be processed by multiple inbound email triggers in a specific order.

    Before you begin

    Role required: admin

    About this task

    Although you can process an inbound email with multiple inbound email actions, you can't process an inbound email with multiple flows by default. You can add a system property to let process owners use multiple triggers to process an inbound email.
    Warning: Allowing multiple triggers to process an inbound email may increase maintenance and decrease system performance.

    Procedure

    1. Add a property with the following settings:
      • Name: glide.hub.flow.inbound_email_trigger.show_advanced
      • Type: true | false
      • Value: true

      After you activate the system property, the Order and Stop processing fields appear on the inbound email trigger, as shown in the following figure.

      Stop processing and Order fields appear on Inbound Email trigger.
    2. Create multiple flows with an inbound email trigger.

      For more information, see Create a flow with an inbound email trigger.

    3. Specify the processing order for each of the inbound email flows:
      1. Open each flow and enter a value in the Order field.

        To give the flow higher priority over other flows, enter a lower number.

      2. Enable or disable stop processing for each flow in your sequence.

        To allow an inbound email to be processed by the next flow in your sequence, clear the Stop processing option.

        To end the sequence on a particular flow, leave the option selected in that flow.

    Tags:

    Feedback
    On this page

    Previous topic

    Next topic

    • Contact Us
    • Careers
    • Terms of Use
    • Privacy Statement
    • Sitemap
    • © ServiceNow. All rights reserved.

    Release version
    Choose your release version

      Allow multiple triggers to process an inbound email

      • Save as PDF Selected topic Topic & subtopics All topics in contents
      • Unsubscribe Log in to subscribe to topics and get notified when content changes.
      • Share this page

      Allow multiple triggers to process an inbound email

      Configure Flow Designer to allow an inbound email to be processed by multiple inbound email triggers in a specific order.

      Before you begin

      Role required: admin

      About this task

      Although you can process an inbound email with multiple inbound email actions, you can't process an inbound email with multiple flows by default. You can add a system property to let process owners use multiple triggers to process an inbound email.
      Warning: Allowing multiple triggers to process an inbound email may increase maintenance and decrease system performance.

      Procedure

      1. Add a property with the following settings:
        • Name: glide.hub.flow.inbound_email_trigger.show_advanced
        • Type: true | false
        • Value: true

        After you activate the system property, the Order and Stop processing fields appear on the inbound email trigger, as shown in the following figure.

        Stop processing and Order fields appear on Inbound Email trigger.
      2. Create multiple flows with an inbound email trigger.

        For more information, see Create a flow with an inbound email trigger.

      3. Specify the processing order for each of the inbound email flows:
        1. Open each flow and enter a value in the Order field.

          To give the flow higher priority over other flows, enter a lower number.

        2. Enable or disable stop processing for each flow in your sequence.

          To allow an inbound email to be processed by the next flow in your sequence, clear the Stop processing option.

          To end the sequence on a particular flow, leave the option selected in that flow.

      Tags:

      Feedback

          Share this page

          Got it! Feel free to add a comment
          To share your product suggestions, visit the Idea Portal.
          Please let us know how to improve this content

          Check any that apply

          To share your product suggestions, visit the Idea Portal.
          Confirm

          We were unable to find "Coaching" in Jakarta. Would you like to search instead?

          No Yes
          • Contact Us
          • Careers
          • Terms of Use
          • Privacy Statement
          • Sitemap
          • © ServiceNow. All rights reserved.

          Subscribe Subscribed Unsubscribe Last updated: Tags: January February March April May June July August September October November December No Results Found Versions Search preferences successfully updated My release version successfully updated My release version successfully deleted An error has occurred. Please try again later. You have been unsubscribed from all topics. You are now subscribed to and will receive notifications if any changes are made to this page. You have been unsubscribed from this content Thank you for your feedback. Form temporarily unavailable. Please try again or contact  docfeedback@servicenow.com  to submit your comments. The topic you requested does not exist in the release. You were redirected to a related topic instead. The available release versions for this topic are listed There is no specific version for this documentation. Explore products Click to go to the page. Release notes and upgrades Click to open the dropdown menu. Delete Remove No selected version Reset This field is required You are already subscribed to this topic Attach screenshot The file you uploaded exceeds the allowed file size of 20MB. Please try again with a smaller file. Please complete the reCAPTCHA step to attach a screenshot
          Log in to personalize your search results and subscribe to topics
          No, thanks Login