Automate Airtable & Baserow Form Integration with n8n

What this workflow does

This workflow creates forms automatically from Airtable and Baserow table structures inside n8n.

It takes data submitted through the form and adds it to the right database rows.

Files attached to the form upload separately and connect correctly to records.

This saves time building forms and avoids mistakes in data and file processing.

Who should use this workflow

This workflow is good for people managing projects that use Airtable or Baserow databases.

It helps teams that need to collect data from many users with forms and handle file uploads.

No need to build forms by hand or manually upload attachments later.

Users with some basic knowledge of API keys and n8n node setup can run it.

Tools and services used

• Airtable API: Retrieves table schemas and inserts records.


• Baserow API: Gets table fields and adds rows with uploads.


• n8n Automation platform: Runs the workflow nodes and manages data flow.


• HTTP Request nodes: Make API calls to fetch schemas and upload files.


• Code nodes: Convert schemas to form fields and prepare data.


• Form Trigger and Form nodes: Capture submissions and render forms for users.

How this workflow works (Input → Process → Output)

Inputs

The workflow starts on form submission through a Webhook node or Form Trigger node.

Select BaseId (Airtable) or TableId (Baserow) from dropdown options to specify where data goes.

The submitted data may include text fields and file attachments.

Processing steps

The workflow retrieves the schema for the selected Airtable base or Baserow table using API calls via Airtable or HTTP Request nodes.

It filters the schema to only supported field types and splits those into single items for transformation.

Code nodes map database field types to n8n form fields, like text, email, dropdown, date, or file input.

The form fields are combined into one JSON schema and rendered to the user through the Form node.

Submitted data is prepared by separating file attachments from normal fields, ensuring type castings and correct formatting.

New records are created in Airtable or Baserow using API calls.

Files in the submission upload separately and get associated with the correct records via additional API updates.

Outputs

Records in Airtable or Baserow are created or updated with user data and attachments.

The form shows a message confirming submission success.

Beginner step-by-step: How to use this workflow in n8n

Step 1: Import the workflow

1. Download this workflow file using the Download button on this page.


2. Open your n8n editor dashboard.


3. Select Import from File and upload the downloaded workflow JSON file.

Step 2: Add credentials and configure IDs

4. Add your Airtable Personal Access Token and Baserow API Token in the credentials section.


5. Update BaseId (Airtable) or TableId (Baserow) fields if your database has different values from dropdown options.


6. Check any emails, folder IDs, or channel names if present and change to your own.

Step 3: Test and activate the workflow

7. Trigger the form by opening the webhook URL provided by the Form nodes and submit sample data.


8. Check the execution in n8n to see that data made it into your Airtable or Baserow tables.


9. Activate the workflow switch in n8n to keep it running for production submissions.

If you want to run self-host n8n, follow standard hosting steps.

Customization ideas

• Add new field types by editing the Code nodes to map your database fields to n8n forms.


• Change placeholder text and help hints inside the JSON form schema before rendering.


• Limit form access with authentication nodes before submission triggers.


• Make dropdown options dynamic by requesting table lists through API calls instead of hardcoded values.


• Edit the final form completion message in the Form Completion node for custom text.

Common problems and fixes

No form submission data received

Cause: Wrong or inactive webhook URL in Form Trigger nodes.

Fix: Make sure webhook path and URL match, and the n8n workflow is active.

Schema fetch fails or is empty

Cause: Bad or missing API Key for Airtable or Baserow.

Fix: Check keys carefully and test using API tools before trying in n8n.

File uploads don’t work or attachments are missing

Cause: Binary file data not mapped properly or incorrect HTTP Request settings.

Fix: Confirm Code nodes extract file data correctly and HTTP Requests use multipart form-data.

Before going live checklist

• Try submitting the form with and without file uploads to confirm workflow behavior.


• Verify Airtable and Baserow API Keys have needed permissions.


• Confirm that all form fields show correctly and required fields enforce input.


• Check records in databases created from test submissions, including attached files.


• Back up any existing Airtable or Baserow data before final deployment.

Summary of results

✓ Forms build automatically from Airtable or Baserow schemas inside n8n.

✓ Form submissions insert accurate rows including files in databases fast.

✓ Manual form design and file handling are no longer needed.

→ Saves hours per week and reduces errors in data entry.

→ Enables easy data collection across team projects using common database tools.