Squarespace form submissions often arrive as emails (like messages from form-submission@squarespace.info)—especially when your marketing agency controls the Squarespace account. The fastest workaround is to forward those submission emails into a Make mailhook, parse the fields, dedupe leads by email, and then create or update a contact + log an activity in JobNimbus.
Photo by Stephen Phillips - Hostreviews.co.uk on Unsplash
If you can get access to the form settings, you can skip the forwarding rule and send submissions directly to Make—but you can still use the same automation pattern either way.
What you’ll build (high level)
Trigger: Squarespace form submission email arrives in Make (via mailhook)
Parse: convert the email body into structured fields (name, email, phone, address, project details)
Dedupe: search JobNimbus by email to find an existing contact
Upsert: create the contact if missing, or update the contact if it exists
Log: create an activity in JobNimbus containing the full submission details
Why email-forwarding is the best “no-access” workaround
If your web agency owns the Squarespace account, you may not be able to add a native integration or change where form submissions go. But you can usually control the inbox that receives the notifications—so you can forward them.
Benefits:
No changes required in Squarespace
Keeps the human-readable notification emails your team is already used to
Lets you automate lead intake immediately (while you wait for access)
Option A (recommended when you don’t have Squarespace access): Forward submission emails to Make
Step 1: Create a Make mailhook address
In Make, create a scenario with an email/mailhook trigger (sometimes called Watch emails / Mailhook depending on your setup). Make will generate a unique inbound email address.
Step 2: Create an Outlook rule (or Gmail filter) to auto-forward submissions
In the inbox that receives the Squarespace notifications:
Condition: From contains form-submission@squarespace.info
Optional extra safety filter: Subject contains "Form Submission"
Action: Auto-forward to the Make mailhook address
This subject filter is a simple “failure-proof” safeguard so random Squarespace emails don’t trigger your lead pipeline.
Step 3: Parse the email into fields you can map
Squarespace submission emails are typically structured as “Label: Value” pairs.
In Make, parse into fields like:
First name / Last name (or full name)
Email
Phone
Address
Project details / Notes
Timeline
Budget range
Important: parsing is easiest when your form field labels stay consistent. If your agency changes labels or adds/removes questions, you may need to adjust parsing.
Step 4: Dedupe leads by email (search before create)
Before you create anything in JobNimbus:
Search JobNimbus contacts by Email
If a match is found, treat it as an update
If no match is found, create a new contact
This is how you avoid duplicates when someone submits twice (or submits again later as a returning customer).
Step 5: Create/update the JobNimbus contact
Map the parsed fields into the matching JobNimbus contact fields.
Common pattern:
Always update: name, email, phone, address
Update when present: budget range, desired timeline, etc.
Step 6: Log an activity (so the context never gets lost)
Even if you store a few fields on the contact, it’s helpful to log a JobNimbus activity that contains the full raw submission.
Include:
Submission timestamp
Full form fields (question → answer)
Source: Squarespace form submission email
Routing metadata: scenario name, inbox, parsing version (optional)
Any errors (if parsing failed)
Option B (cleaner long-term): Ask your web agency for form settings access (or to CC Make directly)
Email forwarding is a strong workaround, but the cleanest setup is either:
Get a limited-access login (or permission) for the Squarespace form settings, so you can set the submission destination yourself, or
Ask the agency to CC the Make mailhook address on form submission notifications.
Confirm JobNimbus dedupe works (submit twice with the same email)
Confirm a JobNimbus activity is created with the full details
Keep the original email notifications enabled during the first week
Troubleshooting
The Make scenario isn’t triggering
Confirm the forwarding rule is enabled
Confirm your mail server allows auto-forwarding to external addresses
Add the subject filter ("Form Submission") if you’re getting noise
Fields are missing or mapped incorrectly
Compare the current Squarespace email format to your parsing logic
Watch for label changes (e.g., “Phone” vs “Cell phone”)
Get help building this
Building a Squarespace-to-JobNimbus lead intake like this usually breaks at the parsing step — email formats shift when an agency edits the form. If you've hit that wall, book a ZoomFlow session — one of our consultants can debug it with you live and ship the working version in the same call.
Make AI agents let your automation workflows decide which tools to use—no hard-coded branching. Learn structured prompting, guardrails, and multi-agent patterns.
Learn how to automate Full Enrich to Pipedrive contact enrichment using Zapier, Make, or n8n. Get the field map, safeguards, and step-by-step workflow.
Learn how to build a Make scenario that reads Zoho CRM email replies, uses AI to classify intent, and auto-responds to warm leads — without manual triage.
