Use the Email Trigger to initiate workflows from incoming emails, without relying on vendor credentials or third-party integrations. This is especially useful when a vendor supports email-based notifications or where traditional integrations are unavailable or restricted.
When you create a new Email Trigger integration instance, a unique email address (e.g., abc123@mg.torq.io) is automatically generated. Instruct your third-party vendor to use this address as the destination for notifications. Upon receipt of an email, the Email Trigger automatically initiates the associated workflow. This workflow can include actions such as initiating threat mitigation, notifying the on-call engineer via Teams or Slack, etc.
To avoid running a workflow repeatedly for the same event, use the Deduplicate operator. This is useful when vendors send repeated notifications for a single event.
Attachments are supported and included as file links in the event payload.
Emails are limited to 4MB in total, including attachments.
How to use
Navigate to Integrations: Go to Build > Integrations > Triggers > Email Trigger and click Add instance.
Name the integration: Give the instance a unique and meaningful name. No other authentication details required.
Finalize: Click Add.
A unique recipient email address is autogenerated for each instance you create.
Share the generated email address: Provide it to the third-party vendor or set it as the destination for email notifications.
Trigger the workflow on receipt: When an email arrives at this address, Torq automatically initiates the associated workflow.
If the integration is shared, the destination workspace won't be able to see the auto-generated email address.
