Grupolive Participant Directory: Airtable + Make.com as Backend by Juani VallejosGrupolive Participant Directory: Airtable + Make.com as Backend by Juani Vallejos

Grupolive Participant Directory: Airtable + Make.com as Backend

Portfolio project
Juani Vallejos
Every season, Grupolive sends participants to work in different cities across the US. Once they land, the first question is always the same: who else from the program is here?
I built a private directory to answer that. Participants enter their ID number, and the app shows them the other participants in the same city, with email, location and a one-click WhatsApp button.
Directory login
Directory login
Directory results
Directory results

How it works

Airtable is the database. The team already manages participants there, so the directory reads straight from the same base. No data to sync and no extra admin panel.
Make.com is the API. The front end talks to Make webhooks that handle log in, authentication and terms, and return only the data each participant is allowed to see.
Light front end on Vercel. Serverless functions handle the requests between the site and Make, so there's no server to maintain.
Admins control what's visible. They decide from Airtable which fields and which participants show up, without touching code.
Make scenario: log in
Make scenario: log in
Make scenario: auth and terms
Make scenario: auth and terms
Make scenario: server response
Make scenario: server response

Why this approach

It shipped fast and costs almost nothing to run. The team keeps working in Airtable like always, and the directory updates on its own. A good example of using no-code tools as a real backend when the use case fits.

0 likes · 38 views · Jul 29, 2024

A private directory where Grupolive participants log in with their ID and find who else is in their US city. Airtable is the database, Make.com is the API, no traditional backend.

Tags