…
Last Snapshot
No widgets added
Use Add Widget to build your operational workspace.
Loading edit options...
Payload Preview
Insert a field placeholder
Add the business baseline and action guidance the AI should use when explaining this widget.
AI-assisted operational assessment using context, thresholds, current value, and snapshot comparison.
Building explanation...
Definition
Filters
Leave this set to No Schedule when this KPI should only run manually.
What This Widget Does
Build a chart or table from materialized or augmented data. You pick an entity, group the data by a field,
and then aggregate values using count, sum, average, min, or max.
Required Inputs
Entity: The data source to analyze.
Group By Field: The category for each slice or bar.
Aggregate: The calculation to perform.
Value Field: Required for sum, average, min, and max.
Chart Types
Bar: Compare totals across categories.
Pie: Show proportions across categories.
Table: List each category and its value.
Percent Of Total
When enabled, a percent column is added to the table and the API returns a percent value for each category.
This is helpful for pie charts and table summaries.
Examples
Accounts by Region: Group By = Region, Aggregate = Count, Chart = Bar.
Open Incidents by Severity: Group By = Severity, Aggregate = Count, Chart = Pie.
Total Revenue by Country: Group By = Country, Aggregate = Sum, Value Field = Revenue, Chart = Bar.
Average Deal Size by Owner: Group By = Owner, Aggregate = Average, Value Field = Amount, Chart = Table.
Tips
Preview before adding to confirm the data looks right.
Use a smaller group-by field first if results are too large.
If values look wrong, verify the value field is numeric and materialized.
Are you sure you want to delete this operational workspace?
⚠ PII
Use this
Total Entities
Field Values Seen
Inserted Values
Updated Values
Unchanged Values
Missing Values
Message
Pipeline
Checkpoint
Sample Rows
Rules Executed
Comparisons
Matches Found
Match Rate
Fuzzy Pass Rate
Edges Created
Matches By Rule
Matches By Match Type
Edges By Type
Components
Largest Component
Avg Component Size
Mapping Errors
Checkpoint
Errors
Guidance
Scheduled Jobs
No scheduled jobs yet.
Set either an interval (repeat every N minutes) or a specific next run time. You can leave one blank.
Resolved Entity
Sources
Details
Sources
Ask a question about entities, relationships, fields, or operational workspaces.
Loading entity...
Resolved Entity
Sources
Details
Sources
Relationship rules match source-backed field values, then create links between the resolved object records.
Relationship Type:
Link Key:
Match Type:
Source Field:
Target Field:
Nothing to review.
Pick the field from one source on the left and the field from another source on the right. Use the same field on both sides for the old same-field matching behavior.
You are about to commit group(s) and entity record(s).
Excluded groups and entities will not be committed.
entity record(s) committed across group(s).
Custom Field: Compares the values from the selected Source Field and Target Field.
Requires: Source Field + Target Field.
Example: `Contact.Email` ↔ `Incident.ContactEmail` using Match Type `exact`.
Primary Key: Compares the Target Field value against the Source Object record_id.
Requires: Target Field. Source Field not required.
Example: Target Field returns `12`, system matches Source record_id `12`.
Email Domain: Extracts the domain from both fields and compares.
Requires: Source Field + Target Field.
Example: `maria@acme.com` ↔ `acme.com` or `https://acme.com`.
Record ID: Compares record_id values across Source and Target objects directly.
Requires: no Source/Target field selection.
Example: Source record_id `1001` ↔ Target record_id `1001`.
Exact: Values must match exactly (case‑insensitive).
Example: `ABC123` ↔ `ABC123`.
Domain: Extracts the domain from each value and compares.
Example: `http://www.gekko.com` ↔ `https://gekko.com`.
If the records are in an array field, use that field path.
Example: { items: [...] } → items
Example: { items: { data: [...] } } → items.data
Example: { result: { records: [...] } } → result.records
If it’s a rowset: { items: [{ rows: [...] }] } → items.0.rows
Primary Key Path should be the field inside each record.
Example array: [{ "id": 1, "name": "Oracle" }] → Primary Key Path: id
Example records path: { items: [ { orgId: 10 } ] } → Primary Key Path: orgId
Rowset example: { items: [{ columnNames: ["id","name"], rows: [[1,"Oracle"]] }] }
Primary Key Path: id (column name)
If duplicate column names exist, select by index in the mapping.
Example: columnNames ["name","name"], rows [["Oracle","Parent"]] → use name[0] (Oracle) or name[1] (Parent)
Use a simple dot-path comparison to tell the ingester when to stop.
Format: path = value
Examples:
items.0.count = 0
hasMore = false
result.recordsCount = 0
You can use variables in the template:
{primaryKeyPath} → replaced with the Primary Key (testing) value.
{offset} → replaced with Offset Start.
{limit} → replaced with Limit.
Examples:
/organizations/{primaryKeyPath}
?offset={offset}&limit={limit}
/queryResults?offset={offset}&limit={limit}
Workspaces you have access to.
Your workspaces
Loading operational workspaces...
No operational workspaces available.
No workspaces match your search/filter.
Start from a template
No templates found.
Industry-specific workspace templates. Browse, preview, and import in one click.
1
Basic Info
2
Classification
3
Review
Industries *
Select all that apply.
Category *
Complexity *
Review your template before publishing it to the library.
Loading templates…
No templates match your filters.
Widgets in this workspace
This template doesn't define any widgets yet.
Ontology
Relationships
Identity resolution
Data Readiness
Coverage
always available
AI Mapping Suggestions
Checking for entities Brain already resolved…
Matching fields…
Field mapping — rename, reassign, or add fields
→
✓
✓
⚠ PII
→
Deploy as a workspace and apply accepted field mapping.
You can still deploy and map the rest later — widgets without matching data will just show empty until then.
AI Provider
Connections
Authentication
Headers
Loading...
API Profile Preview
Detected Profile
Sample Record
:
Detail Preview Response
Loading preview...
Loading endpoints...
Base URL is fixed; add endpoint paths like /accounts or /contacts.
Endpoint Key
Path
Method
Purpose
Action
Uses the saved credentials for this connection. Custom URLs must stay on the same host as the Base URL.
URL
HTTP Status
Reachable
Credentials
Elapsed
Message
Email
GBU
Role