Skip to main content
Question

Lookup record from table that may or may not have a match

  • October 31, 2025
  • 4 replies
  • 67 views

Forum|alt.badge.img+5

I have an Airtable base for events I host. We get repeat attendees at the different events. I would like to send text messages to the participants at a particular event if they opt in for text messages. I have this all working.

The issue I need help with is that I’d like to keep a master list of participants and their phone numbers who have already opted in at a previous event so they don’t have to opt-in every time. I’m looking for suggestions on how to handle this. 

When I add a participant for a new event, it needs to check the master opt-in table to see if there is a match. There will be records that don’t have a match as they have not completed the opt-in previously and opt-in records that won’t have a participant as they are not attending this event. 

As I write this, I’m wondering if an automation is where I need to go for this???

4 replies

TheTimeSavingCo
Forum|alt.badge.img+31

Yeah automation makes sense.  Could you provide some screenshots of your tables?  How are the attendees selecting the opt in?  

Assuming you have a Participation table where each record represents a single Person and a link to an Event, you could create a lookup field to grab their Opt In details:

And if you were using an Airtable form for this you could then use that lookup field to customize whether the ‘Opt In’ checkbox field is visible in the field or not.  Not really sure if this would work for you though, and if you could provide more details on your workflow I’ll see what I can do to help!


Forum|alt.badge.img+5
  • Author
  • New Participant
  • October 31, 2025

Sure, here are a couple of screenshots that include the relevant data. I load the data from another Airtable base with a simple copy and paste. The participants use a Fillout form to opt-in and create the record in the Opt-in table. That’s all working fine. But now I would like to make a modification and have a master opt-in table so that participants don’t have to opt-in if they have already done so at a previous event. But that means some participants will have matches and others won't. Also there will be records in the Opt-in table that won’t have matches with participants. I’m not sure if that would be a new table or just modify the existing Opt-in table… The NACSW number is unique to each handler (participant). 

I appreciate any suggestions you have on how best to manage this process. I don’t want to have to manually link the records if I can avoid it. 

 


TheTimeSavingCo
Forum|alt.badge.img+31

Hmm, do you have a table where each record is a single NACSW number?  If not, try creating a new table with that data, and the quick way to populate it would be to:

  1. Create the new table called ‘NACSW #’ or something
  2. In ‘Entries’, create a linked field to NACSW #
  3. Click the field header of the field ‘NACSW Number’, which will select the entire column
    1. Do this in a view where no records are hidden
  4. Hit CMD / CTRL + C to copy
  5. Click the field header of the field ‘NACSW #’, i.e. the linked field
  6. Hit CMD / CTRL + V to paste
  7. This will create one record per unique NACSW number, regardless of how many Entry records may have that unique number

In the table NACSW #, create a lookup field that’ll display from entries that indicates whether the person has opted in before, and then create a view to filter those out.  You should now have a list of all the people who haven’t opted in yet that you can reach out to, does that help?


Forum|alt.badge.img+5
  • Author
  • New Participant
  • November 1, 2025

Thank you. I’ll take a look at this when I get a chance and let you know if I have any questions.