We use Airtable heavily with parent --> child relationships and are trying to standardize our workflows using record templates, especially within Interfaces while reducing the amount of automations used in this aspect of our workflow.
What we’re trying to do (high level)
We want to generate groups of task records (child records) and link them to a parent record that already exists. We only ever work in interfaces so it must have a way to function for our users there.
- Using record templates or a native grouping feature
- Without relying on automations
- Without creating a new parent record
Current setup
We have many tables that act as a parent record and then one table that is the child record (tasks). Most of them have a pre- and post- step of creation, some with 3 steps where specific tasks are generated at each phase (e.g. Interest, Application, and Decision). Below is an example of 2 steps (pre-award and post-award).
- Pre-award tasks (works well)
- Parent record is created via an Interface form using the native record template tool
- The template creates the parent record and a predefined set of child task records with task dependencies and start and end dates linked.
- All relationships are created at once
- Post-award tasks (where we’re stuck)
- The parent record already exists
- Based on a decision (approved / declined), we need to generate a specific set of post-award tasks
- Currently:
- Task sets live in a separate “templates” table (e.g., “Approved Award Tasks”)
- Automations run when a decision field changes or a button is clicked
- The automation finds the correct linked template name (manually linked) and loops through each task in the list and creates the child record and pulls in any fields I have identified including linking the existing parent project
- This works, but we’re trying to reduce the number of automations and automation complexity while also keeping everything inside Interfaces if possible.
My questions for the community
- Is this currently possible using record templates or another native Airtable feature?
- Are there known workarounds without automations?
- Is this a known limitation of record templates today?
- Has anyone solved a similar “post-creation task generation” problem in Interfaces?
Any insights, patterns, or confirmations that this isn’t yet supported would be super helpful.

