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.

I am using airtable with softr for a client portal, and I am trying to configure an automation to send an email to the portal admin alerting them that a user has logged in for the first time. I have a "users" table in airtable which maps to the "users" table in softr. I have last modified turned "on" in air table. Softr maintains it's own "last seen" field which I have mapped into a matching date field in air table. 

The basic logic is that the "last seen" field is empty until a user logs in. So I would think that I would just need to trigger when the "last seen" is part of the "last modified" history? But this alone would result in an email going out every time the last seen field changes which would be every time the user logs in.

I only care about the FIRST time, so I would need a way to check if the "last seen" field was previously empty, then compare it to the current field contents. I just do not understand where I would get the "previous" value from?

 

Hi there, ​@Redwolf Sports Media! 👋

If the trigger for the Zap doesn’t provide a previous date value to compare against, then maybe you could add another field to the Airtable to track whether it’s the first or a subsequent run of the Zap for the user. One approach could be adding a checkbox in Airtable that the Zap marks when it first adds value into the last seen field in Airtable.

For that approach you’d use a Filter step to check whether the checkbox is not already checked before proceeding. If it’s unchecked, the Zap will then update the last seen field in Airtable with the last seen date from Softr and mark the checkbox for the record as checked. And if it’s already checked then the Zap won’t update the user’s record in Airtable.

Do you think that approach could work? If you give that a try and run into any trouble, or have any follow-up questions just let me know!

Thank you, I solved this in a similar fashion using the native airtable automation functions, where the automation populates a new field called “first login” with date from the “last seen” field (only when the “first login” field is empty). Then sends an email with the containing the user’s name and the first login date.

Pretty much aligned with your idea. Thank you!

That’s an amazing news ​@Redwolf Sports Media! We’re glad to hear that the issue is now resolved!

If you have any other questions, please don’t hesitate to reach out to the Community. We’re always happy to help! 🤗

Thanks so much for sharing your solution, ​@Redwolf Sports Media. Great minds think alike! 😉

Terms & ConditionsAccessibility statement