Topic
Setting Up Email Ingestion Integration in Everbridge 360™.
Description
Email ingestion enables integration between Everbridge Suite and third-party alerting applications such as event monitoring tools, digital signage software, and CAD systems. Incoming emails are parsed and used to automatically launch incidents based on defined criteria.
The following requirements apply to email ingestion configuration:
- Incoming emails must be formatted as plain text
- Approved sender domain or wildcard format is required (for example, "*@yourdomain.com")
- Unrestricted sender domains are not supported
- API access must be enabled for the organization
Processing Behavior
HTML emails are converted to plain text with all HTML tags removed, smart characters are converted to standard characters, and email delivery and processing may introduce latency before incident creation.
Note: If no conditions are defined in the filtering criteria, all emails that meet the base sender and recipient rules will trigger an incident.
Testing and Validation
Test emails should be sent after configuration to confirm successful ingestion and incident creation. Use variable testing tools to validate mappings and parsing behavior before production use.
Troubleshooting
For issues related to email ingestion configuration, filtering behavior, or unintended incident creation, see the related knowledge article for additional information: EBS: Email Ingestion Integration Generates 'Internal ERROR Template Variable have change'
If the issue persists or further assistance is required, contact Everbridge Technical Support to review configuration settings and organization access.