Email Trigger Node

What is an Email Trigger Node?

The Email Trigger node monitors your Gmail or Outlook inbox and activates your workflow whenever a new email arrives. It extracts key information from the email such as sender, subject, body content, thread ID, and any attachments, making this data available for downstream nodes to process.

Outputs

When an email is received, the Email Trigger node provides the following outputs:

  • Sender (string): The email address of the sender of the email

  • Subject (string): The subject line of the email

  • Body (string): The full text content of the email body

  • Thread ID (string): The thread ID of the email, which can be used to reply to the email in a SendEmail action

  • Attachments (files): Email attachments stored in the data pool for use by other nodes

How to set up the Email Trigger Node

  1. Add an Email Trigger node to your workflow

  2. Connect your Gmail or Outlook account:

    • Click "New Connection" if no connection exists

    • Select an existing connection from the dropdown if available

  3. Configure any test values (these are only used in the workflow builder)

  4. Connect the Email Trigger node to downstream nodes in your workflow

  5. Publish your workflow to activate the trigger

Important Notes

  • The trigger will not work until you publish the workflow

  • You must configure a Gmail or Outlook connection before the trigger can be used

  • The Email Trigger node requires permission to access your Gmail or Outlook inbox

  • Test values are only used during workflow design and testing; they don't affect the actual trigger configuration

Using Email Data in Your Workflow

You can reference the email data in downstream nodes by:

  1. Selecting the Email Trigger node as an input source

  2. Using specific email fields (Sender, Subject, Body, Thread ID, Attachments) in your workflow logic

  3. Processing email content with AI nodes or other actions

Common Use Cases

  • Auto-reply to specific types of emails

  • Extract and process information from structured emails

  • Forward important emails to other systems

  • Create tasks or tickets based on email content

  • Filter and categorize incoming emails by sender or subject

  • Process data from email attachments

PreviousTypeform Trigger NodeNextScheduled Execution Trigger Node

Was this helpful?