Integrations
Send form submissions to Baserow
Create a Baserow table whose columns match your form's field names, create a database token, and paste the token and the table ID into the form's settings in Formward. Every processed submission is then added as a new row.
Baserow Cloud stores its customers' data in Germany, and Baserow can also run on your own server, so this is the spreadsheet route that can stay inside the EU end to end. It needs the Professional plan.
Set it up
- In Baserow, create a table with one column per form field, named exactly as the fields are named in your form (for example name, email, message), plus a column called Submitted at. Text columns are the simplest start, as every value is sent as text.
- In your workspace settings, open Database tokens and create a token with create permission for that table. Copy it; Baserow shows it only once.
- In Formward, open the form, go to its Settings tab and scroll to the Connections panel. Choose Baserow.
- Paste the token into Database API token. Leave Base URL empty for Baserow Cloud, or enter your own instance's https address. Click Connect Baserow. The organization owner does this step.
- Tick Sync submissions to this table, enter the Table ID (the number after /table/ in the table's URL) and click Save sync settings.
- Send a test submission and check that the row appears in Baserow.
The request Formward makes
Rows are added through Baserow's create-row endpoint with user_field_names=true, so the body uses your column names:
http
POST https://api.baserow.io/api/database/rows/table/<TABLE_ID>/?user_field_names=true
Authorization: Token <your database token>
Content-Type: application/json
{
"Submitted at": "2026-10-07T09:30:00.000Z",
"name": "Ada Lovelace",
"email": "ada@example.com",
"message": "Do you ship to Norway?"
}The token is stored encrypted. For a self-hosted Base URL, Formward accepts only public https addresses and does not follow redirects, the same guard its webhooks use.
Plan and limits
- Available on the Professional plan and above.
- Each submission gets one attempt with a 10 second timeout. A failure is shown under Deliveries on that submission, labelled Baserow, and is not retried automatically.
- Only processed submissions are synced: never spam, and never a submission held for an unconfirmed notification address.
Where the data goes
Baserow states that all Baserow Cloud customer data is stored in Germany. With a self-hosted instance, the data sits wherever you run it.
Being in the EU makes the transfer question simpler, but it does not settle everything: Baserow becomes another place that holds your submissions, so it belongs in your records of processing, with its own access rules and retention.
Your data-flow page lists every destination each of your forms uses right now.
Troubleshooting
- Connected, but no rows appear
- Connect Baserow saves the token without testing it, so the first real sync is the test. Open the submission in Formward and read the Baserow line under Deliveries: an authentication error means the token is wrong or lacks create permission on that table.
- Rows appear but some cells are empty
- Column names must match field names exactly, including case and spacing. Rename the column in Baserow, or the field in your form, so the two agree.
- "That Baserow URL must be a public https endpoint"
- Self-hosted instances on a private network or plain http cannot be reached from Formward's servers. Expose the instance over https on a public address, or use Baserow Cloud.
- The test works but real submissions never arrive
- Open the submission in your inbox and check its status. Spam is never forwarded, and a submission stays held, and undelivered everywhere, while the form's notification address is unconfirmed. Confirm the address from the email Formward sent to it and new submissions flow through.
Other integrations
Connect Baserow to your first form
Create a form, point your HTML at it and set up Baserow in a few minutes. Submissions are stored and processed in the EU.