Appearance
AireGlu Release Notes
Version: 1.118.0
Release Date: 1st July 2026
Summary of Changes
✨ New Features
- Email Connector Support for Send Email Tasks — GLU-3094, GLU-3136, GLU-3158, GLU-3171
- Reorganised Email Task Authorisation Settings — GLU-3096
- Agent Token Usage Tracking by Tenant — GLU-2962
🐞 Bug Fixes
- Endpoint Name Validation Now Consistent — GLU-3137
- Prevent Self-Referencing Endpoint Task Loops — GLU-3138
- Route Mapping Create Error — GLU-3165
- Adapter Executor No Longer Fails on Extra Parameters — GLU-3179
- Email Task Attachment Upload Fixed — GLU-3186
Detailed Changes
✨ New Features
Email Connector Support for Send Email Tasks (GLU-3094, GLU-3136, GLU-3158, GLU-3171)
Description
AireGlu now supports linking email tasks directly to an email connection, including Office 365 connections via the Microsoft Graph API. You can configure a named email connection at the task level or set one as the tenant-wide default for all email sending. The tenant settings page has been updated to let you choose between the AireGlu default sender, custom SMTP, or a specific email connection. Connections marked as the tenant default are protected from deletion via both the API and the UI.
What this means for you
You can now send emails through your organisation's Office 365 account or other configured email services, rather than relying solely on SMTP credentials. Set a preferred connection once at the tenant level and all email tasks will use it automatically, or override it per task as needed. If a connection is set as the default, you won't accidentally delete it.
Reorganised Email Task Authorisation Settings (GLU-3096)
Description
The SMTP configuration fields within the email task editor have been moved from the main settings into a dedicated Authorisation tab. The authentication type is now selected from a dropdown, offering options for the tenant default, custom SMTP credentials, or an email connection link.
What this means for you
Email task configuration is now cleaner and easier to navigate. Authentication settings are grouped together in their own tab, making it straightforward to see and change how each email task is authorised to send.
Agent Token Usage Tracking by Tenant (GLU-2962)
Description
AireGlu now records agent token usage metrics per tenant and environment. This data will be used to support usage-based pricing and cost analysis across tenants.
What this means for you
Your organisation's AI agent usage is now tracked at the tenant level, providing the foundation for accurate usage reporting and cost transparency as AireGlu's agent capabilities expand.
🐞 Bug Fixes
Endpoint Name Validation Now Consistent (GLU-3137)
Description
The frontend and backend validation rules for endpoint names were out of sync, meaning a user could configure an endpoint with an invalid name (such as one containing an underscore) and only encounter an error on save — without a clear explanation. Frontend validation now matches the backend rules, so invalid names are flagged immediately when entered.
Prevent Self-Referencing Endpoint Task Loops (GLU-3138)
Description
When using an AireGlu Endpoint task, the dropdown list of endpoints to call no longer includes the endpoint currently being edited. This prevents accidental recursive configurations that could result in infinite loops at runtime.
Route Mapping Create Error (GLU-3165)
Description
Creating a new route mapping was incorrectly returning an error to the user even though the record was saving successfully in the background. This been resolved so that route mappings now save and confirm correctly without requiring a page refresh.
Email Task Attachment Upload Fixed (GLU-3186)
Description
When uploading a file attachment via the email task's Advanced Settings tab, the Base64 value being stored incorrectly included the file metadata prefix (e.g. data:text/plain;base64,) rather than the raw encoded content. This caused the attachment to arrive with corrupted content. The metadata prefix is now stripped so only the correct Base64 data is stored and sent.
Adapter Executor No Longer Fails on Extra Parameters (GLU-3179)
Description
Previously, if the data passed to an adapter executor contained additional fields beyond those defined in the adapter's value schema, the execution would fail with a validation error. Extra parameters are now treated as a warning rather than an error, allowing adapters to run successfully while logging unexpected fields for review.