1. Integration / iPaaS
  2. Data model
Reference

The tables behind Integration / iPaaS

Integration / iPaaS ships with 14 tables, grouped here by the feature that uses them. Every record your team works with lives in one of them, and you can add fields and tables in Proto.

Tables
14
Features
6, plus shared settings
Change it
Add fields and tables in Proto

How the model is organised

Configuration

Organizations group People and connector profiles; source mappings belong to a connector profiles record.

Operations

Integration definitions link an organization, owner and connector profile. Sync executions and execution attempts capture delivery observations.

Execution and provenance

Operation runs link to a definition; operation steps give each run its ordered trace.

Review and evidence

Review decisions, evidence documents, follow up actions and state history retain decisions, supporting material and transitions.

Access

Users record account identity and the app's user role value.

Every table, by feature

Connector Profiles

4 tablesAbout this feature
  • Organizations

    Client organizations whose integration endpoints are managed.

  • Connector profiles

    Authorized endpoint and credential profiles used by integration definitions.

    Linked to Organizations
  • Source mappings

    Reviewed field-level transform rules between source and destination systems.

    Linked to Connector profiles
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles

Integration Definitions

5 tablesAbout this feature
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles
  • Connector profiles

    Authorized endpoint and credential profiles used by integration definitions.

    Linked to Organizations
  • Organizations

    Client organizations whose integration endpoints are managed.

  • People

    Owners, operators and reviewers participating in integration operations.

    Linked to Organizations
  • State history

    Immutable status transition history for integration definitions.

    Linked to Integration definitions, People

Mapping Review

5 tablesAbout this feature
  • Source mappings

    Reviewed field-level transform rules between source and destination systems.

    Linked to Connector profiles
  • Connector profiles

    Authorized endpoint and credential profiles used by integration definitions.

    Linked to Organizations
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Integration definitions, People
  • Evidence documents

    Source evidence supporting a mapping or synchronization outcome.

    Linked to Integration definitions, People

Sync Executions

6 tablesAbout this feature
  • Sync executions

    Per-scope synchronization observations produced by pipeline runs.

    Linked to Integration definitions
  • Execution attempts

    Individual delivery attempts for an integration operation key.

    Linked to Integration definitions
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles
  • Operation runs

    Workflow-maintained execution records for validation, synchronization and correction.

    Linked to Integration definitions
  • Operation steps

    Ordered step trace with persisted input and output identities.

    Linked to Operation runs
  • Follow up actions

    Assigned remediation actions for pipelines with unresolved failures.

    Linked to Integration definitions, People

Run Trace

5 tablesAbout this feature
  • Operation runs

    Workflow-maintained execution records for validation, synchronization and correction.

    Linked to Integration definitions
  • Operation steps

    Ordered step trace with persisted input and output identities.

    Linked to Operation runs
  • Execution attempts

    Individual delivery attempts for an integration operation key.

    Linked to Integration definitions
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles
  • State history

    Immutable status transition history for integration definitions.

    Linked to Integration definitions, People

Review and Remediation

6 tablesAbout this feature
  • Review decisions

    Independent reviewer decisions recorded against an exact source revision.

    Linked to Integration definitions, People
  • Evidence documents

    Source evidence supporting a mapping or synchronization outcome.

    Linked to Integration definitions, People
  • Follow up actions

    Assigned remediation actions for pipelines with unresolved failures.

    Linked to Integration definitions, People
  • State history

    Immutable status transition history for integration definitions.

    Linked to Integration definitions, People
  • Integration definitions

    Configured integration pipelines with frozen mapping revisions and watermark state.

    Linked to Organizations, People, Connector profiles
  • People

    Owners, operators and reviewers participating in integration operations.

    Linked to Organizations

Shared and settings

1 table
  • Users

    Users

    Linked to Users

Keys and references

The definition number is the team’s human reference for a pipeline. Revision and mapping version identify the contract examined by a reviewer. The operation key connects a workflow invocation to its attempt and state history. A sync execution’s source record identity identifies the affected scope. Preserve those identifiers when importing historical records or comparing an external receipt.

Migration order

  1. Import Organizations, then People and Users.
  2. Import connector profiles and their source mappings.
  3. Import integration definitions with owner, organization, connector and revision details.
  4. Bring in linked review decisions and evidence documents where their source revision is known.
  5. Import operation runs before operation steps, then execution attempts and sync executions.
  6. Import state history and follow up actions, checking their references and chronology.

Set up Integration / iPaaS your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started