Include conditional logic in wait steps using an "CONDITION/ATTRIBUTE" type | Community
Skip to main content
Dan_Stevens_
Dan_Stevens_
New Participant
April 4, 2017
New

Include conditional logic in wait steps using an "CONDITION/ATTRIBUTE" type

  • April 4, 2017
  • 5 replies
  • 6942 views

We've run into a scenario where we need to include a wait step so that an alert isn't sent out prematurely after a specific triggered activity.  In this case, the alert cannot be sent out until the boolean field has changed to "NO" in CRM and then synced back to Marketo as "FALSE".

Today, there are three types of wait steps:

  1. Duration
  2. Date
  3. Token

I'm suggesting a fourth - called "Condition/Attribute".  Which would allow a lead to wait until an attribute contains a specific value.  It would look very similar to a "choice" within a flow step.  For example:

You might ask, why not just include this as a choice within the "send alert" flow step.  The reason is if the choice isn't true, then the flow step will just be passed.  Having it as a wait step will ensure the lead cannot progress in the flow until a specific condition is true.

    5 replies

    Fabian_Sockel
    Fabian_Sockel
    Level 3
    July 18, 2022

    We need it desperately 🙂

    M
    mplana
    New Participant
    July 18, 2022

    Yes please, 🔝 !

    C
    carolin-dirks
    New Participant
    July 18, 2022

    This feature would make my life with Marketo < > CRM communication so much easier. Top 🔝 🔝 🔝 

    K
    kh-lschutte
    New Participant
    February 6, 2020
    No text available
    Grégoire_Miche2
    Grégoire_Miche2
    New Participant
    April 4, 2017

    Hi Dan,

    This would be a tremendous improvement as it would enable to completely secure race conditions and manage order of operations.

    Look at this idea and the comment I made a while ago, I think it also applies here:

    -Greg

      Dan_Stevens_
      Dan_Stevens_Author
      New Participant
      April 4, 2017

      Hi Greg - I actually came across this and decided to create a new one that included a broader scope; and was more current (that one is from 2014).  I agree - this would alleviate many of the race conditions we're experiencing today.

      Grégoire_Miche2
      Grégoire_Miche2
      New Participant
      April 4, 2017

      HI again Dan,

      I fact, as I wrote in the other one, I would probably require an event broader one: "wait until trigger fires". This trigger could be "data value changes, new value is True"

      We also need to be able to combine is with way to skip the wait if the condition is already true. So the perfect thing would be

      • If Condition is true Wait 0 minutes
      • Else until condition is met (trigger)
      • Wait max 5 days or wait max until April 20th...

      -Greg

      Terms & ConditionsAccessibility statement

      Loading footer...