EnrichmentWrite

Create Enrichment

create_enrichment

Create a new enrichment of any of the 16 types — transform (rule, lookup), guard (filter, split, transfer_match, dedupe), watch (alert, monitor, budget, recurring, fees, anomaly, digest) and AI (memory, ai_categorize, ai_merchant). rule, alert and memory take their own config field; every other type passes its block in `config`, validated server-side. The plan tier decides which types are available.

Try asking

Categorize my transactions by merchant automatically.

Parameters

ParameterTypeRequiredDescription
workspaceIdstringrequiredWorkspace ID — get from list_workspaces. Portal workspaces are valid here when you manage them (look for `isInherited: true` in list_workspaces).
namestringrequiredEnrichment name
typeenum: 'rule' | 'lookup' | 'filter' | 'split' | 'transfer_match' | 'dedupe' | 'alert' | 'monitor' | 'budget' | 'recurring' | 'fees' | 'anomaly' | 'digest' | 'memory' | 'ai_categorize' | 'ai_merchant'requiredEnrichment type
dataTypeenumoptionalRecord shape it runs on (default: transactions where supported; ignored for the workspace-scoped watch types)
enabledbooleanoptionalActive status (default true)
feedIdsstring[]optionalFeed IDs to apply to
allFeedsbooleanoptionalApply to all matching feeds
ruleConfigobjectoptionalRule configuration
alertConfigobjectoptionalAlert configuration
memoryConfigobjectoptionalMemory configuration
configobjectoptionalThe type-specific config for every type other than rule/alert/memory (lookup, filter, split, budget, digest, …)

Example call

The tool call an MCP client sends (required arguments shown with placeholder values).

{
"tool": "create_enrichment",
"arguments": {
"workspaceId": "workspaceId_123",
"name": "value",
"type": "value"
}
}

Use this tool in

Related Enrichment tools