Skip to main content

Hello,

I have a pretty complex Zap, it already has three tiers of Paths, why you are only allowed three I do not know. Because of this I use two Find Member steps that look for a user on the CIrcle.so platform. I have two of these steps because I can potentially pull two different emails (billing and normal).

Now these member steps just run one after the other but they keep erroring and stopping the Zap with a “missing email” error. The Find Member task has this option underlined below:

 

I thought this would make the Zap run as no search result is found but it obviously errors before getting to this point. That’s fine I suppose, although I do wish there was an ignore error option and move on. I have found the error handling function and I could get the Zap to work with a good bit of rearranging. However now I am thinking of possible future scenarios and I’m unsure what I’d need to do to achieve it.

As explained I have multiple emails to work with, Users could be in one of three categories:

  1. Has billing email only
  2. Has normal email only
  3. Has billing and normal email

I can see me wanting to do something with users that match one of the three above. Now I know what I’m doing with Paths but what if say I wanted to use the Find Member task for Circle.so, how could I split the outcome of the next stage of the Zap. Like a nested If statement or If, Then, Else statement in programming?

A scenario might be: If member has billing and normal email then do something

Just wondering what others would do in this scenario given that there will always be an error thrown with missing data.

Thanks

Hi @DisruptiveHR 

Try adding this Zap step: Formatter > Text > Default Value

Sets a default value if an input variable is blank/empty/missing null.

You could use a default email address that will never match, then handle accordingly.

 


Hi @DisruptiveHR,
 
We just wanted to see how everything is going with your Zap. Did Troy's recommendation get the job done? Feel free to reach out if you need further assistance with your Zap. We're glad to address any concerns and assist you.
 
We're looking forward to your response.


Hi Troy,

Interesting work around and I could see it being useful. Unfortunately, later in the Zap I test for the presence of an email to see whether they have a billing email address or not.

I suppose I could put a non email default value in, hmm, let me have a play around with it and see. I will report back.

However, I am unsure this is any better than using error handling apart from not having to rearrange everything. I suppose it probably makes the IF logic easier for the future.

Thanks


OK it works and I like it. I just used 123456789 as the default text if an email is not found, the resulting search does not find anyone and my test later on for an “@” in the field is unaffected.

Nice workaround, thanks again


Hi @DisruptiveHR,

 

Wow! Thank you for confirming that Troy’s resolution got the Zap running. This will significantly help our Community members to have as a reference for the same issue.