Example: Email-to-Data Pipeline
Scenario: You receive documents by email (invoices from vendors, contracts from partners, reports from field teams) and need to extract data from them automatically.
Overview
Email with PDF attachment → qomplement email inbox →
Email Inbox trigger → Parse document → Fill Excel template →
Send results email to your team
Setup
Step 1: Get your upload email address
- Go to Clouds in the sidebar
- Find your unique
@qomplement.comemail address - Copy it
Step 2: Set up email forwarding
In your email client, create a rule to forward matching emails:
Gmail:
- Settings > Filters and Blocked Addresses > Create new filter
- From:
vendor@example.com(or whatever matches) - Has attachment: checked
- Forward to:
your-id@qomplement.com
Outlook:
- Rules > New Rule
- From specific people + has attachment
- Forward to
your-id@qomplement.com
Step 3: Build the workflow
- Go to Workflows > New Workflow
- Add an Email Inbox trigger node
- Connect a Parse Document node (select your extraction template)
- Connect an Excel Template node (select your spreadsheet template)
- Connect a Send Email node:
- To:
your-team@company.com - Subject:
New document processed: {filename} - Attach: the filled Excel file
- To:
- Save and activate
Step 4: Test it
Send a test email with a document attachment to your upload address. Within minutes:
- The document appears in qomplement
- The workflow triggers
- Data is extracted and mapped to Excel
- Your team receives the filled spreadsheet by email
Advanced: Add routing
Use a Condition node to route documents differently:
Email arrives → Parse →
IF amount > $10,000 → Email to finance manager
ELSE → Email to accounting team
Or use Switch to handle different document types:
Email arrives → Parse →
SWITCH on document_type:
"invoice" → Fill Invoice Excel template → Email accounting
"contract" → Fill Contract Excel template → Email legal
"receipt" → Fill Expense Excel template → Email admin
Tips
- Test the email forwarding before building the workflow — make sure documents arrive
- Set up failure notifications on the workflow schedule so you know if something breaks
- Start simple — get the basic pipeline working before adding conditions and branching