Squarespace Form Submissions
FluidGrids has no Squarespace Forms node, and no "New Form Submission" trigger for Squarespace. This page explains why and shows the two ways to get Squarespace form submissions into a workflow today.
Why there is no node
Squarespace does not offer a way for an outside service to receive form submissions:
- None of the Squarespace developer APIs (Analytics, Contacts, Discounts, Inventory, Orders, Products, Profiles, Transactions, Webhook Subscriptions, Websites) returns form submissions or their field values.
- Squarespace webhooks cover commerce and extension events only. There is no form-submission event.
- A form block's Storage options are the Contacts panel, Squarespace mailing lists, email, Google Drive, Mailchimp and Zapier. There is no option to send submissions to a custom URL, so there is nothing a FluidGrids trigger could register with.
The Zapier option is a private partner integration between Squarespace and Zapier, not a public API. If Squarespace opens form storage to other services, FluidGrids will add a native trigger.
Option 1: use a FluidGrids Form Trigger (recommended)
Build the form in FluidGrids instead of in a Squarespace form block. Every submission starts the workflow straight away, with all of its fields.
-
Create a workflow with a Form Trigger. Set the Form Title (
formTitle) and add the Fields (fields) you need, for example:[{ "name": "name", "label": "Name", "type": "text", "required": true },{ "name": "email", "label": "Email", "type": "email", "required": true },{ "name": "message", "label": "Message", "type": "textarea" }] -
Under Respond With (
respondWith), choose Redirect and set Redirect URL (redirectUrl) to a thank-you page on your Squarespace site, so visitors return to your site after they submit. -
Save and activate the workflow. The form's public URL appears on the Form Trigger node. It only accepts submissions while the workflow has an Active version.
-
Put the form on your site in one of two ways:
-
Link to it. Add a button or link on a Squarespace page that opens the form URL. This works on every Squarespace plan.
-
Post to it from your own HTML form. On a plan that allows Code Blocks, add a Code Block with an HTML form whose
actionis the form URL and whose inputnames match the field names in the trigger:<form method="POST" action="https://graphqlworkspaces.burdenoff.com/api/forms/YOUR_FORM_ID"><input name="name" required placeholder="Name" /><input name="email" type="email" required placeholder="Email" /><textarea name="message" placeholder="Message"></textarea><button type="submit">Send</button></form>Copy the real URL from the Form Trigger node rather than typing it. FluidGrids checks required fields again on its side, so a visitor cannot skip them by editing the page.
-
The run receives the submitted values in formData, plus submittedAt, submitterIp, userAgent and referrer.
Things to know:
- The form is public: anyone with the URL can submit it. Do not use Password Protected or Basic Auth with your own HTML form, because a password written into a page is visible to every visitor. Use Max Submissions (
maxSubmissions) or Expires At (expiresAt) on the trigger if you need to limit a form. - File uploads and multi-page forms are not supported by the Form Trigger.
- Submissions count toward your plan's monthly runs. See Plans and Quotas.
Option 2: keep the Squarespace form and use Google Sheets
Use this when the form must stay a Squarespace form block.
- In Squarespace, open the form block, go to Storage and connect Google Drive. Squarespace then adds each submission as a new row in a spreadsheet in your Google Drive.
- In FluidGrids, add a Google Sheets connection (see Credentials) for the same Google account.
- Create a workflow whose trigger is the Google Sheets node's new-row operation (
onRowAdded), pointed at that spreadsheet (spreadsheetId) and its sheet (sheetName). - Map the row's columns to the fields you need in later nodes. The columns follow the order of the fields in the Squarespace form.
This is a polling trigger, so runs start on the trigger's poll interval rather than the moment the form is sent. If you rename, reorder or add form fields in Squarespace, the spreadsheet's columns change too; check the column mapping in your workflow afterwards.
What does not work
- Squarespace Contacts. A submitter with an email address is added to the Contacts panel, but Squarespace stores only the name, email and marketing consent there, not the form's fields. A future Squarespace node may offer a "New Contact" trigger; it will not be a substitute for form submissions.
- Email storage. Squarespace can email each submission, and FluidGrids' Email Trigger (IMAP) can read a mailbox, but the email layout is not a stable format to parse. Prefer one of the two options above.
Next steps
- Workflows — all trigger types, including the Form Trigger
- Credentials
- Troubleshooting