Core Concepts
Adeptia Automate is an integration platform that connects your business systems, transforms data between formats, and automates the movement of information from source to destination. This page introduces the three building blocks every user works with: connections, data mappings, and workflows.
Connections
A connection is a reusable credential and configuration that tells Adeptia Automate how to reach an external system. Before any data can move, you define a connection for each system you want to integrate.
Adeptia Automate supports a broad range of connection types, covering the protocols and platforms most commonly found in enterprise environments:
| Category | What it connects to |
|---|---|
| File transfer | FTP, SFTP, and FTPS servers |
| HTTP | REST APIs and webhook endpoints |
| Database | JDBC-compatible relational databases, including custom drivers |
| Messaging | Apache Kafka clusters, JMS message brokers, and Azure Service Bus queues and topics |
| Web services | SOAP web service endpoints |
| SMTP and IMAP mail servers | |
| OAuth and cloud | OAuth tokens, reusable OAuth profiles, and pre-built connector credentials for cloud services such as Salesforce |
| SAP | SAP system connections |
| Secrets management | Vault-based secrets storage |
Connections carry ownership and project membership information.
Data mappings
A data mapping defines how fields in one schema correspond to fields in another. In Adeptia Automate, a mapping connects one or more source schemas to one or more target schemas, specifying the field-level transformations needed to convert data from the source format into the target format.
Mappings are versioned artifacts that carry ownership, project membership, and configuration details such as character encoding and processing options.
Workflows
A workflow is the unit of integration logic that orchestrates the end-to-end movement of data. It defines where data comes from, what happens to it in transit, and where it goes.
Workflows are owned by a project, versioned, and can be monitored for execution history and status. When you need to understand whether an integration ran successfully, the workflow is where you look.
How the pieces fit together
A typical integration brings together connections, mappings, and workflows:
- Connections provide authenticated access to source and target systems.
- Data mappings translate data between source and target schemas.
- Workflows tie these resources together and run them as a single, managed process.
This architecture keeps each piece independent and reusable. Connections and mappings are shared resources that workflows compose into complete integration solutions.