DocPipe can receive and process documents sent via email. Each pipe has an auto-generated email address that you can forward documents to.
How it works
- Your pipeline includes an email trigger node
- Documents are sent (or forwarded) to the pipe’s email address
- DocPipe extracts file attachments from the email
- Each attachment triggers a separate pipeline run
Step 1: Add an email trigger
Open your pipe’s pipeline editor and add an Email trigger node. The email trigger requires no configuration. The pipe’s email address is generated automatically.
Step 2: Find the pipe’s email address
The pipe’s email address is displayed in the pipe’s Settings tab. It follows the format specific to your pipe 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 pipe.
Step 4: Send a test email
Send an email with a document attachment to the pipe’s email address. DocPipe processes each attachment as a separate file.
Handling attachments
- Each attachment in an email creates a separate file and triggers a separate run
- Only supported file formats are processed (PDF, JPEG, PNG, TIFF, HEIC)
- Unsupported attachments are ignored
- The email body itself is not processed. Only attachments are ingested
Combining with other triggers
You can have both an email trigger and an upload trigger (or HTTP trigger) in the same pipeline. Documents from any trigger flow through the same downstream actions and outputs.
Email ingestion is useful for automating document processing from existing workflows. For example, set up an email forwarding rule to automatically send invoices to your pipe.
