Email

To integrate emails with Enneo, two basic options are available that can be configured under Settings -> Email -> General Settings: IMAP and API.

With the ability to use both IMAP and API integrations, Enneo offers flexibility and compatibility for various email setups and workflows. Regardless of whether a traditional approach with IMAP is preferred or the advanced features of the Enneo API are to be used - both methods allow seamless connection of emails with Enneo.

​

IMAP

The IMAP integration retrieves emails from an IMAP mail server and sends them via this. Enneo supports an unlimited number of mailboxes, so multiple email accounts can be connected and all emails can be centrally managed. Whether private and professional mailboxes or multiple accounts for different projects - with the IMAP integration, all emails can be comfortably organized in one place.

The IMAP integration ensures a smooth experience handling emails. Emails can be read, answered, and organized, similar to a traditional email client. By connecting multiple mailboxes, all communication is bundled, and switching between different email accounts is no longer necessary.

​

API

The Enneo API and the /ticket endpoints allow creating and editing emails. This option offers a seamless two-way synchronization between Enneo and existing ticket systems. The API not only allows retrieving and sending emails but also triggering and receiving webhooks to ensure the synchronization of email communication with other systems.

The API integration offers a higher degree of customization and automation. Emails can be programmatically created and managed and seamlessly integrated into existing workflows. This option is particularly suitable for companies that utilize two ticket systems simultaneously, such as during a testing phase. Changes made in Enneo or another ticket system are synchronized on both platforms thanks to the two-way synchronization, ensuring consistent and up-to-date communication.

Here is an example of a request:

curl --location 'https://demo.enneo.ai/api/mind/ticket' \
--header 'Authorization: bearer <token>' \
--data-raw '{
    "fromName": "Customer Service",
    "process": "batch",
    "from": "support@enneo.ai",
    "to": [
        "eugene@enneo.ai"
    ],
    "priority": "medium",
    "channel": "email",
    "status": "open",
    "subject": "Subject",
    "body": "Body New",
    "direction": "in",
    "firstResponseDueBy": "2024-01-01 00:00:00",
    "dueBy": "2024-01-01 00:00:00",
    "tags": [
        54
    ],
    "contractId": 781506,
    "attachments": [
        {
            "name": "myattachment.png",
            "url": "https://www.enneo.ai/wp-content/uploads/2022/11/Frame.png"
        }
    ]
}'

Further details on relevant /ticket endpoints, including parameters, can be found here:

API Documentation