What are context operations?
Context operations are named, reusable configurations for reading or writing data in the Context Registry. Instead of ad hoc lookups every time an app, action, or page needs data, you define an operation once and reference it wherever that behavior is needed. Think of them as saved recipes: “list all people in this facility”, “fetch one business by ID”, “ingest screening answers onto a candidate”, “update contact phone numbers”.Screenshot placeholder
Context Operations list (
/o): table of saved operations with name, type, active status, and Create operation button.Operation types
When you create an operation, you choose a type that controls what it does:Query and Fetch are read operations. Ingest, Update, and Upsert change data — configure them carefully and test before connecting to production automations.
Create an operation
- Open Intelligent Registries → Operations (
/o). - Click Create operation.
- Enter a name and optional description your team will recognize.
- Select the operation type.
- Save — you land on the operation detail page to configure filters, entity targets, field mappings, and test queries.
Screenshot placeholder
Create context operation dialog: name, description, operation type selector (Query, Fetch, Ingest, Update, Upsert).
Configure and test
On the operation detail page you refine what the operation touches:- Which entity type it applies to.
- Which context types or fields are involved.
- Filters, limits, and match rules (for reads and upserts).
Screenshot placeholder
Operation detail page with configuration sections and Query config tester showing sample results.
Video placeholder (Screen Studio)
Short clip: create Query operation → configure entity type → run tester → see rows returned.
Active vs. inactive
Operations can be active or inactive. Inactive operations stay saved but are not executed by connected pages or automations — useful when retiring a flow without deleting its configuration history. Toggle status from the operations list or detail page.Where operations are used
Context operations power more than the Operations list itself:
Defining operations centrally keeps behavior consistent — one “list active candidates” query reused everywhere instead of duplicated logic.
Write operations (Ingest, Update, Upsert) append events to the Intelligence Timeline so your organization retains a full history of data changes.
Naming and organization tips
Next: Data views — saved ways to present context query results.