Outlook add-in

Category: Add-in

Version: 1.0

Last updated: Januari 13, 2026

Author: Any2Info


Description

The Any2Info Outlook Add-in integrates directly into Microsoft Outlook and allows users to trigger dataflows, agents and agent chats from selected emails. The add-in is registered in Outlook via an XML manifest and appears in the Add-ins tab of the Outlook ribbon.


Installation

Install via Outlook In-Client Store

Steps:

  1. Open Outlook in your browser

  2. Select My add-ins

  3. Choose Add a custom add-in

  4. Upload the XML manifest

  5. Confirm the installation

After installation, the add-in becomes available in the Add-ins tab in Outlook.


Platform Configuration – Add-ins

The Add-ins configuration defines how external applications, such as the Outlook Add-in, interact with the Any2Info platform.

General Settings

Field
Description

Application

The external application that triggers the action (e.g. MS Outlook).

Name

Display name shown to the user in the add-in.

Description

Short description explaining the add-in action.

Successful message

Message shown when execution succeeds.

Failed message

Message shown when execution fails.

Required values message

Message shown when required input is missing.

Icon

Icon displayed in the add-in interface.

Action Types

The Action field determines how the platform handles the add-in request.

Dataflow

Triggers a predefined dataflow.

Use when:

  • Processing emails or attachments

  • Transforming or storing data

  • Integrating with external systems

Required configuration:

  • Flow: Select the dataflow that will be executed

Agent

Executes an AI agent.

Use when:

  • AI-based processing is required

  • Decisions or classifications must be made

  • Dynamic responses are needed

Agent Chat

Starts an interactive chat session with an AI agent.

Use when:

  • User interaction is required

  • Follow-up questions are expected

Entity Mapping

Entities define how incoming data from the external application is mapped into the platform.

Email Entity Example

Each email field can be mapped to a target field used within the platform.

Source Column

Subject

Date

Body

From

To

CC

Attachment

Mapping Behavior

  • Only mapped fields are forwarded to the selected action.

  • Multiple entities can be configured per add-in.

  • The Mapped only option filters the view to mapped fields only.

Flow Selection

When Action = Dataflow, the selected flow determines how the incoming data is processed.

Example:

  • Flow: Full mail

  • Flow: Full mail with attachment

Addin settings

Language selection

The language of the Outlook Add-in can be selected directly by the user via the settings menu (gear icon) inside the add-in. The available languages depend on the translations configured in the Any2Info platform.

Display Texts

All visible texts in the add-in are resolved using Display Texts.

To support multiple languages:

  • Display texts must be defined in the platform

  • Translations must be available for the selected language

If a translation is missing, the default text will be shown.

Download logging

The settings menu of the Outlook Add-in allows users to download the execution logs.

Downloaded logs are saved to the local Downloads folder of the user’s computer and can be used for troubleshooting and support purposes.

Logout

In the settings menu, the user is also able to log out.

Validation

After configuration:

  1. Open Outlook

  2. Select one or more emails

  3. Launch the Any2Info Add-in

  4. Choose the configured action

Successful execution confirms the platform configuration.


Tips & Best Practices

  • Use clear success and error messages to provide meaningful user feedback

  • Use one add-in per use case to keep actions focused and maintainable

  • Choose the correct action type and only map the required values

  • Design add-ins to support multiple selected emails

  • Always use display texts to enable multi-language support

  • Use the download logging feature for troubleshooting and support


Changelog

Version
Date
Change

1.0

January 13, 2026

Initial documentation version added.

Last updated

Was this helpful?