The Client
Us, and smaller client workspaces. Sector7 has its own Twenty workspace, isolated from the agency board. Therapy Lounge publish hooks go through n8n to clear CDN cache when a Webflow site ships.
The question on the Built tab is the brief: can a small team run this without a £700 HubSpot seat? Easy to look like a CRM vendor if we only show the product UI. Keep this secondary. The story is the stack we run.
The Brief
Self-host a CRM with no per-user licence. Wire forms, sheets, Slack, and publish events through n8n so the board is not a spreadsheet with a login.
Primary host is crm.pacing.agency. Automation sits on n8n.pacing.agency.
The Approach
Twenty holds people, companies, opportunities, tasks, and the custom objects we add per workspace. Gmail and Google Calendar sync into the timeline. Sign-in is Google OAuth. REST and GraphQL mean n8n can write a record without someone copying a row.
n8n is the glue. A typical capture is one webhook per site, a switch on the form name, a row in a sheet, and a mail out. PAC lead ingest writes to Twenty with a workspace-scoped credential, not a shared master key.
1. Form / publish
Webflow webhook
2. Route
n8n switch on form
3. Write
Twenty or sheet
4. Tell the team
Slack or mail
Technical Implementation
Twenty is open source, GPL, hosted on Hetzner. The stack note puts hosting at €12.49 a month and no per-user seat. n8n is on a separate Hetzner box (CCX13, Falkenstein), about £10 a month in the tool note, API at n8n.pacing.agency/api/v1.
| Piece | Host | Job |
|---|---|---|
| Twenty CRM | crm.pacing.agency | Board, objects, Gmail, Calendar |
| n8n | n8n.pacing.agency | Webhooks, sheets, Slack, cache |
| Webflow | Client and agency sites | Forms and publish source |
| Slack | Agency workspace | Landed or failed pings |
| Sector7 | Own Twenty workspace | Isolated from the agency board |
| TTL publish | n8n workflow | Clear CDN cache after ship |
- No HubSpot seat: We are not quoting a made-up saving. The sheet question is the claim: a small team can run this without a £700 seat. For us, yes.
- Client isolation: Sector7 does not sit on the agency board. That is the point of workspaces.
- Objects first: n8n only helps if the objects in Twenty are right. A CRM without a journey is still a spreadsheet with a login.
Results & Impact
- The board we use day to day is Twenty, not a rented HubSpot portal.
- Forms and publish events land without a person copying rows.
- A client can have a workspace without sitting in our pipeline.
This page does not sell Twenty seats. Show only the UI and it looks like a vendor site. The useful bit is the two hosts and the workflows between them.
Why It Worked
We needed ops proof, not a CRM brochure. Hosting both sides ourselves is what makes the £700 question answerable.
- Two hosts, one story: CRM and automation are split on purpose. The board stays readable. The workflows stay in n8n.
- Workspace-scoped keys: PAC ingest does not use a shared master credential. That is how client data stays in the right workspace.
- Secondary on /built: Useful as proof we run the stack. Not the offer we lead with.
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Suspendisse varius enim in eros elementum tristique. Duis cursus, mi quis viverra ornare, eros dolor interdum nulla, ut commodo diam libero vitae erat. Aenean faucibus nibh et justo cursus id rutrum lorem imperdiet. Nunc ut sem vitae risus tristique posuere.
