Is it possible to output an empty value in a Tables lookup table ?
I have a simple Table being used as a lookup table in a Zap. What I would like to know is if it is possible to have an entry in the table be empty, so that it outputs nothing as the value.
Zap details:
The step in question is a Find Record step > App: Zapier Tables > Event: Find Record
The Table looks at the Key column (numerical) and pulls in a corresponding text value from the next column
The next step in the Zap writes to SharePoint Online and pulls from the data pulled in this previous step.
The issue is that sometimes the field is empty, and therefore the lookup table needs to be able to carry over an empty value. And right now this is making the Zap error out.
Thank you!
Page 1 / 1
Hi @JoshMNF
For us to have more info, post screenshots showing how your Zap steps are outlined and configured in EDIT mode, and outlined a specific example for us so we can trace the data flow between steps.
Here are some screenshots.
The Path in the Zap using the table:
The Table lookup Step:
The snip of the table itself, where there is no NULL value (which is my question, can we have one?!)
@JoshMNF
The snip of the table itself, where there is no NULL value (which is my question, can we have one?!)
When in doubt, test it out!
If the Lookup Value can be empty, then another approach would be to set a default value and have a Table Record with that default value.
Zap action: Formatter > Text > Default Value
Hey @Troy Tessalone thank you for the quick responses and the help!
Actually the table DOES have an empty value row:
But the Zap still errors out when the field is empty. Maybe something actually needs to be in those table fields?
As for your other recommendation to use Formatter-- sorry, I am fairly new to Zapier and unsure how and where to set this. I have this Formatter step before the Table Lookup. But I am unsure what to put here:
And that made the empty field work! It now writes to SPO as “Unknown”.
Now the issue is that when the NAICS code field is filed out in Pipedrive, it is writing the incorrect thing to SPO!! Something must have gone wrong with the table or the code from Pipedrive. Looking into it!