---
title: Legacy Documentation - Old Canvas
description: Access the old canvas documentation
documentId: ipaas-legacy-canvas
locale: en-US
---

## What is an integration flow?

> An integration is the process of connecting different systems, applications, services, or data so they can work together in a coordinated manner.
> These connections enable information exchange and workflow automation.

### Examples

* Automatically transfer orders from an online store to an ERP system.
* Update contacts in a CRM with data from a marketing system.
* Synchronize financial information between accounting and banking systems.

## Steps

An integration consists of several steps that perform different functions:

### Triggers

Triggers initiate an integration by monitoring events in connected systems or applications, activating the workflow when a predefined condition is met. Examples:

* **Scheduler**: allows you to schedule flow execution at specific intervals, such as daily or weekly.
* **REST**: starts the flow upon receiving an HTTP request, allowing external APIs to trigger integrations.

### Connectors

Connectors facilitate communication with external systems, services, or APIs, ensuring data is exchanged in the appropriate format. Examples:

* **REST API**: allows integration with RESTful services, enabling operations such as GET, POST, PUT, and DELETE on external APIs.
* **Cloud Providers**: connectors for services like AWS S3, enabling storage and file retrieval operations in the cloud.
* **Databases**: connectors that allow reading and writing data in databases such as MySQL, PostgreSQL, and SQL Server.

### Logic Tools

Logic tools enable you to implement rules and conditions within the workflow, controlling how data is processed and actions are executed. Examples:

* **Choice**: defines different paths in the flow based on specific conditions, allowing conditional decisions.
* **For Each**: allows iteration over a collection of items, executing actions repeatedly for each item in the list.
* **JSON Transformation**: transforms JSON data from one format to another, facilitating data adaptation to target system needs.

**How do these steps interact?**

Steps are chained sequentially or in parallel, depending on the integration objective. For example, a flow can start with a trigger that identifies new records in an API, go through a connector to fetch additional information from a database, and then use logic tools to format the data before sending it to a target system.

Consult the documentation pages about the old Canvas:

- [Quick Guide - Creating an Integration](/docs/integrations/ipaas-legacy-create-flow)
- [Connector Manager](/docs/integrations/ipaas-legacy-connector-manager)
- [Flow](/docs/integrations/ipaas-legacy-flow)
- [Environment Variables](/docs/integrations/ipaas-legacy-variables)
- [Triggers](/docs/integrations/ipaas-legacy-triggers)
- [General Tools](/docs/integrations/ipaas-legacy-general-tools)
- [Advanced Settings](/docs/integrations/ipaas-legacy-advanced-settings)
- [Test Mode](/docs/integrations/ipaas-legacy-test-mode)
- [Deploy](/docs/integrations/ipaas-legacy-deploy)
- [Example: Integration with CRM and For Each](/docs/integrations/ipaas-legacy-example)