Jan 08, 2025 07:46 PM
Hi Airtable Community,
I have an Airtable base for Health & Safety for an event. I have an Airtable form which is populating data in a table called "Declarations" (these come from a subset of our stakeholders). I have a second table called "Inductions", which is being populated via an integration with a Jotform form. This second base includes a broader set of data, but critically everyone who completes the Declaration form also needs to complete the Induction form.
I want to create a third table which summarises who has completed which of these forms, using email and/or company name as the common field.
I'd also like to check this data and link it against other lists in other bases (eg Volunteers, Suppliers), using their contacts to sync data.
I am still something of an Airtable rookie, without coding skills, so looking for an explanation that is accessible please - i want to learn a solution, so i can use it across my Airtables.
Thanks!
Jan 09, 2025 05:10 AM
Hello @WanakaShow,
You need to use and read about how to use Airtable Automation. Getting started with automation in Airtable
It's the same as Zapier or Make if you've already used it for different API and tool integration.
Steps you need to follow.
- Create a summary table that includes relevant fields from both tables.
- What's important here is you need to track the trigger for rows when it's added to your "Declarations" and "Inductions" tables.
- Airtable Automation can read all the details about that specific row(which is added) and then on the next step(action) select the summary table fields that are relevant and come from the tables.
Note: you need to create 2 different automation to handle both of the tables. Both tables have different fields.
Because you've used Jotform that's why I recommend you also check this new form builder called Fillout. They have inbuilt integration with Powerful forms for Airtable.
Fillout can be used for Scheduling, Automation, PDF Fill forms and Payments.
I hope this helps. 👍
Jan 09, 2025 09:09 AM
As dilipborad mentioned, it's automation time!
That said, I don't know if you necessarily need to create a summary table, but you do need a contact table that acts as the link between your declarations and inductions. A lot of this is dependent on your base construction and stuff like your primary fields in tables, but you can do a lot of automated linking with the right setup. A few tips...
All of this can be done no-code in automations, you just have to play around with it. It's a bunch of logic puzzles really.