Skip to main content

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Learning Resources
All of our best learning resources can be found here.

Featured Articles Show & Tell Zapier's products AI Hub Zapier Tools Hub

Share your knowledge
Give back to the Community by sharing your automation wins and helping to answer questions.

Share your success See unanswered questions User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

  • How do I use an interface’s managed user email as a variable in a Zap?

    After the managed user adds a row to a table in an interface, I want to update a hidden field containing their email (used for a dynamic filter) so that other managed users won’t see the row they added. 

    I’m having trouble finding a way to use “current user’s email” as a variable in a zap that updates the hidden field in the table when they make a new row. 

    Feel free to ask clarifying questions if needed, Thank you!

Hi there @jacob.mirth. Welcome to the Community! 😁

If you set the default value of the hidden field on the form to be {{currentUser.email}} that should populate the equivalent field in the table with the user’s email address:

818024769863d3a5d45bc8b3fc6d704c.png

Can you give that a try and let me know if that works as hoped?

Hey!

Thanks for the quick reply! So the way the user adds a row to the interface is through the “create new ___” button that comes with the table component by default, so there isn’t an actual form where I can edit these settings.

For now I’ll just remove that button and add a separate form component so I can use this fix. That should work just as well!

Thanks again

Thanks for getting back to me, @jacob.mirth. Glad to hear adding a form component to the interface to allow you to set the default value will be a viable workaround for you here.

Seems like you’re all set for now but do let us know if you need any further help at all. In the meantime, happy Zapping! ⚡️

Terms & Conditions