# Connectors: Release notes {% updates format="full" %} {% update date="2026-04-30" %} ## Highlights * **What shipped:** New IFS connectors for Apps10, PSO, Assyst, and Service Request, plus improved MS Teams experiences for Human-in-the-Loop workflows * **Why it matters:** Expands the set of enterprise systems Digital Workers can connect to, enabling more end-to-end automation across ERP, field service, and ITSM workflows * **Who benefits:** Builders and operators deploying Digital Workers in IFS-centric environments (operations, field service, and IT teams) ## New features ### New connectors
IFS Apps10 * **Description:** The IFS Apps 10 Integration enables seamless connectivity between IFS Loops platform and IFS Applications 10 (IFS Apps10) to synchronize and manage ERP and enterprise operations data. * **Key objects / capabilities:** This enables support for Digital Workers in the IFS Apps10 integration. The list of supported Digital Workers for Apps10 can be found here. * **Auth / setup notes:** Uses OAuth 2.0 Resource Owner Password Credentials (ROPC) grant via Keycloak (mirrors the IFS Cloud connector authentication pattern).
IFS PSO * **Description:** The IFS PSO Integration enables seamless connectivity between Loops and IFS PSO to synchronize and manage field service scheduling and workforce management data. * **Key objects / capabilities:** * Field service scheduling and dispatch * Workforce management (assignment, capacity, and availability signals) * **Auth / setup notes:** Uses session-token-based authentication via the IFS PSO Gateway API, with automatic token persistence and renewal to support uninterrupted operations.
IFS Assyst * **Description:** The IFS Assyst Integration enables seamless connectivity between your platform and IFS Assyst (assystREST v2) to synchronize and manage IT service management data, allowing organizations to streamline ITSM operations through a unified connector framework. * **Key objects / capabilities:** * Incident management * Event tracking * Service request workflows via the assystREST API * **Auth / setup notes:** Uses basic authentication with IFS Assyst REST API credentials, runs as an API task–based integration, and requires an active Assyst instance with network connectivity.
IFS Cloud for Helpdesk Capability * **Description:** This release introduces **Help Desk (Service Requests)** support in the **IFS Cloud connector for TheLoops**, enabling service request data and selected APIs to be used for ticketing, automation, and content access. It establishes OAuth-based connectivity and forms the foundation for future digital worker workflows such as intake and triage. * **Key objects / capabilities:** * **Service Requests (Help Desk)** * Indexed from IFS Cloud into Loops as tickets * Supports scheduled bulk indexing and webhook-based single record updates * Uses **ReqId** as the stable identifier * Contact notes are ingested and mapped as ticket comments * **API Objects (APITask)** * Selected IFS Projection APIs can be imported as tools into Loops * **Content Access** * Scheduled indexing of knowledge and content * **Operational Monitoring** * Job execution status, history, and date-range filtering for bulk indexing * **Auth / setup notes:** * Uses **OAuth client credentials** from **IFS Cloud IAM** * Requires **Client ID** and **Client Secret** * Optional **offline\_access** scope supported * No user-based authentication required
IFS Cloud (Content Management) * **Description:** Content Management is a capability of the **IFS Cloud connector** that enables knowledge and content data from IFS Cloud to be indexed into **TheLoops**. It is designed to make operational content available for use cases such as digital workers (for example, the Knowledge Worker) that depend on reliable access to indexed knowledge and content. * **Key objects / capabilities:** This capability supports scheduled indexing of knowledge and content data using a shared indexing framework. It also provides operational monitoring, allowing users to view indexing job execution status and history for verification and troubleshooting. The current release includes scheduled jobs for indexing IFS Cloud knowledge and content. * **Auth / setup notes:** No separate authentication method is defined specifically for Content Management. It operates under the existing **IFS Cloud connector authentication**, with no additional or standalone authentication configuration mentioned for this capability.
MCP * **Description:** MCP Server support in TheLoops enables native integration with customer‑managed MCP Servers, allowing secure discovery and execution of external or internal tools. This capability establishes foundational connectivity for future digital workers that can dynamically discover and run MCP-hosted tools, supporting both standard MCP implementations and those deployed on AWS Bedrock Agent Core. * **Key objects / capabilities:** * Secure discovery and execution of tools hosted on customer‑managed MCP Servers * Support for both external and internal MCP implementations * Flexible authentication using **OAuth 2.0** or **API key–based** access * OAuth integration with identity providers such as **Keycloak, Okta, and Auth0** via OpenID Connect * Compatibility with **AWS Bedrock Agent Core–based** MCP Servers (OAuth only) * Tool import via **Full Ingress job**, with imported tools displayed in the **Tools** tab * Automatic discovery of authorization and token endpoints using standard OAuth/OpenID metadata * Support for multiple deployment models, including HTTPS‑exposed and identity‑protected MCP Servers * **Auth / setup notes:** MCP Server integrations support flexible authentication options. OAuth 2.0 is the recommended approach, using access tokens issued by an identity provider, with optional refresh token support via the offline\_access scope. TheLoops works with common identity providers such as Keycloak, Okta, and Auth0 using standard OpenID Connect flows. For MCP Servers that do not rely on an identity provider, API key authentication is supported by passing a static key via request headers. However, API key authentication is not supported for MCP Servers running on AWS Bedrock Agent Core, which require OAuth-based authentication.
### Improvements
MS Teams **Overview:** The Microsoft Teams Integration enables seamless connection between TheLoops platform and Microsoft Teams , allowing customers to ingest Teams data for collaboration and helpdesk use cases. This release provides a Microsoft Teams Digital Worker homepage, secure authentication with ongoing token lifecycle management, and configurable ingestion options with validation during setup. **Key improvements:** * Microsoft Teams Digital Worker homepage with a dedicated tab per Digital Worker / Teams HITL channel, showing total interactions, interactions awaiting HITL, and direct links to the conversations that need user input * Support for adding the IFS Loops app in Microsoft Teams to connectusers directly to a Digital Worker. * Microsoftco Teams Adaptive Cards support for richer, action-oriented notifications and interactive follow-ups (buttons) **Authentication Setup:** * Optional User Email field added for identification of the authenticated Teams account. * Tenant-wide Teams domain reuse across workspaces \ Support to configure the same Microsoft Teams domain across multiple Loops workspaces. * Support for multiple Teams domains across different workspaces with one Teams connector per workspace per tenant
Outlook **Overview:**\ The Microsoft Outlook integration connects **IFS Loops** with **Microsoft Outlook**, allowing email data and inboxes to be accessed and managed within the Loops platform. The setup includes a guided authorization flow and confirmation to ensure the integration is active and validated. **Key Capabilities:** * Secure connection between IFS Loops and Microsoft Outlook * Ability to authorize an Outlook account with admin consent * Support for adding and managing **shared inboxes** per selected user * Flexible configuration to assign specific shared mailboxes to specific users * Confirmation and validation of successful integration setup * Ability to regenerate authentication tokens when reconnection is required (for example, if a token or password expires) **Authentication Setup:**\ Authentication is handled through an **Outlook authorization flow** initiated during integration setup. When connecting, a Microsoft Outlook authentication window prompts the user to select an Outlook account and approve access; the account must have **admin consent**. Token lifecycle management supports reconnection when needed, allowing administrators to regenerate tokens from the Authentication tab to restore access if credentials expire or become invalid.
Tooling via connectors * **Connector-based standard tools:** Each connector includes a set of ready-to-use standard tools that can be used to build Digital Workers. Faster time to value: These tools reduce setup time and help builderscreate and iterate on Digital Workers more quickly.
### Known issues * Some imports may still require manual validation of connector permissions/scopes after configuration, depending on the target system {% endupdate %} {% endupdates %} --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://kb.theloops.io/releasenotes/release-notes/connectors-release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.