Collect monthly invoices and email them to an accountant
The poster built a bot that logs into each site monthly, grabs the invoice, and emails it to their accountant. Task: Suggested implementation: Develop a Chrome extension named Severino to automate recurring vendor bill collection for providers like AWS, Vercel, GitHub, Google Cloud, Twilio, and Slack. The tool operates within the user's existing browser sessions to retrieve invoice PDFs from provider portals and email them to the accountant, utilizing saved 'recipes' for known providers. Human role involves initial setup, authentication maintenance, and exception handling for new or changed vendor interfaces.; tools: custom-built or unnamed agent. Human role: Source evidence is unavailable regarding specific human roles or division of labor.; limitations: Prerequisites include active browser sessions for all vendor portals and a configured email service. The source indicates only billing-page text leaves the machine, excluding cookies or tokens, but this claim is unverified due to source truncation. Integration uncertainty exists regarding how the tool handles multi-factor authentication or session expiry. Human approval is required before deploying to production environments..
Tools
custom-built or unnamed agent
Published on Agent Work Atlas:
Overview
The poster built a bot that logs into each site monthly, grabs the invoice, and emails it to their accountant.
Workflow
Suggested implementation: Develop a Chrome extension named Severino to automate recurring vendor bill collection for providers like AWS, Vercel, GitHub, Google Cloud, Twilio, and Slack. The tool operates within the user's existing browser sessions to retrieve invoice PDFs from provider portals and email them to the accountant, utilizing saved 'recipes' for known providers. Human role involves initial setup, authentication maintenance, and exception handling for new or changed vendor interfaces.
Reported result
Actual outcomes are unknown as the source text is truncated and the original URL returned a 403 error. The author claims the tool automates monthly invoice delivery, eliminating manual chasing on the 3rd of the month. Proposed acceptance check: Verify that invoices for at least three configured vendors are successfully emailed to the accountant on the scheduled date without manual intervention.
Human role
Source evidence is unavailable regarding specific human roles or division of labor.
Limitations
Prerequisites include active browser sessions for all vendor portals and a configured email service. The source indicates only billing-page text leaves the machine, excluding cookies or tokens, but this claim is unverified due to source truncation. Integration uncertainty exists regarding how the tool handles multi-factor authentication or session expiry. Human approval is required before deploying to production environments.
Try it
I need to build a Chrome extension prototype called 'Severino' to automate invoice collection. [replaceable inputs: Vendor list (e.g., AWS, GitHub), Accountant Email, Output Directory]. Steps: 1. Create a manifest.json for a Chrome extension with permissions for activeTab and storage. 2. Develop a background script that checks for scheduled times (e.g., 3rd of the month). 3. Implement a content script that navigates to [replaceable inputs: Vendor Portal URLs], locates the invoice PDF link using CSS selectors defined in a 'recipe' JSON file, and downloads it. 4. Integrate an email sending function (using a placeholder API) to send the PDF to [replaceable inputs: Accountant Email]. 5. Ensure no cookies or tokens are transmitted externally; only the PDF file and metadata. Deliverables: A zipped Chrome extension folder and a README.md. Quality Measure: Run a dry run with a mock vendor page. Confirm the PDF is downloaded and the email trigger fires. Safeguards: Do not connect to real vendor accounts yet. Use local mock HTML files for testing. Require my explicit confirmation before attempting any real network requests or email sending. If selectors fail, log the error and stop.
Source reports are not independently verified. Publication date is the catalog publication date, not the original article date.