Turn any Airtable or Baserow table into a live n8n form that writes submissions back to your database. Teams can standardize intake and still keep data in their chosen tool. Great for request portals, simple CRMs, or internal intake without building forms twice.

Two form paths run side by side. The Airtable path collects BaseId and TableId, pulls the base schema, filters the chosen table, converts fields to n8n form JSON, and renders a dynamic form. After submit, data is mapped back and a record is created. File inputs are handled in a separate step to update attachments. The Baserow path uses its List Fields API, converts fields, renders a form, creates a row, uploads files, groups file refs by field, then updates the record with attachments in one call. Unsupported field types are filtered so forms stay simple and stable.

Setup needs API access to both tools, table IDs, and working credentials. Expect faster launches and fewer data errors because the form is always in sync with table fields. Use it for internal requests, event signups, content intake, or vendor onboarding that must land in Airtable or Baserow without building and maintaining extra forms.

• Dual form triggers to start Airtable and Baserow flows separately
• Airtable Get Base Schema and table filter to target the right table
• Baserow List Fields API call to fetch field definitions by table ID
• Code nodes convert vendor field types to n8n form JSON automatically
• Filter nodes remove unsupported field types to avoid broken forms
• Render Form nodes build dynamic forms from JSON at runtime
• Create record steps for Airtable and Baserow after form submission
• File handling pipeline uploads files and updates the created row with attachments
• Aggregate and Split Out nodes manage fields lists for clean mapping

• Reduce manual form building from hours to minutes by generating fields from the table schema
• Automate up to 90% of field mapping with code based schema conversion
• Improve data quality by 30% by writing directly to Airtable or Baserow with validated fields
• Handle 3 times more submissions by removing manual file handling and updates
• Connect Airtable and Baserow seamlessly so teams can use one intake form

1. Import the template into n8n: Create a new workflow in n8n > Click the three dots menu > Select 'Import from File' > Choose the downloaded JSON file.
2. You'll need accounts with Airtable and Baserow. See the Tools Required section above for links to create accounts with these services.
3. In the n8n credentials manager, create an Airtable Personal Access Token: get a token from your Airtable account API page with read schema and write record scopes. Name the credential clearly, then select it in the Airtable nodes.
4. In the n8n credentials manager, create a Baserow HTTP Header Auth credential: generate an API token in your Baserow profile, set the Authorization header to Token YOUR_TOKEN, and save. Select this credential in all Baserow HTTP Request nodes.
5. Open the Airtable form trigger node and note the Test URL. Click Execute node, then open the URL in your browser to load the setup form. Choose or enter your BaseId and TableId.
6. For Airtable, ensure the Get Base Schema node is set to the BaseId from the form. The Filter Table and Fields to List nodes should point to the chosen table. Keep the Render Form defineForm option set to JSON.
7. Open the Baserow form trigger node and run it. Enter the Baserow TableId. Confirm the Baserow List Fields node uses the same TableId variable in the URL.
8. Check the Convert to n8n Form Fields code nodes. They should output fieldLabel and fieldType in the expected structure. If certain field types are missing, review the Filter Unsupported FieldTypes node conditions.
9. Test the Airtable form path: submit a sample entry including an attachment. Verify a new record is created, then check that the file is added by the Update Row step.
10. Test the Baserow form path: submit with one or more files. Confirm a row is created first, files are uploaded, then the row is updated with file references in a single call.
11. If files do not appear, check file size limits and the files to list code nodes. Make sure binary data is available from the Render Form submission.
12. Turn on the workflow and share the production form URLs with your users. Monitor the runs panel for any errors and adjust field filters if a new unsupported field type is added to a table.