How it works
- Your pipeline includes an email trigger node
- Documents are sent (or forwarded) to the pipeline’s email address
- Ingestly extracts attachments from the email
- Each attachment triggers a separate pipeline run
Step 1: Add an email trigger
Open your pipeline’s editor and add an Email trigger node. The email trigger requires no configuration. The pipeline’s email address is generated automatically.Step 2: Find the pipeline’s email address
The pipeline’s email address is displayed on its Settings tab. It follows the format specific to your pipeline and organization. Copy this address to use for forwarding or as a destination address.Step 3: Connect the rest of the pipeline
Connect the email trigger to your action and output nodes, just like any other trigger. For example: Email Trigger → Extract Action → Callback Output Save and activate the pipeline.Step 4: Send a test email
Send an email with a document attachment to the pipeline’s email address. Ingestly processes each attachment as a separate document.Handling attachments
- Each attachment in an email creates a separate document and triggers a separate run
- Only supported formats are processed (PDF, JPEG, PNG, TIFF, HEIC)
- Unsupported attachments are ignored
- The email body itself is not processed. Only attachments are ingested
The total inbound email payload (headers, body, and all attachments) is capped at 30 MB. Messages larger than that are rejected before they reach the pipeline. For larger documents, use the webhook trigger instead.