Source: [Original HTML page](https://stolenorbit.com/en/templates/integration-map/)

Language: English

FREE TEMPLATE · FILL IN, DOWNLOAD, REUSE

# System integration map

Describe each connection as a contract between systems. This worksheet clarifies what may be read or written and what must happen when a request fails.

[By Stolen Orbit](https://stolenorbit.com/en/about/) Revision 2026-09-24

## When to use it and what to produce

[Source for this section](https://stolenorbit.com/en/templates/integration-map/#template-purpose)

When automation transfers data between existing tools and operations, implementation partners and IT need a shared specification.

One connection record containing field mappings, permissions, duplicate handling and a reconciliation check.

Fill in the fields below and download your document. The website does not send or save answers: closing the page may lose them. Examples are illustrative and should be replaced with your process data.

[Download the complete blank template (.md)](https://stolenorbit.com/downloads/integration-map-en.md)

Without JavaScript, download the full template above and complete it in your editor.

## 1\. Define the connection

[Source for this section](https://stolenorbit.com/en/templates/integration-map/#contract)

Separate reads, creates and updates. A system available through a user interface does not necessarily provide the required APIs or permissions.

**See a worked example**

Illustrative example: an approved request creates an ERP order draft. The customer code comes from the ERP master record; a free-text company name is not sufficient identification.

**Source, destination and owners**

Record test and production environments and a technical contact for each system.

**Trigger, frequency and operation**

Describe what triggers the transfer, when it runs and which record is created or changed.

**Fields and authoritative source**

Map identifiers, formats, units and precedence rules when the systems contain different values.

## 2\. Limit the effects

[Source for this section](https://stolenorbit.com/en/templates/integration-map/#controls)

Specify access and expected behaviour before connecting production credentials. Record references to secrets, never passwords or tokens in this worksheet.

**See a worked example**

Illustrative example: use the request identifier as an external reference. If a draft with that reference exists, verify its state before attempting another write.

**Allowed and prohibited operations**

List accessible resources and fields; specify actions that need human approval.

**Identity and duplicate handling**

Define how repeated delivery of the same event is recognised without producing a second operation.

**Limits and dependencies**

Document verified API, size, availability and version limits; label anything still awaiting confirmation.

## 3\. Design recovery

[Source for this section](https://stolenorbit.com/en/templates/integration-map/#recovery)

A missing response does not prove that a write failed. Plan checks before repeating operations that can produce real effects.

**See a worked example**

Illustrative example: after a timeout, search for the draft by external reference. If its state remains uncertain, send the case for review instead of creating another order.

**Errors, retries and expiry**

Separate temporary failures, invalid data and cases needing intervention; set bounded retry rules.

**Source-to-destination check**

Specify which identifiers, counts or amounts are compared and how frequently.

**Recovery and owner**

Explain how to stop the flow, resume from the correct point and inspect effects already produced.

## Pitfalls to avoid

[Source for this section](https://stolenorbit.com/en/templates/integration-map/#template-pitfalls)

-   Promising an integration before verifying actual access and system capabilities.
-   Retrying a write without checking whether it already happened.
-   Monitoring technical errors while missing absent or duplicate records.

[Keep your CRM connected to the work happening around it.](https://stolenorbit.com/en/services/crm-automation-ai-integration/)

[Connect your ERP with a clear account of every record.](https://stolenorbit.com/en/services/erp-integration-automation/)

[AI agent or workflow: start with the decisions the job requires.](https://stolenorbit.com/en/resources/ai-agents-or-workflows/)

[Build or buy AI: compare the complete business process.](https://stolenorbit.com/en/resources/build-or-buy-ai/)

[Reliable automation knows what to do when the outcome is uncertain.](https://stolenorbit.com/en/resources/automation-failures-and-duplicates/)

[All templates and tools](https://stolenorbit.com/en/tools/)

[All guides](https://stolenorbit.com/en/resources/)

## Take the next step together.

Use this document to start a discussion about scope, evaluation and project ownership.

Review the text before sending. Only your email is needed alongside the message; other details are optional.

[Contact us](/en/contact/)

## Turn the question into a next step.

-   [Use what you have, connect it, or build the missing part?](https://stolenorbit.com/en/resources/native-automation-connectors-custom-integrations/)
-   [Automation failures and duplicates](https://stolenorbit.com/en/resources/automation-failures-and-duplicates/)
-   [ERP integration](https://stolenorbit.com/en/services/erp-integration-automation/)