Skip to main content
AI connectors are designed to connect to a number of AI models that expose a REST API. The supported list is below.

Key Capabilities

  • Multi-provider AI integration
  • Flexible prompt engineering
  • Customizable AI model selection
  • Structured output control
  • Intelligent content processing

Overview

The AI connector is a flexible integration tool that connects to any AI model via REST APIs, enabling you to process input messages using configurable system and user prompts to generate structured outputs within your data flows. It supports popular AI services like OpenAI, Gemini, Ollama, and other OpenAI-compatible providers, with full control over API endpoints, models, and parameters. With Script-enabled prompts and customizable output formats, the connector enables use cases such as extracting insights from unstructured feedback, translating content across languages, and transforming text data into actionable structured information.

Actions

Connector Configuration

This section contains all of the configurable connector properties.

AI Config Tab

If you have not already configured the global AI settings at Settings > Advanced > AI Settings, the AI Config tab displays a message that you must do this before you can use the connector. Click the Configure AI Settings button, and follow the instructions in AI Settings. If the global settings have already been configured but you want to override them in this connector, click Edit. To override the global settings, toggle on Override global setting. Now you can select which AI provider you want to use, enter the appropriate connection details and then save the configuration. The connector supports the following providers:
  • Claude
  • Deepseek
  • Gemini
  • Grok
  • Ollama (cloud and local)
  • OpenAI
  • OpenAI Compatible (any AI provider that implements OpenAI’s API)
Use the Edit AI Settings pane to define the Base URL (only available when the provider is Ollama or OpenAI Compatible), add the provider’s API Key, and select a Model. To populate the User Prompt field, you can click Suggested Prompts to see a set of predefined prompts for a variety of use cases, or you can enter your own prompt directly into the field. This is where you define the task or request that you want the connector to perform when it receives a file. For example, you could enter something like Summarize the inbound EDI X12 file using natural language so that employees who are not familiar with the EDI X12 structure can read the summary and understand what information the document contains. This field supports Script. You can also choose to Attach input messages to requests. This is especially useful when you are providing binary files (such as a PDF or image) to the AI provider. To include non-binary files in the request, you need to use _message.body in your prompt, like this:
See the Summarize option in the Suggested Prompts dropdown for a complete example.
Toggle System Prompt to provide a set of specific instructions, constraints, languages, or roles that the AI provider should use when providing its response. For example: Do not use any em dashes or emojis in your response. This field also supports Script. The way in which you test your configuration and prompts varies by the connector’s action type:
  • If your connector is a trigger, click the Test button.
  • If your connector is a transform or terminal, on the Testing tab, paste content into the Input Body or use the dropdown to add Headers and values, then click the Test button.
In both cases, the test results appear in the Testing tab. Logs from the test are displayed in the Log tab.

Settings Tab

Settings related to the core configuration of the connector.

Configuration

Advanced Settings

Advanced Tab

Other Settings

Proxy Settings

Message

Logging

Miscellaneous

Automation Tab

Automation Settings

Settings related to the automatic processing of files by the connector.

Alerts Tab

SLAs Tab

Transactions Tab

This tab lists all messages associated with the connector. Use the search bar to find specific messages, or click the funnel icon to apply a filter. You can filter by time, message direction, and/or status. Options on this tab vary depending on the connector’s action type:
  • If your connector is a Trigger, use the Receive Files button to start the flow.
  • If your connector is a Transform or Terminal, use the Upload Files button to upload files to the flow.

Macros

Examples