Connector types reference
Adeptia supports connections to a wide range of external systems and services, giving you a single place to define and manage the credentials and settings your integrations need to communicate with the outside world.
What connector types are
A connector type represents a category of external system that Adeptia knows how to communicate with. When you build an integration, you create a connection of the appropriate type and supply the details specific to that system. Adeptia then uses that connection wherever the integration needs to send or receive data.
Supported connector types
Adeptia supports the following categories of external system:
| Connector type | What it connects to |
|---|---|
| FTP | File transfer servers, supporting FTP, SFTP, and FTPS protocols |
| HTTP | REST API endpoints and webhooks |
| OAuth | OAuth 2.0 tokens for cloud services |
| OAuth profile | Reusable OAuth configurations |
| Connector OAuth | Pre-built credentials for specific cloud applications such as Salesforce |
| Database | JDBC-compatible relational databases |
| Database driver | Custom JDBC drivers for databases not covered by built-in support |
| Kafka | Apache Kafka clusters |
| SAP | SAP systems |
| SOAP | SOAP web service endpoints |
| Vault | HashiCorp Vault for secrets management |
| Managed file transfer | Managed file transfer servers |
| Azure Service Bus | Azure Service Bus queues and topics |
| JMS | JMS message brokers |
| SMTP and IMAP email servers |
What you configure for each type
Each connector type asks for the information relevant to that kind of system. Common details across all types include a display name, an optional description, and the project the connection belongs to. Beyond that, each type has its own specific settings:
| Connector type | Key details you provide |
|---|---|
| FTP | Host, port, protocol (FTP, SFTP, or FTPS), transfer mode, and transfer type |
| HTTP | The URL of the endpoint |
| OAuth / Connector OAuth | OAuth version and token expiry |
| OAuth profile | OAuth version, grant type, scope, and token URL |
| Database | Connection host, driver, schema, authentication type, and connection pooling options |
| Database driver | Driver class and the driver JAR files to load |
| JMS | Server type, broker URL, and connection factory names for queues and topics |
| SOAP | Web service version and message encoding |
| Kafka | Bootstrap server addresses |
| Azure Service Bus | Namespace and shared access key name |
| Server host and port | |
| SAP | Application server host, system number, and client identifier |
| Vault | Vault server URL and authentication method |
| Managed file transfer | Server URL |
Sensitive details such as passwords, tokens, and secrets are handled separately and are not exposed once saved.
How connections fit into your integrations
Ownership and organization
Every connection records who owns it, which project it belongs to, and when it was last modified. You can search for connections by name or description, and filter by connector type, making it straightforward to find the right connection as your library of integrations grows.