Skip to main content
Connect an existing Baserow table to a Figranium task to append extracted results after each run. Create the destination and its fields in Baserow first, then choose them in the task’s output settings.

​
Overview

After a task finishes extracting data, Figranium can send its JSON result to a configured output destination. For Baserow, each object becomes a row and an array of objects becomes a batch of rows.

​
Supported Providers

Baserow

Append task results to an existing Baserow table through the Baserow REST API.
Additional providers may be added in future releases.

​
Baserow Integration

Baserow is a self-hosted, open-source alternative to Airtable. Figranium can append extracted JSON data to a table that you select from the databases and tables available to your saved token.

​
Prerequisites

  1. A running Baserow instance, either self-hosted or Baserow.io cloud.
  2. A Baserow database token with permission to list accessible databases and tables and create rows in the destination table.
  3. An existing database, table, and fields that match the task’s output.

​
Step 1: Configure credentials

You can add a Baserow credential in Settings > Connections or from the task editor:
1

Open the credential form

In Settings > Connections, go to Database / Output and add a credential. Alternatively, open task Settings > Output and choose + New next to the credential selector.
2

Enter your Baserow details

Select Baserow, then enter a name, the Baserow base URL (for example, https://api.baserow.io), and your API token.
3

Save the credential

Save the credential. Figranium stores it separately from task variables and uses it when sending rows to Baserow.

​
Step 2: Select the output destination

1

Open task output settings

Open the task in the editor and go to Settings > Output.
2

Choose Baserow and a credential

Select Baserow, then select the saved credential that can access your destination.
3

Choose or provision a destination

Select an existing database and table available to the token, or use the provisioning flow to create a dedicated database and table for the Task output. Figranium can create compatible text fields and add missing columns for provisioned destinations.
4

Create matching fields in Baserow

Create a field for each key in your extraction output. The task editor shows known output fields that are missing from the selected table. If you use a JavaScript extraction script and have no sample output yet, run the task once to identify the fields.
5

Choose error behavior and save

Set On Push Error to ignore (default) or fail, then save the task. fail marks the execution as failed if the Baserow push fails.

​
Provisioned destinations

The Baserow provisioning flow creates a dedicated database and table for an individual Task output. It configures typed destination settings, provisions text fields for the output, and adds columns when new output fields require them. Use an existing destination instead when you want to manage the database, table, and field schema yourself. Provisioning and database or table discovery require the saved Baserow token to have the corresponding access. These workspace and provisioning operations are rate-limited.

​
Return data that matches your table

Figranium uses Baserow’s user_field_names=true option. Object keys in your extraction result must match the field names in the selected table exactly, including capitalization. Return a single object to insert one row:
Return an array of objects to insert multiple rows:
Each returned object becomes a row. Nested objects and arrays are serialized as JSON text. The table must already have compatible fields for every key.

​
How data is sent

Figranium authenticates with Authorization: Token <your-token>.

​
Error handling

By default, output push failures are ignored so a temporary Baserow issue does not fail the task. Set On Push Error to fail if the execution should fail when the push fails. Check the execution logs for the output push status.
Figranium validates Baserow URLs and redirect destinations to help prevent requests to private or internal network addresses. See Security best practices for details.