Pipeline Router

Route events to different downstream pipelines based on configurable matching rules, enabling conditional fan-out and event filtering.

⚠️

This integration is currently in beta. Configuration and behaviour may change.

Configuration

Field	Type	Required	Description
`rules_json`	string	Yes	JSON array of routing rules. Each rule has a ‘match’ expression and a ‘pipeline_id’ to route matching events to.
`default_pipeline_id`	string	No	The pipeline ID to route events to when no rules match. If not set, unmatched events are dropped.
`match_field`	string	No	The event field path to evaluate against routing rules. Defaults to the full event object.

Quick Setup

Navigate to Integrations in the sidebar.
Open the Integration Library tab.
Find Pipeline Router or filter by Other.
Click Install, select a variant if available, and fill in the required fields.
Click Install Integration to create the integration with a ready-to-use default configuration.

API Setup

curl -X POST http://localhost:8084/v1/admin/integration-catalog/pipeline_router/install \
  -H "Authorization: Bearer YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Pipeline Router",
    "variant": "default",
    "config": {
      "rules_json": "[{\"match\": \"event_type == 'purchase'\", \"pipeline_id\": \"pipe-123\"}]"
    },
    "delivery_mode": "server_side"
  }'

Delivery

Events are delivered server-side from your Datafly Signal infrastructure directly to the Pipeline Router API. No client-side scripts are loaded for this integration.

Visit Pipeline Router documentation for full API documentation and credential setup instructions.

Google AJSID Segments Wallaroo