Component Autodiscovery

Component autodiscovery automatically includes or excludes components in a journey based on their key. When a new component is created that matches a journey's patterns, it is automatically added to the journey.

How to set patterns

You can configure autodiscovery when creating a journey or from the Settings tab of an existing journey.

1. Expand or edit the Component Autodiscovery section.
2. Enter one or more Include patterns to match component keys.
3. Optional. Enter Exclude patterns to exclude specific components, even if they match an include pattern.
4. Click Preview to see which existing components match before saving.

Pattern syntax

Patterns are matched against the component key using Unix-style wildcards. Separate multiple patterns with commas or newlines.

Pattern	Matches
*	All components
prod_*	Keys starting with prod_
*_daily	Keys ending with _daily
pipeline_?	pipeline_A, pipeline_B, etc. (single character)
[pP]*	Keys starting with p or P

How matching works

A component is included in the journey when:

1. Its key matches at least one include pattern, and
2. Its key does not match any exclude pattern.

Exclude patterns always take priority over include patterns.

Automatic component addition

When a new component is created through the events API, all journeys in the same project are checked. If the new component's key matches a journey's patterns, it is automatically added to that journey's DAG as an unconnected node.

Examples

Include all production pipelines, exclude QA:

• Include: prod_*
• Exclude: prod_qa_*

Include multiple prefixes:

• Include: ingest_*, transform_*, load_*

Include everything except test components:

• Include: *
• Exclude: test_*, dev_*