Email Trigger Node
Entry or waypoint
Email Trigger has two current uses:
- with no incoming connection, a matching message starts the workflow;
- with an incoming connection, the running workflow waits at this node for a matching message.
The On Email Received Start choice opens the same trigger configuration for an entry trigger.
Basics
Open the node and configure:
| Setting | Purpose |
|---|---|
| Name this trigger | Optional label for the subscription. |
| Which mailbox should we watch? | Choose a managed RAPTIX address or an available connected mailbox. |
| New RAPTIX address | Create a managed address when the address pool is enabled. |
| Check for new emails every | Polling interval for a connected mailbox; minimum 60 seconds. Managed addresses receive messages without this polling interval. |
| Wait timeout | Optional minutes, hours, or days for a mid-workflow wait. Use its timeout route when configured. |
| Who sends it? | Anyone, Specific people, or Anyone from a company. |
| Subject contains | Optional subject match. |
| Attachments | Doesn't matter, Must have files, or Must have no files; optionally limit file types. |
| Save attachments for later nodes | Preserve matching files as workflow values for downstream nodes. |
Automatic replies and no-reply messages are skipped by the trigger protections.
Filters
Choose whether All conditions match or Any condition matches, then use only the groups the process needs:
| Group | Current controls |
|---|---|
| People | Must be CC'd, must be BCC'd, excluded senders, Internal/External sender, and Reply-To different from sender. Internal/External uses the company domains defined in Organization. |
| Attachments | Minimum/maximum count, minimum/maximum size in MB, calendar invite, and Real attachment/Inline image placement. The Basics tab also controls required/no files and optional file extensions. |
| Content | Body contains, subject or body contains, excluded words, document-number detection with an optional regex, project codes, and Arabic/English/Mixed language. |
| Email state | High/Normal/Low priority, Read/Unread state, New/Reply/Forwarded thread type, and minimum/maximum email age in minutes. |
The Filters tab badge shows how many advanced filters are configured. Several narrow rules can prevent legitimate messages from matching, so test after adding or removing a rule.
Organization, Schedule, and Rate limits
- Organization — enter Company domains for internal/external classification and optional allowed sender organizations. The watched folder is the mailbox folder shown by the panel, normally INBOX.
- Schedule — set optional working-hours start/end, working days, and timezone. Messages outside the configured hours still run immediately in the current product, but are marked as off-hours; Schedule is not a pause window.
- Rate limits — set the maximum emails per hour overall and per sender, maximum workflows running at once, per-sender cooldown seconds, and the consecutive-failure threshold that pauses processing.
Testing and live status
After a subscription has been saved, the panel shows Running or Stopped, a refresh control, and a failed in DLQ count when failures exist. The current panel exposes the count as a warning badge; it does not show a separate dead-letter table or retry action.
The Testing tab is Enterprise-only and provides:
- Test mode (Dry Run), which evaluates messages without starting the workflow;
- Test connection, available after the subscription is saved;
- Preview recent matches, showing matched/skipped messages and skip reasons;
- Test with a sample email, using a subject, sender, body, and optional attachment filenames without requiring a saved subscription.
The sample result states whether the workflow would run and shows the pass/fail result for each evaluated rule.
Save and start
- Save the workflow first so it has a persistent record.
- Save the Email Trigger node again to create or update its subscription.
- Use the trigger's Start control and confirm its status is Running.
- Send a controlled matching email.
- Verify the new instance or waiting step in All Instances.
Use Stop when the mailbox should no longer create or release instances. Stopping the subscription does not delete the workflow design.
Email variables
The node makes message data available to later nodes, including subject, sender, body, and saved attachments where configured. Open Variable Panel and copy the exact generated variable rather than typing a guessed name.
Troubleshooting
| Problem | Check |
|---|---|
| Subscription cannot be saved | Save the workflow, then save the node again. |
| No message matches | Running status, mailbox, sender, subject, attachment rule, Filters, Organization, Schedule, and rate limits. |
| Connected mailbox is slow | Polling interval is at least 60 seconds; managed addresses do not use that interval. |
| A mid-workflow wait never resumes | Confirm the incoming connection, matching rules, and timeout configuration. |
| Files are unavailable later | Enable Save attachments for later nodes and select the result from Variable Panel. |
| A DLQ warning appears | Refresh the status, check the consecutive-failure threshold and mailbox connection, and investigate the underlying workflow or delivery error. The current panel shows a count, not a DLQ table. |
| Testing is not visible | The Testing tab is Enterprise-only. |