Skip to main content

Reusable Saved Fields

Saved fields let you create reusable field configurations that can be applied across multiple templates. Instead of re-configuring the same field properties (type, validation, default value, options) every time you create a template, save a field once and reuse it everywhere.

How it works

  1. Configure a field with the desired properties (type, validation, options, default value, etc.).
  2. Save it via the API or the template builder UI.
  3. When creating or editing a template, select the saved field to instantly apply its configuration.
  4. Changes to a saved field do not retroactively update templates that already use it — each template gets a copy at the time of application.

API endpoints

List saved fields

Retrieve all saved fields for your account. GET /api/settings/saved_fields
Response:

Create a saved field

Save a new reusable field configuration. POST /api/settings/saved_fields
Request parameters: Response (201 Created):

Delete a saved field

Remove a saved field from your account. This does not affect templates that already use a copy of this field. DELETE /api/settings/saved_fields/:id
Response: HTTP 204 No Content on success. Error response (404 Not Found):

Using saved fields in templates

Via the template builder

In the template builder, the field palette includes a “Saved Fields” section below the standard field types. Click a saved field to place it on the document. The field inherits all saved properties (type, validation, default value, options, etc.).

Via the API

When creating or updating a template schema, reference a saved field by including its properties. There is no special reference syntax — you copy the configuration into the schema:
Saved fields are copied into the template schema when applied. Updating or deleting a saved field does not change templates that already use it.
Use saved fields to enforce consistent field naming and validation across your organization. For example, save a “Company Name” field with a standard key, placeholder, and validation pattern so every template uses the same configuration.
The key property of a saved field should be unique across your organization’s field library. If two saved fields share the same key and are both applied to the same template, the values object will have key collisions when pre-filling or reading submission data.