Generating summaries of new emails using ChatGPT

As we all know, integrating artificial intelligence with software is all the rage these days. That's why EmailEngine has decided to follow the trend and integrate with the ChatGPT API to explore the usage of AI technology. The integration is not super in-depth, but it's a step forward in incorporating AI into the process.
So, what can this integration do for you? Well, with the help of ChatGPT API, EmailEngine can now generate summaries of incoming emails and even provide a sentiment estimation for the email. This can help you quickly assess the tone and importance of these emails for whatever reason you would need it.
It's important to note, however, that these summaries and sentiment estimations are only provided for webhooks about new emails, not for API requests.
PII alert! If ChatGPT integration is enabled then EmailEngine uploads the text content of incoming emails to the servers of ChatGPT. ChatGPT does not use this content for training, but you need to verify if this behavior is in accordance with your data processing agreements with your users.
To enable the integration, navigate to the Service configuration page and look up the Labs section. Provide the OpenAI API key, and check the "Generate summaries with OpenAI" checkbox.

If possible, use an API key of a paid OpenAI account. The API key for a free account has very strict rate limits, and if you are processing several emails at a time, then ChatGPT API requests will fail.
If everything is set up correctly and the integration works, then whenever you get a webhook for a new incoming email, it should include a section called summary. Also, consider that if you have configured webhooks not to contain any email message content, the summarization might fail, as there would be nothing to summarize.

EmailEngine will skip summary processing if requests to ChatGPT API fail for any reason. In that case, the summary section would be missing from the webhook payload. If you need to know why summaries are not included with the webhooks, check the logs of EmailEngine.