Integrations
Connects to the tools you use
Set up connections through ERP.AI and Proto workflows, with every change logged.
- Integration / iPaaS
- Source system
- Destination system
- Credential service
- Operational evidence
Integration / iPaaS · Available now
Example screen with sample data
Trace each integration revision from mapping review to sync outcome.
Integration / iPaaS manages the records around scheduled data exchange. An integration owner links an organization and connector profile to a definition, records the intended schedule, and fixes the mapping version for the revision under review.
- No per-user fees
- Manual work is free
- Configure it in Proto
OverviewDefinitions Awaiting Validation×
Integration / iPaaS · Integration definitions
New integration definition
Definitions Awaiting Validation
Approval conditions
Integration definitions in view
6Draft
6| Number | Name | Definition | Scheduled date | Revision | Mapping version | |
|---|---|---|---|---|---|---|
| ID-46293 | Customer records to billing | Fulfillment order feed | 27 Oct | 770 | v2.4 | |
| ID-32659 | Inventory levels to storefront | Employee directory endpoint | 30 Oct | 50 | v2.5 | |
| ID-84535 | Orders to fulfillment | Fulfillment order feed | 23 Oct | 270 | v3.0 | |
| ID-98677 | Employees to access directory | Employee directory endpoint | 20 Oct | 80 | v3.1 | |
| ID-87000 | Invoices to finance ledger | Employee directory endpoint | 17 Oct | 880 | v3.2 |
6 of 6 records
Customer records to billingIntegration definitions · ID-46293
DraftDefinitionFulfillment order feed
Scheduled date27 Oct
Revision770
Mapping versionv2.4
Review revisionID-46293 · Customer records to billing
Independent Reviewer approves or returns the validated revision.
Waiting for Independent Reviewer
ApproveReturn
- Tables, ready to use
- 14
- Saved views
- 12
- Roles with set permissions
- 7
- Reports and dashboards
- 8
Features
See every integration revision
Every feature works on the same records. Pick one to see the screen your team works in.
Connector Profiles
Keep each organization's endpoint profile, effective dates and mapping rules together.
- Organization first
- Dated authority
- Mapping context
- Organizations
- Connector profiles
- Source mappings
- Integration definitions
OverviewActive Connector Profiles×
Integration / iPaaS · Connector Profiles
New
Active Connector Profiles
Connector profiles
| Name | Code | Organization | Effective from | Effective to | Active | |
|---|---|---|---|---|---|---|
| Billing production API | BILL-PROD | Willowgate Services | 25 Oct | 27 Oct | ||
| Storefront inventory API | STORE-STOCK | Hollowbrook Retail Group | 11 Oct | 15 Oct | ||
| Fulfillment order feed | FULFILL-ORD | Willowgate Services | 20 Oct | 24 Oct | ||
| Employee directory endpoint | STAFF-DIR | North Quay Fulfillment | 27 Oct | 02 Nov | ||
| Finance ledger connection | LEDGER-FIN | Moss Harbor Distribution | 14 Oct | 22 Oct |
6 of 6 records
Billing production APIConnector profiles · CP-80627
CodeBILL-PROD
OrganizationWillowgate Services
Effective from25 Oct
Effective to27 Oct
Integration Definitions
Own the scheduled revision, selected connector and current synchronization state.
- Draft and validation
- Review and enablement
- Execution and history
- Integration definitions
- Connector profiles
- Organizations
- People
- State history
OverviewValidated Definitions×
Integration / iPaaS · Integration Definitions
New
Validated Definitions
Enabled waits for the integration owner
| Number | Name | Revision | Mapping version | Owner | Status | |
|---|---|---|---|---|---|---|
| ID-98875 | Customer records to billing | 640 | v2.4 | Elif Duarte | Validated | |
| ID-53672 | Inventory levels to storefront | 290 | v2.5 | Soren Malik | Validated | |
| ID-47052 | Orders to fulfillment | 920 | v3.0 | Soren Malik | Validated | |
| ID-96863 | Employees to access directory | 430 | v3.1 | Jin Okafor | Validated | |
| ID-85949 | Invoices to finance ledger | 670 | v3.2 | Amara Chen | Validated |
6 of 6 records
Customer records to billingIntegration definitions · ID-98875
ValidatedRevision640
Mapping versionv2.4
OwnerElif Duarte
Mapping Review
Review source-to-target transforms against the exact definition revision.
- Field pairs
- Version and timing
- Decision evidence
- Source mappings
- Connector profiles
- Integration definitions
- Review decisions
- Evidence documents
OverviewMapping Rules×
Integration / iPaaS · Mapping Review
New
Mapping Rules
Source mappings
| Name | Version | Source field | Target field | Transform rule | Definition | |
|---|---|---|---|---|---|---|
| Customer ID to billing account | v1.0 | customer_id | billing_account_id | Trim spaces from customer ID | Employee directory endpoint | |
| SKU to storefront item | v1.1 | sku | storefront_sku | Convert SKU to uppercase | Support ticket export | |
| Order status to fulfillment stage | v1.2 | order_status | fulfillment_stage | Map shipped to dispatched | Billing production API | |
| Employee ID to directory user | v2.0 | employee_number | directory_user_id | Preserve leading employee zeros | Payments settlement API | |
| Invoice total to ledger amount | v2.1 | invoice_total | ledger_amount | Round invoice total to cents | Payments settlement API |
6 of 6 records
Customer ID to billing accountSource mappings · SM-28279
Versionv1.0
Source fieldcustomer_id
Target fieldbilling_account_id
Transform ruleTrim spaces from customer ID
DefinitionEmployee directory endpoint
Sync Executions
Compare per-scope sync results with attempts, receipts and watermarks.
- Scoped output
- Delivery attempt
- Reconciliation
- Sync executions
- Execution attempts
- Integration definitions
- Operation runs
- Operation steps
- Follow-up actions
OverviewSync Outcome Review×
Integration / iPaaS · Sync Executions
New
Sync Outcome Review
Sync executions
| Parent | Source record id | Scheduled date | Outcome | Synced record count | Error count | |
|---|---|---|---|---|---|---|
| Orders to fulfillment | CUST-2026-8911 | 04 Nov | Pending | 7 | 18 | |
| Invoices to finance ledger | ITEM-2026-4412 | 17 Oct | Accepted | 21 | 9 | |
| Orders to fulfillment | ORDER-2026-7619 | 15 Oct | Pending | 34 | 28 | |
| Customer records to billing | EMP-2026-1284 | 20 Oct | Accepted | 31 | 27 | |
| Payments to reconciliation | INV-2026-3310 | 02 Nov | Pending | 23 | 22 |
6 of 6 records
CUST-2026-8911Sync executions · SE-41869
PendingParentOrders to fulfillment
Scheduled date04 Nov
Synced record count7
Error count18
Mapping versionv2.4
Run Trace
Inspect validation, sync and correction runs through their numbered steps.
- Run identity
- Ordered steps
- External proof
- Operation runs
- Operation steps
- Execution attempts
- Integration definitions
- State history
OverviewRevision History×
Integration / iPaaS · Run Trace
New
Revision History
State history
| Source | Source revision | From status | To status | Occurred at | Actor | |
|---|---|---|---|---|---|---|
| Employees to access directory | 400 | Draft | Awaiting review | 19 Oct | Soren Malik | |
| Inventory levels to storefront | 390 | Awaiting review | Approved | 12 Oct | Tomas Qureshi | |
| Supplier catalog to purchasing | 600 | Approved | Scheduled | 17 Oct | Rafiq Novak | |
| Inventory levels to storefront | 370 | Scheduled | Running | 11 Oct | Priya Solis | |
| Payments to reconciliation | 610 | Running | Completed | 13 Oct | Priya Solis |
6 of 6 records
DraftState history · SH-18827
SourceEmployees to access directory
Source revision400
To statusAwaiting review
Occurred at19 Oct
ActorSoren Malik
Review and Remediation
Record independent revision decisions and close the loop on failed work.
- Independent review
- Evidence
- Assigned resolution
- Review decisions
- Evidence documents
- Follow-up actions
- State history
- Integration definitions
- People
OverviewPending Review Decisions×
Integration / iPaaS · Review and Remediation
New
Pending Review Decisions
Approval conditions
| Source | Source revision | Reviewer | Decision | Evidence reference | |
|---|---|---|---|---|---|
| Support tickets to analytics | 930 | Mila Haddad | Pending | mapping_review_oct2026.pdf | |
| Employees to access directory | 470 | Elif Duarte | Pending | stock_sync_reconcile.csv | |
| Payments to reconciliation | 780 | Jin Okafor | Pending | order_stage_samples.csv | |
| Support tickets to analytics | 300 | Soren Malik | Pending | directory_access_approval.pdf | |
| Payments to reconciliation | 560 | Priya Solis | Pending | invoice_validation_log.csv |
6 of 6 records
mapping_review_oct2026.pdfReview decisions · RD-16732
PendingSourceSupport tickets to analytics
Source revision930
ReviewerMila Haddad
Process
From field contract to reconciled result
Mapping to reconciled sync ships ready to use. One step needs a named approval before the work moves on: Review revision (Independent Reviewer).
Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.
-
Set mapping version
Identify the field rules that belong to this revision.
Customer records to billingID-46293 · Connector AdministratorSet mapping versionBy Connector Administrator -
Validate revision
Record a run trace and fix the mapping version for review.
Customer records to billingID-46293 · Integration OwnerValidate revisionBy Integration Owner -
Review revision
A separate reviewer decides on the exact revision.
Customer records to billingID-46293 · Independent ReviewerReview revisionBy Independent ReviewerApprovalIndependent Reviewer approves or returns the validated revision. -
Enable revision
Make the approved revision ready for its schedule.
Customer records to billingID-46293 · Integration OwnerEnable revisionBy Integration Owner -
Synchronize scope
Record each scoped output, attempt and external receipt.
Customer records to billingID-46293 · Integration OperatorSynchronize scopeBy Integration Operator -
Reconcile outcome
Compare watermarks, counts and destination acknowledgements.
Customer records to billingID-46293 · Integration OperatorReconcile outcomeBy Integration Operator
Inside a record
Connect your source and destination
Open any integration definition to see its execution attempts, the roles that work on it, its process stages and its approvals on one page.
- 1Record details
Definition, Scheduled date, Revision and Mapping version.
- 2Execution attempts
Each line is linked to this integration definition.
- 3Who works on it
Admin, Connector Administrator and Integration Owner, each with their own permissions.
- 4Process stages
Every status change, in order.
- 5Approvals
Review revision, with who decides.
Definitions Awaiting ValidationCustomer records to billing×
Integration / iPaaS · Integration definitions
Log activity
Customer records to billing
Fulfillment order feed · Draft
1
Record details
DefinitionFulfillment order feed
Scheduled date27 Oct
Revision770
Mapping versionv2.4
2
Execution attempts
Customer records to billing
| Source | Operation key | Attempt number |
|---|---|---|
| Orders to fulfillment | sync-customers-2026-10 | 460 |
| Support tickets to analytics | sync-stock-2026-10 | 220 |
| Customer records to billing | sync-orders-2026-10 | 510 |
- Execution attempts
- 6
- Total attempt number
- 3,290
3
Who works on it
- AdminManage Users, Organizations, People, connector profiles
- Connector AdministratorManage connector profiles, source mappings
- Integration OwnerManage integration definitions, evidence documents
5
Approvals
- Review revisionIndependent ReviewerApproved
Approvals
Review the exact mapping before release
OverviewApprovals×
Integration / iPaaS · Overview
Approvals
Signed in as Independent Reviewer
Waiting for you
4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
- ID-46293Customer records to billingDraft3dActions
- ID-32659Inventory levels to storefrontDraft1dActions
- ID-84535Orders to fulfillmentDraft2dActions
- ID-98677Employees to access directoryDraft3dActions
Who approves what
| Decision | Approver | |
|---|---|---|
| Review revisionA separate reviewer decides on the exact revision. | Independent Reviewer | |
| Approve integration definitions | Independent Reviewer |
2 approval rules · set per role in Proto
Roles
A workspace for each role
Everyone opens Integration / iPaaS to the work that is theirs. Pick a role to see what it starts with.
Admin
Sets access and oversees organization, people and connector configuration.
- Manage Users, Organizations, People, connector profiles
- View integration definitions, operation runs, review decisions, state history
Connector Administrator
Maintains approved endpoint profiles and the mapping rules attached to them.
This is the first screen this role sees.
OverviewDefinitions Awaiting Validation×
Definitions Awaiting Validation
Integration definitions · Connector Administrator
| Number | Name | Definition | Scheduled date | Revision | Mapping version | |
|---|---|---|---|---|---|---|
| ID-46293 | Customer records to billing | Fulfillment order feed | 27 Oct | 770 | v2.4 | |
| ID-32659 | Inventory levels to storefront | Employee directory endpoint | 30 Oct | 50 | v2.5 | |
| ID-84535 | Orders to fulfillment | Fulfillment order feed | 23 Oct | 270 | v3.0 | |
| ID-98677 | Employees to access directory | Employee directory endpoint | 20 Oct | 80 | v3.1 | |
| ID-87000 | Invoices to finance ledger | Employee directory endpoint | 17 Oct | 880 | v3.2 |
6 of 6 records
Integration Owner
Owns definition revisions, schedule and the request for independent review.
This is the first screen this role sees.
OverviewDefinitions Awaiting Validation×
Definitions Awaiting Validation
Integration definitions · Integration Owner
| Number | Name | Definition | Scheduled date | Revision | Mapping version | |
|---|---|---|---|---|---|---|
| ID-46293 | Customer records to billing | Fulfillment order feed | 27 Oct | 770 | v2.4 | |
| ID-32659 | Inventory levels to storefront | Employee directory endpoint | 30 Oct | 50 | v2.5 | |
| ID-84535 | Orders to fulfillment | Fulfillment order feed | 23 Oct | 270 | v3.0 | |
| ID-98677 | Employees to access directory | Employee directory endpoint | 20 Oct | 80 | v3.1 | |
| ID-87000 | Invoices to finance ledger | Employee directory endpoint | 17 Oct | 880 | v3.2 |
6 of 6 records
Integration Operator
Runs reviewed synchronization work and investigates its recorded outcome.
This is the first screen this role sees.
OverviewOperation Schedule×
Operation Schedule
Operation runs · Integration Operator
Queued3
sync-customers-2026-10Payments to reconciliation
20
21 Octsync-orders-2026-10Customer records to billing
330
19 Octsync-invoices-2026-10Support tickets to analytics
240
26 OctAdd
Running3
sync-stock-2026-10Customer records to billing
90
24 Octsync-staff-2026-10Orders to fulfillment
170
24 Octsync-payments-2026-10Payments to reconciliation
170
13 OctAdd
Independent Reviewer
Decides on the exact revision and checks evidence before release or correction.
This is the first screen this role sees.
OverviewDefinition Status Board×
Definition Status Board
Integration definitions · Independent Reviewer
Draft2
Customer records to billingPinefield Commerce
550
Support tickets to analyticsMoss Harbor Distribution
770
Add
Validated1
Inventory levels to storefrontMoss Harbor Distribution
150
Add
Enabled1
Orders to fulfillmentPinefield Commerce
730
Add
Running1
Employees to access directoryWillowgate Services
550
Add
Completed1
Invoices to finance ledgerRiver Vale Finance
180
Add
Remediation Owner
Resolves assigned failures and verifies compensating work.
This is the first screen this role sees.
OverviewDelivery Attempts×
Delivery Attempts
Execution attempts · Remediation Owner
Queued2
sync-customers-2026-10Orders to fulfillment
460
25 Octsync-invoices-2026-10Invoices to finance ledger
440
29 OctAdd
Running2
sync-stock-2026-10Support tickets to analytics
220
20 Octsync-payments-2026-10Payments to reconciliation
710
29 OctAdd
Failed1
sync-orders-2026-10Customer records to billing
510
25 OctAdd
Unknown1
sync-staff-2026-10Supplier catalog to purchasing
950
22 OctAdd
Audit Reader
Examines decisions, receipts and revision history across the organization.
This is the first screen this role sees.
OverviewRevision History×
Revision History
State history · Audit Reader
| Source | Source revision | From status | To status | Occurred at | Actor | |
|---|---|---|---|---|---|---|
| Employees to access directory | 400 | Draft | Awaiting review | 19 Oct | Soren Malik | |
| Inventory levels to storefront | 390 | Awaiting review | Approved | 12 Oct | Tomas Qureshi | |
| Supplier catalog to purchasing | 600 | Approved | Scheduled | 17 Oct | Rafiq Novak | |
| Inventory levels to storefront | 370 | Scheduled | Running | 11 Oct | Priya Solis | |
| Payments to reconciliation | 610 | Running | Completed | 13 Oct | Priya Solis |
6 of 6 records
Reports
Explain each sync outcome
Answer questions about sync outcomes, attempts, decisions and revision history.
Overview×
Integration / iPaaS · Overview
Integration / iPaaS dashboard
This quarter
Operation runs in view
6Queued
3Running
3Integration definitions by status
How far records got this quarter
| Stage | Reached | Step | |
|---|---|---|---|
| Draft | 24 | ||
| Validated | 5 | 21% | |
| Enabled | 2 | 40% | |
| Running | 1 | 50% |
Revision by status
Sample totals per stage
- 01Sync outcomes by definition
Which scopes were accepted, rejected or left pending for each pipeline?
- 02Scheduled work and completion
Which definitions reached completion against their scheduled date?
- 03Errors by mapping version
Compare integration definitions mapping version and error count with the related sync observations.
- 04Attempt failures by operation
Which operation keys have failed attempts and recorded reasons?
- 05Watermark movement
Read source and destination watermarks on integration definitions beside the latest sync executions observations.
- 06Pending revision decisions
Which exact revisions are waiting for a named reviewer?
- 07Correction follow-up
Who owns unresolved failures and when are they due?
- 08Revision transition audit
What changed between revisions, and who recorded the transition?
Who it's for
Fit the flow to your operating team
See how Integration / iPaaS fits your kind of team.
Controls
Keep receipts and corrections in view
Each stage of mapping to reconciled sync names the role that acts and the status it records, so a change is never anonymous.
OverviewMapping to reconciled sync×
Integration / iPaaS · Process
Mapping to reconciled sync
Each stage, the role that acts and the status it records
Process stages
11Approval steps
1Roles involved
5Tables touched
10Validate revision
Integration OwnerStatusDraft → Validated
RecordsReview decisions, Operation steps, Operation runs
Enable revision
Integration OwnerStatusValidated → Enabled
RecordsState history
Synchronize scope
Integration OperatorStatusEnabled → Running
RecordsExecution attempts, Operation steps, Sync executions
- StartReview decisionsValidate revisionDraft → Validated
- ApprovalEvidence documentsReview revisionIndependent Reviewer
- StepState historyEnable revisionValidated → Enabled
- StepExecution attemptsSynchronize scopeEnabled → Running
- StepState historyReconcile outcomeRunning → Completed
AI agent
Ask Proto to prepare the next step
Ask Proto to help prepare, inspect and explain integration work.
It can
- Connector Administrator: List the profile and mapping details to check before an endpoint change takes effect.
- Integration Owner: Prepare a revision review from the definition, mapping version and validation trace.
- Independent Reviewer: Compare the pending decision with its source revision and attached evidence.
- Integration Operator: Gather the run, attempt, receipt and per-scope outcome behind an uncertain delivery.
Stays with a person
- The owner and reviewer make the release decision under your team's access policy.
- A destination's actual response must be checked against its receipt and business result.
- Give Proto access only to the records and actions its user is permitted to handle, and have a person confirm a correction before it changes an executed integration.
- Usage and any metered actions follow your account's plan.
Show the pending decision for this integration revision and the mapping version it covers.
Find the failed delivery attempt and its run step for this operation key.
Summarize the evidence needed to close this follow-up after the destination result is checked.
The owner and reviewer make the release decision under your team's access policy.
Data model
Your data, in tables you can change
Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.
Browse all 14 tables14tables
- Connector Profiles4
- Integration Definitions5
- Mapping Review5
- Sync Executions6
- Run Trace5
- Review and Remediation6
Implementation
Roll out one team at a time
Start with one team and one process, then add the rest once the basics are running.
Name the flow
Select a source, destination, organization, owner and operating schedule. Identify the source identities that the team can verify in both systems.
Configure the connection
Enter the connector profile, endpoint authority and field mappings with their version and effective date.
Validate and review
Draft the integration definition, run validation, inspect the numbered trace and have an Independent Reviewer decide on the exact revision.
Run a small scope
Enable the approved revision, synchronize a test scope and compare the receipt, attempt, output and watermarks.
Rehearse a fault
Produce a rejected or uncertain result, assign follow-up and verify how a correction preserves the prior revision.
Pricing
$0per user
The base account and everyday work in the ERP.AI app are free, for every user.
- No per-user or per-seat fees
- Viewing, editing, approving and exporting records in the app is free
- Pay only for machine work: API calls, imports, workflows and AI agents
- Prepaid credits from $5. Purchased credits never expire
Machine work rate card Included per $1 of credit
| Usage | Per $1 |
|---|---|
| Record reads (list, filter, get) | 20,000 |
| Search or aggregate queries | 4,000 |
| Record writes | 4,000 |
| Imported or synced records | 200,000 |
| Workflow runs | 2,000 |
| AI agent runs | 2,000 |
| Scheduled jobs or webhooks | 20,000 |
| File uploads (MB) | 2,000 |
| CSV or PDF exports | 100 |
How do I get started?
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.
Who owns a pipeline revision?
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.
Who approves a revision?
An Independent Reviewer examines the exact source revision and its evidence. The owner can enable an approved revision after that decision is recorded.
What happens during validation?
Validation records an operation run and numbered steps, fixes the mapping version, marks the definition Validated and opens a pending independent review decision.
How do I inspect a sync result?
Start with the per-scope outcome and source identity. Compare its mapping version and watermarks with the delivery attempt, run step and external receipt.
What should I do with an uncertain attempt?
Use the operation key and provider reference to check the destination response before sending again. Assign a follow-up if the outcome remains unresolved.
Can a completed result be corrected?
Yes. The correction workflow retains the executed revision and writes a successor with compensating output, a verification follow-up and a new review decision.
Where is the decision history?
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.
Which systems can I connect?
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.
Set up Integration / iPaaS your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.