Skip to main content

​
Overview

Forms let you collect information from people outside your workspace (bug reports, lead capture, intake questionnaires) and turn each submission into a record on an object. You build the form visually, publish it, and share a public link or embed it on your site. Every submission flows through the same pipeline as a record created by hand, so indexing, workflows, and permissions all apply.

​
How it works

Each form is tied to a destination. When you create a form you pick one of two destinations:
  • Records: submissions become records on an object. Choose an existing object or leave it empty to auto-create one.
  • Spreadsheet: submissions land in a standalone spreadsheet; you define the fields in the editor.
The builder is organized into a left rail of pages and endings. Each page holds fields drawn from the destination object’s properties. Add a property to a page and it becomes a question. Optional branching rules route a submitter to a different page or ending based on their answers. Endings are what the submitter sees after the last page: a thank-you message, a redirect, or an embedded meeting booking calendar. Publishing flips the form to Active. Each submission then creates a record the same way a manually created record would (under the form owner’s identity), so any workflows on the object fire automatically.
This page is about public data-collection forms. To defer an email send to a later time, see Email → Scheduling.

​
Using it

1

Create a form

On the Forms screen, click Create Form, name it, and pick a destination (Records or Spreadsheet). For Records, select or auto-create the object.
2

Build pages and fields

In the editor, add pages and drop in object properties as fields. Set fields required as needed, add branching rules, and configure endings. Use Preview to test the flow.
3

Publish and share

Click Publish, then open Share to create a public link (/forms/s/<token>) or copy the embed code. Append ?embed=true when embedding in an iframe.
4

Confirm submissions

Submit through the public link, then check the destination object. A new record appears named after the form.

​
Troubleshooting

When reporting an issue, include the request id shown in the error toast. It links the in-app error to the server logs.

Scheduling

Embed a meeting-booking calendar as a form ending.

Records

Where form submissions are stored.

Objects

Form fields come from an object’s properties.

Communications

All inbound and outbound channels.