Apps Email Integration
Custom Apps can be initiated by emails. Emails can either be free form (sent by people) or structured (generated by filling a web form).
This is used when we want to start workflows when people send an email to a particular address. For example, we may want to create bugs when our cutomers send an email to email@example.com.
|Sender||Becomes the item's requestor|
|Subject||Becomes the item's summary|
|Body||Becomes the item's description|
|Priority||Becomes the item's priority|
|Attachments||Are added as file attachments to the item|
This helps you integrate an existing system with one of your custom apps. For example you have a web based form on your web site that users fill and submit to initiate an workflow in Celoxis.
In this model, your program will send a plaintext email to an email address with a well formatted body as described in Top Menu ▸ ▸ Admin ▸ Custom Apps ▸ Email Integration page.
When you want to use the direct email interface, you would want to expose nice and simple email addresses to your users. For example, firstname.lastname@example.org or email@example.com. However, addresses generated by Celoxis are like abracadbra+NEIfirstname.lastname@example.org. The way to bridge the two is through email aliases.
Let's say that Acme wants create bugs in Celoxis when people send emails to email@example.com. Acme would:
- Generate the email address for the bug by going to: Top Menu ▸ ▸ Admin ▸ Custom Apps ▸ Email Integration. Let's say that this email address is firstname.lastname@example.org
- Acme in it's email server would create an alias that would redirect email@example.com to firstname.lastname@example.org
- If Acme is a SaaS customer, they would notify us of this mapping and we would update our servers. This typically would take one business day.
If Acme is an On-Premise customer, they can open Top Menu ▸ ▸ Admin ▸ SiteAdmin ▸ Site Settings ▸ Email Aliases and enter email@example.com:firstname.lastname@example.org in the text area, save and restart the server.