{"id":3430,"date":"2026-02-01T21:48:00","date_gmt":"2026-02-01T21:48:00","guid":{"rendered":"https:\/\/formsbridge.codeccoop.org\/?page_id=3430"},"modified":"2026-02-02T08:19:52","modified_gmt":"2026-02-02T08:19:52","slug":"grist","status":"publish","type":"page","link":"https:\/\/formsbridge.codeccoop.org\/documentation\/grist\/","title":{"rendered":"Grist"},"content":{"rendered":"\n
\n
<\/div>\n<\/div>\n\n\n\n
\n
<\/div>\n\n\n\n

\u2190 Documentation<\/a><\/p>\n\n\n\n

Grist<\/h1>\n\n\n\n

Grist<\/strong> is an open-source, self-hostable alternative to spreadsheets that combines the simplicity of a spreadsheet with the power of a relational database, enabling real-time collaboration, customizable workflows, and automation\u2014ideal for teams and developers.<\/p>\n\n\n\n

The Grist add-on<\/strong> allows you to seamlessly integrate WordPress form submissions directly to your spreadsheet tables, transforming how you manage and analyze form data.<\/p>\n\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n\n

The add-on<\/h2>\n\n\n\n

The Grist REST API<\/a> can be used to integrate your data in Grist with any external system. The API closely follows REST semantics, uses JSON to encode objects, and relies on standard HTTP codes to signal operation outcomes. To talk with this API the add-on implements a custom bridge class based on the generic REST bridge that requires Bearer credentials.<\/p>\n\n\n\n

A Grist bridge<\/strong> will store your form submissions as entries in your Grist spreadsheets. Each field of your forms will be translated to a table column, and every form submission inserted as a new row of the table.<\/p>\n\n\n\n

In addition, the add-on comes with a bridge template to create dynamic forms based on your tables.<\/p>\n\n\n\n

How to use<\/h2>\n\n\n\n

The first step to use the add-on is to activate it in the add-ons table in the general settings tab.<\/p>\n\n\n\n

\"Screenshot\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

Once activated, a new tab will be visible in the settings page. If it’s your first time, it should looks like this:<\/p>\n\n\n\n

\"Grist<\/figure>\n\n\n\n

The template wizard<\/h3>\n\n\n\n

The recommended way to set up a new bridge is to use a template as a starter point. The add-on’s template wizard will set up a new Bearer credential, a backend connection and a form, all of them linked with a new bridge.<\/p>\n\n\n\n

With this setup ready, you can edit the bridge’s form to fit your requirements or manually add new forms and bridge them with the backend \/ credential you’ve configured on the previous step.<\/p>\n\n\n\n

The template wizard will lead you through four steps:<\/p>\n\n\n\n

1. Credential<\/h4>\n\n\n\n
\"Screenshot\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

In this step, Forms Bridge will register a new Bearer credential. To set up this authentication, you have to register a new API key<\/strong> in your Grist account<\/a>.<\/p>\n\n\n\n

\n

This API key can be used to access your account via the API. Don\u2019t share your API key with anyone.<\/p>\n<\/div>\n\n\n\n

\n

If you already have a Bearer credential registered, the template wizard allows you to reuse it. If you want to get multiple Grist bridges, the recommended way to proceed is to register a Bearer credential and reuse it on your bridges.<\/p>\n<\/div>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

2. Backend<\/h4>\n\n\n\n

Grist can be self-hosted or used as a cloud service. Based on your setup, this step will require different configurations.<\/p>\n\n\n\n

Start by defining a unique name to identify the backend connection. After that, you have to configure the base URL<\/strong> of the backend. By default the add-on will propose https:\/\/docs.getgrist.com<\/code>, but you can change the URL in case you’re self hosting Grist.<\/p>\n\n\n\n

The last field, the Team ID<\/strong>, is the identifier of your Grist site. In the cloud service of Grist it is the subdomain of your team site (e.g. example<\/code> in https:\/\/example.getgrist.com<\/code>). In self hosted instances, it can be extracted from the URL path (i.e. example<\/code> in http:\/\/localhost:8484\/o\/example<\/code>).<\/p>\n\n\n\n

\n

If you already have the Grist API registered as a backend, the template wizard allows you to reuse it. If you want to get multiple Grist bridges, the recommended way to proceed is to register the backend once and reuse it on your bridges.<\/p>\n<\/div>\n\n\n\n

\"Screenshot<\/figure>\n\n\n\n

3. Form<\/h4>\n\n\n\n

In this step you have to choose the title of the form the template are going to create. The add-on will create a new form with a dynamic set of fields based on the table you decide to integrate with.<\/p>\n\n\n\n

4. Bridge<\/h4>\n\n\n\n

In the last step of the wizard, you have to set a unique name for the new bridge and select the table<\/strong> you want your form to get bridged.<\/p>\n\n\n\n

\"Screenshot\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

After that, click on submit<\/mark> and Forms Bridge will generate the credential, backend, form and bridge setting. It only remains to publish the new form on a public page and wait for a new form submission!<\/strong><\/p>\n\n\n\n

Manual set up<\/h3>\n\n\n\n

With templates, you can save a lot of time while configuring your bridges, but you can achieve the same result with a manual set up.<\/p>\n\n\n\n

A Grist bridge<\/strong> will require the following components:<\/p>\n\n\n\n

1. Credential<\/h4>\n\n\n\n

As mentioned before, the Grist API works with Bearer tokens to grant access to its resources. To solve this authentication requirement, the add-on requires you to register an API key<\/strong> in your Grist account<\/a>.<\/p>\n\n\n\n

Once you have the token, you have to go to Settings > Forms Bridge > HTTP > Authentication<\/code> and register a new authentication credential. Select Bearer<\/strong> as the authentication schema and put the key value as the Access token<\/strong> field.<\/p>\n\n\n\n

2. Backend<\/h4>\n\n\n\n

To configure the Grist API as a backend, follow this steps:<\/p>\n\n\n\n

    \n
  1. Register a new backend with a unique name (Grist API<\/em>, for example), and a URL with https:\/\/docs.getgrist.com<\/code> as value for cloud services, or the base URL of your self hosted Grist instance.<\/li>\n\n\n\n
  2. Select JSON<\/code> as the Encoding Schema<\/strong><\/li>\n\n\n\n
  3. Select the Bearer credential you’ve configured on the previous step.<\/li>\n<\/ol>\n\n\n\n

    3. Form<\/h4>\n\n\n\n

    The add-on supports any kind of form. Get your preferred form builder and create a new form. Once created, you can choose it as the target form to be bridged on the bridges panel of the add-on.<\/p>\n\n\n\n

    4. Bridge<\/h4>\n\n\n\n

    The add-on\u2019s bridge is an extension of the generic REST bridge. Because of this they looks so similar. Like the REST bridge, the add-on\u2019s bridge requires a unique name, a backend, a form, an endpoint and an HTTP method.<\/p>\n\n\n\n

    The endpoint of a Grist bridge should be like \/api\/docs\/{docId}\/tables\/{tableName}\/records<\/code>. The docId<\/strong> can be extracted from the table URL. For example, the in the URL https:\/\/docs.getgrist.com\/abc123456789\/Example\/p\/1<\/code> the baseId is “abc123456789”. The tableName <\/strong>parameter of the URL is the name of your table.<\/p>\n\n\n\n

    \n

    Despite the different methods available (GET, POST, PUT, DELETE, PATCH), the most common case is to use the POST as the bridge method to write new rows to your spreadsheets. The other available methods are useful for API introspection or to set up workflow automations, but are not designed to be used as the bridge method.<\/p>\n<\/div>\n\n\n\n

    Troubleshooting<\/h2>\n\n\n\n

    To troubleshooting your bridges you can use the plugin’s debug console from the General Settings page. Enable the debug mode and submit a sample form response to see what’s going on under the hood.<\/p>\n\n\n\n

    Common issues<\/h3>\n\n\n\n
      \n
    1. Authentication failures<\/strong>\n