Collect monthly supplier and utility invoices into Google Drive

On the first business day of every month at 6am, collect that month's invoices and statements from the supplier, utility, and B2B portals that have no API, file them into Google Drive, and report back in Slack. Use a cron trigger that fires at 6am on the 1st, 2nd, and 3rd of each month, and exit immediately without doing any work unless today is genuinely the first business day of the month. That way the collection happens exactly once even when the 1st falls on a weekend or a public holiday.

Portal logins must never appear in this prompt or in the workflow configuration. Before the first scheduled run, set up a Notte credential vault: call Create Vault once, then Add Vault Credentials once per portal, keyed to that portal's login URL. Every scheduled run then references that vault by its id and attaches it to the browser session, so the agent authenticates out of the vault and no password is ever passed in the task text, logged, or repeated in the summary.

Work through the portal list one portal at a time. For each portal, use Start Session to open a cloud browser session with the credential vault attached, then use Start Agent against that session, telling it to log in, locate the invoices or statements dated in the month just gone, and download each one. Notte agent runs are asynchronous: Start Agent returns immediately, so poll Get Agent Status until the status leaves active, waiting roughly 15 to 30 seconds between checks. A Notte session defaults to a maximum duration of 15 minutes, so raise the max duration for portals known to be slow, and treat a run that hits the ceiling as a failure for that portal rather than retrying indefinitely.

When an agent run finishes, the downloaded documents live in that session's download storage rather than in the agent's written answer. Use List Session Downloads to see what the agent actually captured, then Download Session File to get a download link for each document. If a run reports success but produced no downloads at all, treat that portal as failed and say so in the summary instead of quietly reporting nothing.

File everything into Google Drive under a dated folder for the month. Use Create Folder to make a folder named for the month being collected in YYYY-MM format, inside the parent finance folder I nominate, and reuse that folder if it already exists rather than creating a duplicate. Then use Upload File (Multipart) to upload each retrieved document into it, naming files so the portal and the month are obvious, for example "2026-07 - Acme Utilities - invoice.pdf". Upload File (Multipart) handles files up to 5MB; if a document is larger than that, skip it and note it in the summary rather than failing the run.

The agent must stop rather than guess. If a portal presents multi-factor authentication, a one-time passcode, a CAPTCHA, or a login screen that no longer matches what it expects, it should stop work on that portal immediately and report what it saw. The same applies if the portal logs in fine but its invoice or billing area has clearly been redesigned and the agent cannot confidently identify the right documents. Never try to work around an authentication challenge, never submit a guessed code, and never download a document the agent is not confident is the correct one. A portal that stops this way is a normal reportable outcome, not an error to retry.

Finish with a single Slack Send a Message post to the finance channel. List each portal that succeeded along with exactly which documents were collected and filed, then a clearly separated section for the portals that did not complete, each with its reason: multi-factor prompt, changed layout, login rejected, timed out, or nothing found for the month. Include a link to the month's Drive folder. Finance treats that failure list as their manual to-do list, so name the portal and the reason plainly, and send the message even if every single portal failed.

Handle each portal independently throughout. One portal failing, timing out, or stopping on a login challenge must never prevent the remaining portals from being attempted, and must never stop the Drive filing or the Slack summary from happening.