Connectors
Connectors in the Work.AI platform enable Business Processes (BPs) and AI Agents to communicate with external systems. They provide standardized integration points for retrieving and enriching data, sending information to third-party services, triggering workflows based on external events, and orchestrating end-to-end automation across enterprise environments.
Work.AI offers a wide range of connectors—from no-code general-purpose configurations to domain-specific connectors delivered as Asset Bundles. These connectors support multiple integration patterns, including REST and SOAP APIs, message queues, email ingestion, file polling, long-running listeners, and enrichment services.
General-purpose connectors support standard integration needs through configurable protocols including REST, SOAP, FTP, JMS/MQ, Kafka, and others.
Email-specific connectors streamline data ingestion from Microsoft Exchange and Outlook.
Proprietary and enrichment connectors provide dedicated integrations with third-party services for regulated and industry-specific use cases, allowing AI Agents to work directly with authoritative external data sources.
General-purpose connectors
Each connector serves a specific integration role within the platform. Select the connector that best matches your integration requirements, data sources, and AI Agent capabilities:
| Connector | Purpose | Usage |
|---|---|---|
| REST connector | BP exposure to external systems over REST for synchronous or asynchronous execution | API-based BP execution |
| Generic connector | No-code integration with external systems via REST, SOAP, MQ, Kafka, FTP, and other protocols | Flexible inbound and outbound communication between a BP or AI Agent and an external system |
| Trigger connector | Custom Java-based triggers that start BPs on external events or scheduled polling | Event-driven automation and advanced polling |
REST connector
The REST connector is an external connector that enables you to run BP transactions using REST API calls. It listens to incoming HTTP requests and routes them to Control Tower for processing, making BPs accessible to external systems via standard HTTP protocols. Each API call is processed as a discrete transaction, identified by a signal ID unique to the target BP definition, and passes through the BP steps as a single unit of work.
The connector supports multiple request formats, authentication mechanisms, and optional response handling, making it suitable for processing individual documents, emails, or other business-specific data items via exposed API endpoints. For further details, see Process transactions with REST connector.
Generic connector
The Generic connector is a versatile, no-code solution that allows you to integrate external services into your automations without writing custom code. It supports a wide range of protocols and connection scenarios and can be configured to either send data to external systems or receive data from them.
Depending on the integration pattern, the Generic connector can be added as a standard Bot Task within a BP or used as a Trigger start element. This flexibility allows you to implement both outbound service calls and inbound data ingestion using the same connector framework. For configuration details, refer to Configure no-code Generic connector.
Trigger connector
The Trigger connector enables event-driven automation by starting BP workflows in response to external events or scheduled polling. It is commonly used in scenarios where processes must react to incoming emails, queue messages, file arrivals, or time-based conditions.
Trigger connectors are implemented in Java and deployed as Worker artifacts. Once deployed—either manually to Nexus or as part of an AI Agent Asset Bundle—they become available as Trigger elements in the BP Workflow designer interface, allowing BPs to be initiated directly by external events or polling logic. For configuration instructions, refer to Trigger Connector.
Email-specific connectors
| Connector | Purpose | Usage |
|---|---|---|
| Email Fetch connector | UI-configurable ODF 2-based email retrieval | Outlook and Exchange email automation |
| Simple Email connector | Lightweight email retrieval from MS Exchange with S3 storage | Exchange mailbox processing |
Email Fetch connector
The Email Fetch connector is an ODF 2–based library designed for receiving emails from supported email services and preparing them for automated processing.
The connector supports both modern and legacy Outlook integrations and includes the necessary data structures and configuration forms to manage email retrieval and processing within the platform. It is distributed as a Maven dependency and is available through Solution Catalog in Control Tower. For more details, see Email Fetch Connector.
Simple Email connector
The Simple Email connector provides a streamlined solution for retrieving emails from Microsoft Exchange mailboxes using the Microsoft Graph API. Unlike the Email Fetch connector, it has no direct Work.AI platform dependencies, making it a lightweight option for focused email retrieval scenarios.
The connector retrieves new emails from configured folders, stores attachments in S3, and outputs references to the stored content for downstream processing. After processing, emails can be moved to designated folders to prevent reprocessing.
The Simple Email connector is distributed as an Asset Bundle and can be downloaded from the public Nexus repository or installed via Solution Catalog in Control Tower. For details, refer to Simple Email Connector.
Proprietary and enrichment connectors
In addition to the core connectors listed above, Work.AI includes a broad set of proprietary and enrichment connectors widely used by AI Agents. These connectors enable automated alert ingestion, message-based integrations, file and content processing, outbound notifications, and data enrichment.
| Connector | Purpose | Usage | AI Agent |
|---|---|---|---|
| Bridger XG connector | Integration with LexisNexis Bridger for alert ingestion, enrichment, and lifecycle updates | Automated alert polling, splitting, enrichment, and decision-making in anti-money laundering (AML) workflows | |
| Firco Continuity Case Manager API connector | Integration with Firco Continuity for alert retrieval and status management | Processing Firco alerts and applying AI-driven decisions | Tara |
| Firco PI Continuity connector | Integration with Firco PI for transaction screening alerts | Transaction screening alert processing and automated resolution | Tara |
| Thomson Reuters CLEAR connector | Integration with Thomson Reuters CLEAR for public record search and monitoring | Adverse media monitoring (AMM) and entity watchlist polling | |
| Dow Jones Factiva | Integration with Dow Jones Factiva for screening and media retrieval | Initiating screening requests, creating cases, and retrieving alerts and media content | Evan |
| World-Check One | Integration with World-Check One for screening and adverse media | Submitting screening requests, creating cases, and retrieving alerts and media | Evan |
| Google GeoCode API | Address validation and geocoding | Validating and normalizing address data | Any |
| OpenCorporates API | Company data enrichment | Validating and enriching company profiles | Tara |
| Google Custom Search API | News and web content retrieval | Retrieving and processing news articles for enrichment | Evan |
| AMF—Company Profiles | Entity verification via public registries | Validating entity status and capturing evidence | Kayla |
| Companies House Public Data API—Company Profiles | Company registry data retrieval | Retrieving official company information | Kayla |
| CSSF—Entity Profiles | Regulatory registry verification | Validating entity status and capturing evidence | Kayla |
| Department of Labor (EFAST 5500) | Retirement plan and filing retrieval | Retrieving Form 5500 filings and related data | Kayla |
| NYSE | Market and company data enrichment | Retrieving publicly available market data | Kayla |
| Sayari Graph—Resolution | Entity resolution and enrichment | Resolving entities and retrieving related data | Kayla |
| US Securities and Exchange Commission—Edgar | Public filings and disclosures | Retrieving company filings and disclosures | Kayla |
| US Securities and Exchange Commission—Mutual Fund Profiles | Fund profile verification | Validating fund status and capturing evidence | Kayla |
| Twelve Data | Financial and market data enrichment | Retrieving financial and market data | Kayla |