Route Params

Extracts URL parameters from a surface's URL pattern and makes them available as pipeline output. This is the primary way to access dynamic URL segments in a page surface's data source pipeline.

Configuration

Setting	Description
URL Pattern	The URL pattern with {parameter} placeholders (auto-populated from the surface's URL pattern)

Input

None (source node).

Output

Returns an associative array where each key is a parameter name from the URL pattern and each value is the corresponding segment from the current URL.

For a pattern /products/{category_slug}/{product_slug} matched against /products/electronics/laptop:

{
  "category_slug": "electronics",
  "product_slug": "laptop"
}

Example Patterns

URL Pattern	Current URL	Output
/products/{category_slug}	/products/electronics	{ "category_slug": "electronics" }
/products/{category_slug}/{product_slug}	/products/electronics/laptop	{ "category_slug": "electronics", "product_slug": "laptop" }
/users/{user_id}/profile	/users/42/profile	{ "user_id": "42" }
/blog/{year}/{month}	/blog/2026/03	{ "year": "2026", "month": "03" }

Typical Usage

Route Params is typically the first node in a page surface's pipeline, feeding parameters into downstream query or lookup nodes:

Route Params → Lookup (products, where slug = row.product_slug) → Output

Or with a query:

Route Params → Query Table (products, where category_slug = row.category_slug) → Sort (name, asc) → Output

The extracted parameters are available as row.parameter_name in downstream node expressions.

TIP

Route Params is designed for use in page surface pipelines. If you need to access shortcode parameters or parent context in a regular component pipeline, use the Get Context node instead.