Questions, answered

Click Get started, then use Proto to configure Integration / iPaaS for your business. Start with one organization, one connector profile, a short field mapping and a definition whose source identities you can check at the destination.

The Integration Owner owns the definition, schedule and mapping version presented for validation. The connector profile and its field rules are maintained by the Connector Administrator.

An Independent Reviewer examines the exact source revision and its evidence. The owner can enable an approved revision after that decision is recorded.

Validation records an operation run and numbered steps, fixes the mapping version, marks the definition Validated and opens a pending independent review decision.

Start with the per-scope outcome and source identity. Compare its mapping version and watermarks with the delivery attempt, run step and external receipt.

Use the operation key and provider reference to check the destination response before sending again. Assign a follow-up if the outcome remains unresolved.

Yes. The correction workflow retains the executed revision and writes a successor with compensating output, a verification follow-up and a new review decision.

Review decisions identify the reviewer and source revision. State history records transitions, actors, reasons and operation keys. Evidence documents can support the mapping or outcome.

Your team sets up the source and destination endpoints, credentials and field contract for its own systems. Connector profiles hold the authorized endpoint context used by definitions.