MailTrigger Documentation

Welcome to MailTrigger’s documentation! Use the sidebar to navigate through the sections.

Contents

• What is MailTrigger?
  • Key Features
  • How It Works
  • Why Use MailTrigger?
• Real-World Use Cases
  • Travel Alerts Without API Hassles
  • Multi-Domain Email Simplified for Startups
  • Automated Internal Alerts for DevOps Teams
  • Customer Support Made Smarter and Faster
• Scenarios of Using MailTrigger
  • Real-Time Alerts from DevOps Tools
  • Add New Channels Without Changing Your Code
  • Forward Emails from Gmail to Messaging Apps
• Quick Start
  • Step 1: Create Your Account
  • If You Have Your Own Domain
    • Step 2: Verify Your Domain
    • Step 3: Create Mailbox
    • Default SMTP to Origin Route
      • Manual Setup (If Your Domain Has No Valid MX Record)
    • Step 4: Send a Real Email from the Command Line
      • Windows (PowerShell)
      • Linux (swaks)
      • Expected Results
  • If You Don’t Have a Domain
    • Get Your Free Mailbox Address
    • Understand the Goal
    • Step 2: Create a Route for Your Built-In Mailbox
    • Step 3: Send a Test Email to Your MailTrigger Mailbox
      • Using an External Mail Client (e.g. Gmail)
      • Using the Command Line
      • Expected Results
  • (Optional) Incoming Mail for Custom Domains
    • Enabling Incoming Email Support
    • Relay to Origin Route
• Tutorial
  • The Story
  • Goal & Expected Outcome
  • Step-by-Step Guide
    • 1. Create Your Account and Mailbox
    • 2. Create the Payment Keyword Rule
    • 3. Create the Forward Action
    • 4. Create the Route
    • 5. Verify Route Order
    • 6. Quick Testing (Command Line)
      • Windows (PowerShell)
      • Linux (swaks)
    • 7. Sample GitHub Workflow
  • What Happens Now?
  • Alternative Setup: Trigger Routes via Built-In Mailbox
    • How This Works
    • Why This Might Be Useful
  • Enhancement: Add Telegram Alerts for Alice
    • Story: Alice Checks Telegram More Than Email
    • Goal & Expected Outcome
    • Steps to Add Telegram Notifications
      • STEP 1: Obtain Alice’s Bot Token & Chat ID
      • STEP 2: Create the Telegram Action
      • STEP 3: Attach the Action to the Existing Route
      • Quick Test
• Key Concepts
  • Mailbox
  • Rules – When should something happen?
    • Supported Rule Types
  • Actions – What should happen next?
  • Routes – The pipeline that connects rules to actions
  • Example Scenario (Illustrative)
• Integrations
  • Chat & Messaging Notifications
    • Telegram Action
    • Discord Action
    • Slack Action
    • LINE Action
    • Microsoft Teams Action
    • WhatsApp Action
  • Core Email Actions
    • SMTP Action
    • Forward Action
    • AutoRespond Action
    • Relay Action
  • API Integration
    • API (Webhook) Action
  • Automation & Intelligence
    • LLM Action
    • JavaScript Action
    • WASM Action
• Advanced Features
  • LLM Rule usage and prompt examples
  • LLM Action
    • Feature 1: Modify Email Content
    • Feature 2: Control whether to execute next Action (passToNext)
    • Feature 3: Attach response as a file
  • JS Rule & JS Action
    • JS Rule: Custom logic using JavaScript
    • JS Action: Dynamically modify or process email
  • Attaching Action Results as Mail Attachments
  • Inline Variables for Actions
    • Available Inline Variables
    • Usage Examples
  • Email forwarding and SMTP relay
    • Forward Action: Send to another mailbox via external SMTP
    • Relay Action: Send mail directly via MailTrigger
  • Setting Up Scheduled Actions
• Recipes
  • 1. Webhook (API) Action → JS Action → Telegram Action
    • Use Case
    • Overall Flow
      • 1. API Action
      • 2. JS Action
      • 3. Telegram Action
  • 2. LLM Action + Auto Respond
    • Use Case
    • Overall Flow
      • 1. LLM Action
      • 2. AutoRespond Action
• Send Mail via MailTrigger
  • A. Verify and Configure Domain
  • B. Create RelaySMTP Action
  • C. Create a Route to Use RelaySMTP
• Gmail SMTP Setup Guide
• Testing & Debugging
  • 1. Viewing Route / Action Logs
    • Route Logs
    • Action Logs
    • Debugging Tips
  • 2. Test Suite for Rule / Action / Route
    • Preparing a Test Email
    • Running the Test
• API Access
  • 1. API Token Generation
  • 2. Authentication (No Username/Password Support)
• MailTrigger API Reference
  • Available APIs
  • Additional Notes
  • When Would I Need to Use These APIs?
• System Notifications
  • Routing System Notifications (Rate Limits, Quotas)
  • User Profile: LLM API Key & Notification Defaults
• Technical Explanation
  • What is WebAssembly?
  • Creating Custom WASM Files
  • Sample Program
• Release Notes
  • MailTrigger Release History
• FAQ
  • Why is the Route Not Triggering?
  • What Are SPF / DKIM / DMARC Checks?
  • Why Was a Route Marked as Quarantined?
  • Why Are There Default “SMTP to Origin” and “Relay to Origin” Routes?