n8n + RevvedAgents: power-user automation without leaving your CRM

n8n is great at visual automation. RevvedAgents is great at running AI against your HubSpot portal, with an approval layer. Neither one alone covers "let a RevOps power user build a custom agent without writing code" — but together they do.

Here's how we wired them, and what you can now build.

The pitch

Every RevvedAgents user gets a per-org n8n workspace, cloned from a master template we maintain. When you publish a new n8n workflow as an RevvedAgents "agent," it shows up in your catalog alongside our code agents, uses the same Approval Inbox, the same quota logic, and the same execution logging.

So a RevOps team can:

1. Build a visual workflow in n8n ("when a contact is created in HubSpot with lead_source=Webinar, call an enrichment API, draft a warm email, submit to Approval Inbox").
2. Publish it as an agent.
3. Subscribe it to a specific HubSpot connection.
4. Every run flows through the same approval, billing, and logging as every other agent.

The power user builds the flow. The end user sees a normal agent.

What we had to solve

The tricky part was making n8n feel like a first-class citizen in a multi-tenant SaaS. Three decisions:

1. One master template, per-org clones. We maintain a canonical n8n workflow — the "RevvedAgents base template" — and every new org gets a clone on first install. That keeps the template versioned in one place while giving each org an isolated execution environment.

2. Callbacks, not polling. When an n8n workflow finishes a run, it POSTs back to RevvedAgents with findings + proposed actions. That hits the same Approval path as our code agents, so downstream UX is identical.

3. MCP integration for chat. We also exposed n8n as an MCP server, so the chat interface can trigger n8n workflows directly. The LLM sees n8n workflows as tools, same as it sees search_contacts or create_deal.

What you can build

A few patterns we've seen work well:

• Enrichment chains: webhook → Clearbit → Apollo → HubSpot property update, submitted as a batch for approval.
• Complex lead scoring: read contact + company + deals → pass through a scoring prompt → write back a composite icp_score property.
• Cross-CRM bridges: HubSpot change event → Salesforce record update, with an RevvedAgents-approved audit log.

The bar for "building a custom agent" dropped from "spin up a microservice + deploy to our infra" to "drag boxes in n8n, hit publish."

The tradeoff

n8n agents aren't as deeply integrated as code agents — they can't, for example, share memory with the main agentic loop. But for 80% of what a RevOps power user actually wants to build, that doesn't matter.

If you're a technical RevOps lead who's always wanted to ship custom automations but didn't want to own infrastructure, this is the workflow for you. Install RevvedAgents, provision your n8n workspace from settings, and build.