Conditional Logic Returning Invalid Input when Record Length = 0

[Cole_Wedemeier]

Hello!

There are a LOT of posts regarding the popular error of "Received Invalid Input" but in my search I didn't find anything that was specific to the conditional logic of the automation being the area that returned the error.

I've created a video to show how the conditional logic works when the list properties length = 1, but if it = 0, then the conditional logic check returns the "Received Invalid Input" error. 

Any help is appreciated.

[TheTimeSavingCo]

Hmm I tried testing out an automation that had a conditional on a lookup of a linked field and it worked fine, and so I figure your setup's different.  If you could let me know what field you're looking up I'd love to test it out! 

[dilipborad]

Hello @Cole_Wedemeier 
First and most importantly, please show the field type of every linked record and some sample data. That makes more sense.
@TheTimeSavingCo you've tried one example, but the real issue here is the return type of data.

At first glance at your shared video, it looks like whenever data comes(with the right data), it returns an object and the length calculation is also different.
Just for a quick suggestion try "null" if it fixes your issue. Otherwise please share more table data types with some of the sample data.

👍

[Cole_Wedemeier]

@dilipborad and @TheTimeSavingCo 

I have tried putting "null" into the conditional rule, but it just disappears and Airtable thinks the condition is not completely input yet.

I've created a sample base for you to see the fields and how they are interconnected. While that won't give you the automation, you can see the fields.

Let me walk you through that particular step in the automation. 
Conditional Goal: If someone does not have an Onboarding Form record, which is linked to the Client List table,  then send a gmail email to them. 

Records to work with: 
Client Rita = NO Onboarding Form
Client Crystal = HAS Onboarding Form

Conditions are in image. Note: the "Onboarding Form" is a linked record to the Client List. The Client List is then a linked record on the Results Tracking table to which the automation is being built on for a trigger of "When form is submitted"

Full Automation:
Trigger: When a form is submitted

Action: Update Record

Conditional Action 1: If total audience growth ≤ 0.24 AND Movement Makers Qualified (from client list) (from results tracking) length = 0

Conditional Action 2: If total audience growth ≥ 0.25 AND Movement Makers Qualified (from client list) (from results tracking) length = 0

Conditional Action 3 (where I'm getting stuck)
if Onboarding Form (from Client List) length = 0

[dilipborad · Accepted solution]

Hello @Cole_Wedemeier 
Thanks for the detailed explanation and also share the base.

I've tried things on my side, Now first see this screenshot.

1) Add the "Find Records" step before conditions.
Note: I've used basic conditions, but if you need to cross-check multiple fields then conditions may vary.
2) In the conditions, just use simple condition for the length check based on the "Find Records" step

I hope this fixes your issues. 👍

[Cole_Wedemeier]

@dilipborad I had to try several variations of the Find Record, but ultimately it was the solution. Thank you so much!