To integrate your emails with enneo, you have two general options that can be configured in Settings -> Email -> General Settings, which are IMAP and API.
By offering both IMAP and API integration options, enneo ensures flexibility and compatibility with different email setups and workflows. Whether you prefer a more traditional approach with IMAP or want to leverage the capabilities of the enneo API, you can choose the method that best suits your needs and seamlessly connect your emails to enneo.
1. IMAP
enneo fetches and sends emails from your IMAP mail server. enneo supports any number of mailboxes. This means you can connect multiple mailboxes to enneo and manage all your email communication from one place. Whether you have separate mailboxes for personal and work emails or multiple mailboxes for different projects, enneo's IMAP integration allows you to access and manage all your emails conveniently.
IMAP integration in enneo provides a seamless experience for managing your emails. You can read, reply, and organize your emails within enneo, just as you would in your email client. By connecting multiple mailboxes, you can consolidate all your email communication into one platform, eliminating the need to switch between different email accounts.
2. API
You can use the enneo API /ticket endpoints to create and manipulate emails. This powerful option provides a seamless two-way sync between enneo and your existing ticket systems. By utilizing the enneo API, you can not only retrieve and send emails, but also trigger webhooks and set up receiving webhooks to ensure that your email communication stays in sync with other systems or applications.
The API integration in enneo allows for a deeper level of customization and automation. You can programmatically create and manage emails, integrating them into your existing workflows and systems. This is particularly useful for businesses that want to run two ticketing systems in parallel, e.g. during a trial phase. With the two-way sync, any changes made in enneo or your ticketing system will be reflected in both platforms, keeping your email communication consistent and up to date.
Here you find a sample 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 for the relevenant /ticket
endpoints including parameters can be found here: