Multi-Node Routing: One Form, Many Sheets
Route every submission to the right spreadsheet - by form, by field value, by location, or by team. Per-node column sets, aggregate master sheets, and no middleware.
Key Benefits
Per-Campaign, Per-Team, Per-Location Sheets
Route each submission to the sheet that owns it. The 2026 Gala goes to the gala sheet, the Monthly Sustainers list to the recurring sheet, the Volunteer Corps to the volunteer sheet - all from one form endpoint.
Aggregate Master Sheets
Mirror every routed submission to a master aggregate sheet for board reports, cross-team dashboards, and auditing. Individual teams get their focused view; leadership gets the whole picture.
Rule-Based Routing Logic
Route on form ID, field values, UTM source, logged-in user role, submission IP region, or any combination. Build routing rules visually in the SheetLink admin - no code, no if-else spaghetti.
Per-Node Field Mapping
Different sheets can have different column sets. The sales team's sheet only needs name, email, company. The finance sheet needs payment fields. The master aggregate captures everything.
Safer Than Manual Splitting
Routing happens inside the plugin, so a missed rule just sends the submission to a fallback sheet instead of losing it. No rows disappear, no delivery fails silently.
How It Works
When a form is submitted, SheetLink Forms captures the payload as usual. With Multi-Node Routing enabled, the plugin evaluates your configured rules in order and picks a destination node (or several) for the row. Each node is an independent Google Sheet or tab with its own field mapping, webhook URL, and optional column filter. A row can go to a single node (exclusive routing), multiple nodes (broadcast routing), or to a matched node plus a master aggregate (mirror routing). If no rule matches, the submission lands in a configurable fallback node so nothing is ever dropped. The same <a href="/docs/troubleshooting">retry queue</a> protects every node independently - one slow sheet doesn't block the others.
Real-World Use Cases
Real Estate: Per-Agent Lead Sheets
A brokerage with 20 agents wants each agent to see only their own leads, but the broker needs a master view. Multi-Node Routing sends each submission to the agent's personal sheet based on the selected agent field, and mirrors every lead to a broker-only master sheet.
Nonprofits: Per-Campaign Segmentation
An organization runs three simultaneous campaigns (Gala, Sustainers, Volunteers). Each campaign team wants a focused sheet. Development wants a combined master. Multi-Node Routing splits the donation form by campaign field and mirrors the totals upward.
Schools: Per-Campus Aggregation
A district has 12 campus sites, each running enrollment forms. Each campus office needs their own sheet for fulfillment. The district superintendent needs a master roster. One form, one plugin, two levels of visibility.
Agencies: Per-Client Routing
An agency manages 30 client WordPress sites. Multi-Node Routing on a shared template routes each site's submissions to the client-specific Google Sheet the client owns, with a client-specific column set that matches their CRM. Agency staff keep a master observability sheet across all clients.
Events: Speakers to Program Committee
A conference registration form handles attendees, sponsors, speakers, and media in one form. Multi-Node Routing sends each role to a different sheet: attendees to ops, sponsors to sales, speakers to the program committee, media to PR - each with the columns relevant to that team.
Feature Comparison
| Feature | Without Multi-Node Routing | With Multi-Node Routing | |
|---|---|---|---|
| Destination logic | One sheet per form (or complex Zapier router) | Rule-based routing in the plugin | |
| Per-team visibility | Everyone sees everything, or build filter views manually | Each team gets their own sheet automatically | |
| Master aggregate | Manual pivot or import | Built-in mirror to aggregate sheet | |
| Per-node field mapping | Same columns for all destinations | Different columns per destination | |
| Missed-rule handling | Submission silently lost or misrouted | Fallback sheet catches unmatched rows | |
| Setup complexity | Per-sheet Zapier Zaps or custom code | Visual rule builder, one plugin |
Frequently Asked Questions
How is Multi-Node Routing different from the core plugin's routing?
The core plugin supports simple routing: form A to sheet A, form B to sheet B. Multi-Node Routing adds rule-based routing across many nodes - by field value, UTM source, user role, region, or custom conditions - plus aggregate mirroring, per-node column sets, and fallback handling.
Can one submission go to multiple sheets?
Yes. You can configure exclusive routing (first matching rule wins), broadcast routing (every matching rule fires), or mirror routing (one matched node plus a master aggregate). Each node delivers independently.
What happens if none of my routing rules match?
The submission goes to your configured fallback node. Nothing is ever dropped. The delivery log flags fallback routes so you can refine your rules later.
Do different sheets need identical column structures?
No. Each node has independent field mapping. Some nodes can have 5 columns, others 25. The master aggregate can capture every field while team sheets stay focused.
Can I route based on form field values or only form ID?
Both. Routing rules can match on form ID, field equals/contains/regex, numeric ranges, UTM parameters, logged-in user role, submission IP country, or any combination. Rules are evaluated in order you define.
How does this compare to Zapier's multi-path routing?
Zapier's Paths feature does conditional routing too, but each path consumes tasks separately and charges per destination. Multi-Node Routing runs inside your WordPress install with no per-submission fees and no middleware latency - submissions land in the right sheets in under 3 seconds.
Route every form submission to the right sheet
Per-team, per-campaign, per-location sheets with aggregate master views. No middleware, no per-task fees.