Dynamic Form Generator for Airtable and Baserow - n8n Workflow

Automation developers and technical users looking to leverage the power of the n8n node for dynamic UI generation.
Organizations seeking to replace restrictive, proprietary database forms (Airtable, Baserow) with customizable n8n forms.
Users interested in understanding how to implement custom logic and schema mapping within a single n8n workflow.
Anyone looking for advanced n8n templates demonstrating complex data flow and custom scripting.

This sophisticated n8n workflow demonstrates the power and flexibility of the n8n platform by dynamically generating custom forms based on external database schemas (Airtable and Baserow). Traditional database forms often lack advanced logic or customization options. This n8n workflow solves that problem by retrieving the base schema using dedicated n8n node connections (Airtable) or HTTP requests (Baserow), mapping native field types to n8n form fields using custom code, and then rendering the form dynamically. The value provided by this n8n template is immense, offering complete control over the input experience while ensuring accurate data insertion, including complex file and attachment handling, into your target database. This whole process leverages the n8n trigger to initiate the dynamic rendering sequence.

This n8n workflow operates on two parallel paths, initiated by a form n8n trigger for either Airtable or Baserow.

1. Trigger and Schema Retrieval: The user first selects the target Base/Table ID via the initial form n8n trigger. For the Airtable path, the workflow uses the Airtable n8n node to retrieve the base schema, filters for the selected table, and then splits out the individual fields. For the Baserow path, an HTTP Request n8n node fetches the table fields.


2. Schema Conversion (Code n8n node): A crucial Code n8n node, Covert to n8n Form Fields, transforms the raw database field metadata (e.g., singleLineText, multipleSelects) into the specific JSON format required by the n8n form renderer. Any unsupported field types are filtered out. The fields are then aggregated.


3. Dynamic Rendering: The aggregated JSON field definitions are fed into a subsequent Form n8n node (Render Form/Render Form1). This n8n node uses the dynamic JSON definition to display a complete, custom form to the end user.


4. Data Preparation and Creation: Upon form submission, the data is processed by a preparation Code n8n node (Prep Data for Insert), which cleans the data, typecasts booleans, and crucially, removes file/attachment fields, as these must be handled separately. The main record is then created in Airtable or Baserow using the Airtable n8n node or an HTTP Request n8n node.


5. Attachment Handling: The Files To List Code n8n node extracts the binary file data associated with the submission. These files are then uploaded. For Airtable, the Update Airtable Row HTTP Request n8n node handles the file upload directly into the newly created record. For Baserow, files are uploaded first using a dedicated Baserow Upload File HTTP Request n8n node, the references are grouped by the Group By FieldName Code n8n node, and finally, the row is updated using the Baserow Update Row HTTP Request n8n node. The n8n workflow concludes with a success message displayed by the final Form n8n node.

To use this n8n workflow, follow these steps:

1. Import: Copy the entire n8n workflow JSON provided and import it into your n8n instance.


2. Airtable Credentials: Ensure you have configured an Airtable Personal Access Token credential, linked to the relevant Airtable n8n node (Get Base Schema and Airtable Create Record).


3. Baserow Credentials: Configure a generic HTTP Header Auth credential for Baserow API access, linking it to the Baserow HTTP Request n8n node instances.


4. Initial Configuration: In the first two n8n trigger nodes (On form submission and On form submission1), update the default BaseId and TableId dropdown options to match the IDs of the databases you wish to build forms from. Look for the Sticky Notes labeled with '🚨 Change your ID here!' for guidance.


5. Activation: Save and activate the n8n workflow. Access the URL provided by the initial n8n trigger node to begin dynamic form generation.

On form submission / On form submission1 (Form Trigger n8n node): Serves as the initial n8n trigger. It collects the user's selection (BaseId and TableId) necessary to start dynamically generating the target form.
Get Base Schema (Airtable n8n node): Connects to Airtable to retrieve the full schema metadata for the specified Base, enabling the dynamic creation of the n8n form fields.
Baserow List Fields (HTTP Request n8n node): Used in the Baserow path to call the Baserow API and retrieve table field details.
Covert to n8n Form Fields / Covert to n8n Form Fields1 (Code n8n node): This is a key n8n node where custom JavaScript logic translates native database field types (e.g., date, multiselect) into the required n8n JSON form field schema structure.
Render Form / Render Form1 (Form n8n node): Renders the dynamically generated n8n form using the JSON output created in the previous step. This is where the user interacts to submit data.
Prep Data for Insert (Code n8n node): Prepares the submitted form data for API insertion by removing file fields and correctly typecasting data for the creation API n8n node calls.
Airtable Create Record (Airtable n8n node) / Baserow Create Row (HTTP Request n8n node): Creates the new row in the respective database using the prepared non-file data.
Files To List (Code n8n node): Extracts binary file data from the n8n submission, separating it into individual items for subsequent upload, demonstrating powerful file handling within the n8n workflow.

• Update Airtable Row / Baserow Update Row (HTTP Request n8n node): Handles the final step of attaching files to the newly created record. This requires different logic for each platform due to unique API requirements, managed expertly within this n8n workflow.