Task –– A single record being processed through an integration. For example, one order, one product, or one customer. Every piece of data that flows through Alumio becomes a Task that can be tracked, retried, or inspected.Incoming configuration –– The part of an integration that retrieves data from a source system, such as an API, FTP server, or database to Alumio.Source (Subscriber) –– The component inside an Incoming configuration that connects to a source system and retrieves data from it. The subscriber defines the protocol and method used to fetch data, for example, an HTTP subscriber calls a REST API, a Filesystem subscriber reads files from an FTP server, and a Webhook subscriber listens for incoming data pushed by an external system.Outgoing configuration –– The part of an integration that sends processed data from Alumio to a target system, such as an API, database, or filesystem.Destination (Publisher) –– The component inside an Outgoing configuration that connects to a target system and delivers processed data to it. The publisher defines how data is sent, for example, an HTTP publisher posts data to a REST API, a Database Batch publisher inserts rows into a database, and a Filesystem publisher writes files to an FTP server.Route –– The connection between a source and a target system. A Route defines where data comes from, where it goes, and how it is transformed along the way.Scheduler –– A timer that automatically runs an Incoming configuration or Route at a defined interval, so integrations run in the background without manual triggers.
HTTP (API) connection –– A connection to a REST or HTTP-based external system. Holds the base URL, authentication, and request settings needed for Alumio to communicate with an API.HTTP Authentication –– The credentials and authentication method used by an HTTP connection. Configured separately and linked to an HTTP client. Supported types include Basic, Bearer Token, OAuth 2.0, OAuth 1.0, API key, and more.HTTP Proxy connection –– A synchronous inbound endpoint in Alumio. An external system sends a request to it and receives a real-time response from a connected target system. Used when the caller needs an immediate data response, not just a confirmation.Databaseconnection –– A direct connection to a relational database such as MySQL, PostgreSQL, MSSQL, or Oracle. Used to read rows from or write data to a database as part of an integration.SOAPconnection –– A connection to a SOAP-based web service. Uses a WSDL definition to describe available operations and communicate using XML-formatted messages.Email Servers –– A connection for sending emails from within integrations. Supports SMTP and SendGrid. Used to deliver notifications, status updates, or reports automatically during data processing.Webhook connection –– An inbound endpoint in Alumio that external systems push data to in real time. Data is received and processed asynchronously as Tasks in the background.Filesystem connection –– A connection to a remote or local file environment such as FTP, SFTP, AWS S3, Azure Blob Storage, or Google Cloud Storage. Used to read files from a source or write files to a destination as part of an integration.
Storages –– A built-in key-value data store that persists data between integration runs. Used for delta filtering, pagination tracking, ID mapping, and caching reference data.Entity transformer –– A configuration that modifies, maps, or filters data as it flows through an integration. Used to convert data from one format or structure into another.Space –– An isolated environment within a single Alumio instance, used to separate configurations and data for different customers or projects.Data Engine –– A worker that picks up jobs from the Scheduler Queue and executes them. The number of Data Engines available depends on your Alumio license.Environment variable –– A securely stored value, such as an API key, that can be reused across multiple configurations without exposing the raw value.Alerts –– Automated email notifications triggered when something goes wrong in an integration. Can be configured to fire when a Task reaches a specific status (e.g. Failed) or when no new Tasks are created within a defined time window.
