Product Integrations Pricing Blog About Sign in Request access

How i10X Works

An agent that executes, not merely triggers

i10X goes beyond webhooks and rule-based automations. It retains the complete process context, works across every system, and manages handoffs now handled by your ops team.

Request access

Point-to-Point vs. Process Execution

What sets a process-carrying agent apart from a webhook chain

Webhooks fire without follow-up. Rules handle isolated steps without memory. i10X retains state throughout.

Without i10X
CRM deal closed
↓
Ops copies into ERP
↓
Finance gets email alert
↓
Fulfillment updated in 24-48h
~3 hours of coordination time per deal
With i10X
i10X Process Agent
01 Detects CRM deal closure
02 Checks required fields against ERP
03 Creates mapped ERP record
04 Alerts finance and fulfillment via chosen channels
Completed in under 90 seconds

Process Context Retention

Agent retains state across every system

Once i10X completes step 1 in Salesforce, its result reaches step 3 in Xero and step 4 in Slack. The agent carries context forward, so no one must pass it between systems.

Unlike point-to-point integrations, process execution keeps the full workflow context with the agent rather than a human coordinator.

Process Discovery
● Scanning Salesforce activity log
● Cross-referencing NetSuite entries (48h window)
● Identifying 3 consistent handoff patterns
● Model ready for review
Detected: CRM closed-won → ERP order create
↓
Detected: Invoicing trigger after ERP create
↓
Detected: Slack notification to #finance channel

Bidirectional Actions

Beyond reading: it creates records, updates fields, and sends messages.

At each step, i10X creates the ERP sales order, updates the CRM opportunity stage, and sends the Slack notification to the right channel. It logs timestamp, triggering condition, and exact field values for every action.

The audit log lets you inspect any run, reverse an individual step, and schedule exports to your SIEM or data warehouse.

Run Log: Order #ORD-2847
14:03 Trigger: SF Opportunity stage = Closed Won
14:03 Validated 6 required fields
14:03 Created NS Sales Order SO-11204
14:04 Notified #finance, #fulfillment

Human-in-the-Loop Routing

For a judgment call, the agent pauses and asks the person responsible

i10X handles suitable steps unattended. If a condition needs a real decision, it pauses, presents the precise question with full process context, and sends it to the authorized decision-maker. Processing resumes exactly where it paused.

Order #ORD-2901
Paused at step 3 of 5
Decision Required Billing address differs from shipping address
CRM shows billing: 12 Raffles Place. ERP shipping address: 80 Anson Road. Discrepancy exceeds the 40% confidence threshold for automatic resolution. Finance team lead has been notified. Awaiting confirmation to proceed.

Access and Audit

Designed around enterprise access controls

Process access by role

You set each agent's permission boundary. It reads and writes only the systems and fields you authorize. Credentials are stored and scoped for each integration.

Run audit trail

The log records every action: timestamp, triggering condition, system, and field values before and after. Export runs to your SIEM or data warehouse on schedule. Available on Growth and Enterprise plans.

Rollback by step

Reverse any agent action from the run log without undoing the workflow. This helps when a step causes an unexpected downstream result.

Ready to automate your first process?