Repository navigation
feat(workflows): an entity filter node - #562
Merged
Merged
Conversation
Keeps a list's entities by type, a stop list of names, length, a pattern or how often they're said, between extraction and saving. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_016j3Y4Dh3DLGwyFYBH23QML
21 of 23 tasks
This was referenced Oct 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Requested by Adeel · project thread
Description
Before: keeping only some of the entities an extract node found meant a generic Filter with a hand-written test per rule.
After: an Entity filter node (a primitive, so every workflow scope has it) keeps a list's entities by the types it keeps or skips, a stop list of names (matched case and spacing aside, as entities are joined), a minimum name length, a name pattern (a regular expression, checked as match trees check theirs: no runaway backtracking, a time limit per name), and how often each is said (its
mentions, else how often the list names it). Anything in the list that isn't an entity is left out. The canvas has its settings panel, card summary and Publish checks.How:
flow.entity_filterbeside the other primitives inflow.py, reusinganalyze.ent_keyandmatch's pattern check and search;workflow-model.tsandnode-settings.tsxfor the canvas.Motivation and Context
One of the three node types in the parked "New workflow node types" ask (HTTP call, template render, entity filter), now started. The HTTP call node follows in its own PR; template render is the existing
templateprimitive.Types of changes
Checklist:
test_entity_filter_keeps_the_entities_asked_for,workflow-flow.test.ts).docs/processing.md(Workflows) updated.Done questions
/api/v1/workflows, the catalog lists the node and its settings).analyze.ent_key,match._pattern_valueandmatch._search.Generated by Claude Code