Squarespace form blocks store submissions inside Squarespace.

Where a form block sends things

A Squarespace form block is a small application: it renders fields, validates them, stores submissions in the site, and emails an address you configure. That is a good deal for a small site and a dead end for a workflow that needs the record elsewhere, because the block’s target is not a setting you can change.

Replacing it with a plain form

<form action="https://freelyform.com/f/FORM_ID" method="POST">
  <label for="sq-email">Email</label>
  <input id="sq-email" name="email" type="email" autocomplete="email" required>

  <label for="sq-message">Message</label>
  <textarea id="sq-message" name="message" rows="4" required></textarea>

  <button type="submit">Send</button>
</form>

The trade, stated plainly

If Squarespace should remain the record, keep the block. If the submission has to trigger something else — a webhook, a rule, a CSV somebody else reads — the code block is the way, and the styling duplication is the price.

Test where it will run

Code behaviour on Squarespace depends on the plan and the template, and the editor preview can differ from the published page. Submit once from the live site, confirm the record, and confirm the success destination. That is a two-minute test that prevents a launch-day surprise.