xMatix

Computes defaults for a proposed business record without saving it. This is a defaults preview, not a complete save-validation result. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

data_preview

Queries business records with filters, ordering, paging, optional IDs and property selection. Record-level permissions apply. Missing requested IDs are reported separately. The target is the xMatix Data API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

data_query

Evaluates a saved entity view and returns its permitted business records. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

data_query_view

Executes a named xMatix entity server action on a record. Effects depend on the action and can include record changes, messages and outbound calls.

data_run_action

Partially updates a business record through the xMatix Data API. Configured lifecycle automation can update other records or contact external systems. Returns a compact record echo. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

data_update

Describes one entity: its fields (name, label, data type, lookup target, required), related lists (child collections usable as 'relations' in query_data) and actions. Field names are the exact identifiers accepted by the xMatix Data API.

describe_entity

Fetches the full content of a search result by id: 'record:{Entity}:{Guid}' returns the record, 'entity:{Name}' its definition, 'doc:{name}' a platform guide, 'kb:{id}' a knowledge passage. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

fetch

Fetches one record by id, optionally with child relations (comma-separated related-list names). Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

get_record

Creates an integration app and initial access assignments for its administrators. The app contains connections, bindings, flows and triggers. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_app_create

Reads one integration app and its configuration. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_app_get

Lists integration apps with aggregate activity and run information. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_app_list

Updates an integration app, including its name, activity and execution settings. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_app_update

Lists an integration app’s entity binding definitions. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_binding_list

Creates or updates an entity binding, including direction, write mode and approval settings. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_binding_save

Lists stored connection definitions for an integration app without executing their connectors. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_connection_list

Creates or updates a connector connection and its configuration in an integration app. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_connection_save

Probes a configured connector destination using its credentials. Registered probes read remote status or sample data and may refresh authentication; they do not write business records. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_connection_test

Lists registered integration connectors and their supported capabilities. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_connector_catalog

Lists an integration app’s flow definitions. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_list

Creates or updates a flow definition and its binding. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_save

Replaces a flow’s active version with the selected version, making its definition immutable. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_version_activate

Creates a new draft flow version with an optional step-graph definition through the xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_version_create

Reads a flow version, including its stored step-graph definition. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_version_get

Evaluates pure transforms in a flow version against sample input. Connector and sink steps are skipped; no live integration execution occurs. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_version_preview

Updates a draft flow version after static graph validation. Active versions are immutable. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_version_update

Lists draft and active versions of an integration flow. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_flow_versions

Reads the stored error details of an integration run. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_run_errors

Reads an integration run, including status, attempt information and archived input. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_run_get

Starts another real integration execution using a run’s archived input. Configured connectors and sinks may contact external destinations and create, overwrite or delete data. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_run_replay

Reads the stored, secret-redacted input/output snapshots of an integration run’s steps. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_run_steps

Lists recent integration runs with status and latest error information. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_runs

Lists integration step kinds and their configuration schemas. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_step_kinds

Starts a real integration run from a trigger. Each call creates a new run; configured connectors and sinks may contact external destinations and create, overwrite or delete data. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_trigger_fire

Lists an integration app’s manual, scheduled, entity-event, webhook and poll trigger definitions. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_trigger_list

Creates or updates an integration trigger and its execution configuration. Target: xMatix Integration API. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

integration_trigger_save

Lists recent tenant background jobs with status, type, creation-date and paging filters. Results are ordered newest first. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

jobs_list

Adds a supported component to a stored web layout and saves the modified layout document. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

layout_add_component

Adds a field to a stored web or mobile layout and saves the modified layout document. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

layout_add_field

Summarizes a layout document, including its sections, fields and components. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

layout_describe

Reads a stored layout document and its properties. Optional: pass 'organization' to run just this call in another organization this connection covers — the conversation itself stays where it is.

layout_get