Form submissions can flow straight into a client's Google Sheet

Form submissions can land in a Google Sheet

Every form has a new card on its Publish tab, under Share. Connect a spreadsheet there and each submission appends as a row: when it arrived, the submission id, then a column per question.

Connecting either makes a fresh spreadsheet named after the form, or points at one you already keep. The picker lists your ten most recently modified sheets and the tabs inside them. The header row is written the moment you connect, so a wrong account or a wrong sheet fails while you are looking at it, not on the next visitor's submission.

Forms that already have submissions can be backfilled. Turn it on at connect time and the old rows arrive oldest first, with progress on the card. New submissions keep landing while that runs.

The sheet is the client's, and it behaves like it. Reorder the columns, rename a header, add a Called back? column of your own, and answers still land where they belong. Add a question to a live form and a column appears at the end. Rows already in the sheet keep their values.

Answers go in exactly as they were typed, so dates and numbers arrive as text. A file-upload question writes the file's name.

Nothing that happens to the sheet can cost you a submission. It is stored first and written to the sheet afterwards. If a write fails, the sync card shows the error, and the next successful write clears it.

Configuring sync is a manager-and-above action, because pointing a form at an outside spreadsheet sends client data out of SharpOS. Editors see the card and can't change it. Viewers never see it.

Connect Google Sheets once for the whole organization

Google Sheets now sits on the Organization → Integrations page next to Google Calendar, Resend, Facebook, Meta Ads, WhatsApp and ElevenLabs. A manager connects the client's Google account once. Form sync and the workflow steps both run against that connection.

Disconnect it and every form sync in the organization stops at the same moment. Reconnecting does not turn them back on. A manager re-enables sync one form at a time, so a reconnect can't quietly resume appending to a spreadsheet nobody remembers choosing.

Spreadsheet steps in the workflow builder

Once Sheets is connected, four steps show up: Add sheet row, Find sheet row, Read sheet range and Create spreadsheet. Cards, customers, audits and webhooks can write to a spreadsheet now, not just forms.

The spreadsheet field accepts a pasted Sheets link or a bare id. It also accepts a reference, so the target sheet can come from whatever started the workflow. Find row and Read range pass what they find to later steps, which is enough to look something up in a client's sheet and branch on it.

Publish an image straight off a card

An image property on a card, page or customer can go into the media field of the Instagram or Facebook publish step. That field used to accept only a Media Center asset picked by hand. Both work now. The same reference goes back into an image property through Update property, so a workflow can carry a picture from one record to another and then post it.