WorkflowsBuildTriggers

Email Trigger

Start workflows when emails arrive

Email triggers start your workflow when an email arrives at a designated address. Use them to process incoming documents, respond to inquiries, or automate email-based business processes.

Getting Your Workflow Email Address

When you add an email trigger to your workflow:

  1. Select Email Received as the trigger type
  2. A unique email address is generated:
{workflow-name}@{your-org}.workflows.flint.com

For example:

invoice-processing@acme.workflows.flint.com

Emails sent to this address trigger your workflow.

Configuring the Trigger

Sender Filtering

Control which emails trigger the workflow:

FilterDescription
Any senderAll emails trigger the workflow
Specific domainsOnly from @partner.com, @vendor.com
Specific addressesOnly from invoices@supplier.com
Trusted sourcesFrom addresses in your trusted sources list

Subject Filtering

Filter by email subject:

FilterExample
ContainsSubject contains "Invoice"
Starts withSubject starts with "[ORDER]"
Matches patternSubject matches regex PO-\d{6}

Attachment Requirements

Specify attachment requirements:

SettingBehavior
Not requiredProcess with or without attachments
RequiredOnly trigger if attachments present
Specific typesOnly PDF, XLSX, etc.

Accessing Email Data

In your workflow, access email content via trigger:

{{trigger.from}}              // Sender email address
{{trigger.to}}                // Recipient address (JSON string)
{{trigger.subject}}           // Email subject
{{trigger.text}}              // Plain text body
{{trigger.html}}              // HTML body
{{trigger.emailId}}           // Unique email identifier
{{trigger.attachmentCount}}   // Number of attachments

Attachments

Access attachments as an array:

{{trigger.attachments}}              // All attachments
{{trigger.attachments[0]}}           // First attachment
{{trigger.attachments[0].filename}}  // File name
{{trigger.attachments[0].content}}   // File content (base64)
{{trigger.attachments[0].mimeType}}  // MIME type
{{trigger.attachments[0].size}}      // Size in bytes

Trusted Sources

Trusted sources are pre-approved senders that can trigger your workflows. Manage them in Settings Trusted Sources.

Add a Trusted Source

Click Add Source and enter:

  • Email address (invoices@supplier.com)
  • Or domain (@supplier.com)

Verify (Optional)

For higher security, verify the source:

  1. Flint sends a verification email
  2. The source clicks the link
  3. Source is marked as verified

Assign to Workflows

In your email trigger, select Trusted Sources Only and check which sources apply.

Email Processing Tips

Setting Up Email Forwarding

If you receive emails at an existing address and want to process them in Flint:

Gmail Forwarding

  1. In Gmail, go to Settings Forwarding
  2. Add your Flint workflow address
  3. Verify the forwarding address
  4. Choose "Forward a copy" or set up a filter

Outlook/Microsoft 365

  1. Go to Settings Mail Rules
  2. Create a rule for emails matching your criteria
  3. Set action to "Forward to" your Flint address

Generic SMTP Forwarding

Configure your email server to forward:

  • All emails to a specific address
  • Emails matching certain criteria
  • A copy (BCC) of all incoming mail

Testing Email Triggers

Send a Test Email

  1. Compose an email to your workflow address
  2. Include test content and attachments
  3. Send and watch the workflow run

Use the Test Feature

  1. In the workflow editor, click Test Trigger
  2. Enter sample email data:
    • From address
    • Subject
    • Body
    • Upload test attachment
  3. Click Run Test

Troubleshooting

IssueCauseSolution
Email not triggeringSender not in filterCheck sender filtering settings
Attachments missingLarge files rejectedCheck attachment size limits (25MB)
Wrong sender showingForwarding issueCheck header parsing settings
Duplicate runsEmail sent multiple timesEnable deduplication by message ID
Delayed processingHigh volumeCheck your workflow queue

Best Practices

  • Use specific addressesinvoices@ rather than inbox@
  • Filter senders — Always restrict who can trigger workflows
  • Handle failures — Add error handling for malformed emails
  • Monitor volume — Set up alerts for unusual email volumes
  • Test with production-like data — Use realistic attachments and content

On this page