Introducing the Alumio Route Builder
Now connect, orchestrate, and govern integrations at scale from one visual interface
A Squarespace site collects a great deal that nobody ever follows up, so what reaches Salesforce is the handful of actions that the business genuinely intends to act on and nothing else.
A marketing site gathers newsletter signups, contact forms, event registrations and download requests, and a CRM that receives all of it becomes a list nobody works. Reps stop opening it, conversion reporting turns into a measure of form traffic, and the genuinely interested enquiry sits between two hundred people who wanted a PDF. The filtering has to happen before Salesforce rather than inside it. Connecting Salesforce and Squarespace settles which actions mean something, so the CRM holds people somebody intends to contact. The list then holds people, not submissions.
DATA THAT FLOWS BETWEEN THEM
Form submissions
Event registrations
Contacts
Leads
Campaign sources
Consent records
The Squarespace actions you nominate create Salesforce records and the rest stay on the site, so a rep opens a list of people worth calling rather than a form log.
Each submission reaches Salesforce carrying the page and campaign it came from, so marketing can tell which parts of the Squarespace site produce work rather than traffic.
Repeat submissions are matched to the Salesforce record that already exists, so somebody who downloads three papers is one interested person and not three new leads.
What a visitor agreed to on Squarespace travels with them, so a contact reaches Salesforce with the basis for contacting them attached rather than merely assumed.
Somebody registers for an event on Squarespace and Alumio creates the Salesforce record with the event attached, so the follow-up is aimed at people who turned up rather than everybody who ever completed a form on the site.
A visitor requesting a document is recorded without a Salesforce lead, so the CRM is not filled with people who wanted a document, and the rule deciding this is one setting rather than a habit each team applies differently.
When a returning visitor submits again, Alumio matches them to the existing Salesforce record and adds the new activity, so growing interest shows as a history on one contact instead of three leads three reps are working.
Alumio sits between sales channels and fulfillment systems as a governed integration backbone. Orders are routed, transformed, and validated, while status updates return to every channel.
Authenticate your systems using Alumio's pre-built connectors. Choose from 200+ connector packages in the marketplace, plus unlimited custom integrations.
Define how data fields map between systems in a visual interface. Adjust formats, enrich records, and apply business logic, no custom code required.
Configure flows to run in real time on events, on a schedule, or both. Reduce manual data entry and let Alumio handle movement and transformation between systems.
.svg){kind=icon}
Once your first integration is live, adding your ERP, PIM, WMS, or CRM connects to the same hub. Existing flows keep running. No rebuilding from scratch.
Nobody connects a second website. What a Squarespace site usually needs beside it is whatever runs the events, because a registration is the one action on a marketing site that reliably means something, and the attendance list lives in the event tool rather than on the page. Alumio holds that connection alongside this one, so Salesforce learns who actually came rather than who signed up.
It can, and which submissions qualify is decided before anything is created. Alumio reads Squarespace form submissions as they arrive, applies the rule you set about which become Salesforce records, and matches against what already exists. Actions that do not qualify are still recorded, so nothing is lost, but the CRM only grows with people somebody has agreed to contact.
No, this is configured rather than coded. The CSV of signups somebody downloads and imports each week is what goes, along with the deduplication afterwards. Which Squarespace forms create which Salesforce records, and how a person is matched, are entries in Alumio's interface. Where a lead source has to be derived from the page path, the Code Transformer takes that step.
The actions that imply somebody wants to be contacted, which is usually two or three of the forms on a site rather than all of them. A Squarespace registration or a contact request means something; a newsletter signup or a document download generally does not, and treating them alike is how a Salesforce list becomes something reps stop opening. Deciding that boundary is the whole of this integration.
A signup that created a second lead for somebody already in the system is the failure that degrades the list, because both records look correct. Alumio watches each submission live and records the Squarespace form with the Salesforce record it matched to, so a match it could not make raises an alert with the reason rather than defaulting to a new lead. Retries run where configured, so nothing is quietly duplicated.
Talk to an Alumio integration specialist. We'll map the right architecture for your systems, at the right scale, so your operations stay reliable through every change.
.svg)
