Skip to main content
Connections define how Alumio communicates with external systems. Each connection type is tailored to a specific protocol or authentication method and can be reused across multiple integrations. Navigate to Connections in the top navigation to access all connection types.

​
HTTP (API)

An HTTP client defines how Alumio connects to a REST API. It stores the base URI, authentication details, and default headers used when making requests to the target system. HTTP clients are reused across Incoming and Outgoing configurations, meaning credentials and connection settings are managed in one place.

​
HTTP Authentication

HTTP Authentication configurations store authentication credentials separately from the HTTP client. Supported methods include Basic auth, OAuth 2.0, API key, and Bearer token. Decoupling authentication from the HTTP client allows you to reuse the same credentials across multiple connections or swap them without reconfiguring each integration.

​
Webhooks

A Webhook creates a dedicated POST endpoint that an external system can push data to in real time. When data arrives, Alumio processes it through the linked Incoming configuration and creates tasks for further processing. See Webhooks for a full overview.

​
SOAP

A SOAP connection defines how Alumio connects to a SOAP-based web service. It stores the WSDL URL and any authentication required to communicate with the service. Used in Incoming and Outgoing configurations the same way as HTTP clients, but tailored to the SOAP protocol.

​
HTTP Proxies

An HTTP Proxy creates a dedicated API endpoint that an external application can call in real time. Alumio receives the request, optionally transforms it, forwards it to the target system, and returns the response to the caller. See HTTP Proxies for a full overview.

​
Email servers

An Email server connection stores the SMTP configuration needed to send emails from within an integration. Used in Outgoing configurations when the destination system is an email recipient rather than an API or database.

​
Databases

A Database connection stores the credentials and connection details needed to read from or write to an external database directly. Supports common database types. Used in Incoming and Outgoing configurations when the source or destination system is a database rather than an API.