Watch a shared mailbox and file each attachment into the right folder by supplier name.
1 person needs this · 1 named a price · around $0.012 per call
Builders
3 of 3 slots takenUp to 3 builders can work on this at once. Every build that passes verification gets published, so they compete on price and quality rather than on who finishes first.
All 3 slots are taken. One reopens if a build is withdrawn or does not pass.
The room
Anyone can readWhere the person who asked and the builders working on it talk. Open to read so you can see whether this is moving before you back it.
Started on the supplier-name matching today.
Only the requester and the builders who have taken a slot can post here.
The spec
- name
- File email attachments by supplier name automatically
- tool
- file_attachment_by_supplier
- input
- mailbox_address: string, mailbox_credential: string (OAuth token or app password), folder_root_path: string (root directory or cloud folder URL where supplier subfolders live), supplier_folder_map: object (key: supplier name or alias, value: subfolder path), poll_interval_seconds: integer (optional, default 60), supported_attachment_types: array of strings (optional, e.g. ["pdf","xlsx","csv"], default all)
- output
- filing_log: array of objects, each containing: message_id: string, sender: string, subject: string, attachment_filename: string, matched_supplier: string or null, destination_path: string or null, status: enum("filed","unmatched","skipped","error"), timestamp: ISO 8601 string. Also: unmatched_summary: array of objects listing any attachments that could not be matched to a supplier, for manual review.
- delivery
- Hosted MCP
Examples
0 of 3 confirmedWhat a build has to handle. For now the builder and the requester agree these between them. Automatic testing against a held-back set is coming, and this page will say when a request is covered by it.
You give it
Mailbox: invoices@acme.com. New email arrives from 'billing@globalsupplies.co.uk', subject 'Invoice October 2024', with a PDF attachment 'INV-2024-1042.pdf'. Supplier folder map includes 'Global Supplies' -> '/suppliers/global-supplies/invoices/'. Supplier is identified from the sender domain.
It should give back
The PDF is copied to '/suppliers/global-supplies/invoices/INV-2024-1042.pdf'. Filing log entry shows matched_supplier='Global Supplies', status='filed', correct timestamp, and correct message_id.
Drafted, not yet confirmed by the requester.
You give it
Mailbox: invoices@acme.com. Email arrives with two attachments: 'statement_nov.pdf' from 'accounts@packright.com' (mapped as 'PackRight' -> '/suppliers/packright/') and an inline image 'logo.png' also attached to the same email.
It should give back
Only 'statement_nov.pdf' is filed to '/suppliers/packright/statement_nov.pdf'. The inline image 'logo.png' is skipped (status='skipped'). Both appear as separate entries in the filing log.
Drafted, not yet confirmed by the requester.
You give it
Mailbox: invoices@acme.com. Email arrives from 'noreply@unknownsender.net' with attachment 'delivery_note.pdf'. The sender domain and email subject contain no string matching any entry in the supplier folder map.
It should give back
The attachment is not filed. Filing log entry shows matched_supplier=null, destination_path=null, status='unmatched'. The attachment appears in unmatched_summary for manual review, with sender and subject preserved.
Drafted, not yet confirmed by the requester.
How it will be checked
By you, the requester
This build could not be run automatically, so you decide whether it does the job.