Auto-submit your weekly portal report from a spreadsheet

By General Input

Every Monday an AI browser agent reads the next row from your spreadsheet, logs into the portal, submits the form for you, and Slacks the confirmation.

Integrations

  • Browser Use Cloud
  • Google Sheets
  • Slack

Type

Deterministic Code

Categories

  • Operations

Every Monday at 8am, automatically submit our recurring web-portal report so nobody has to re-key the same numbers by hand. This is a fixed, deterministic pipeline, so build it as a code workflow where every step is a known node: read one pending row, run one browser task with those values, write the result back, and notify.

Start with Google Sheets Get Values to read the next pending submission row from the tracking sheet. Each column holds one of the form field values, plus there is a status column. Select the first row whose status is empty or Pending, so a row that was already submitted is never picked up again.

Pass those column values to a Browser Use agent task with Run Agent Task. The task should use a saved Browser Use login profile so it does not have to re-authenticate the portal each week, then log into the vendor or government portal, fill the required web form with exactly those values, and submit it. Instruct the agent to return the confirmation or reference number the portal shows after a successful submission, and to report whether the submission actually succeeded.

Because Browser Use tasks run asynchronously, poll Get Session until the session leaves the running state, then read its output and its task success flag.

If the task reports success and returns a confirmation number, use Google Sheets Update Values to write that confirmation number plus the current timestamp back into the same row and set its status column to Submitted, so the row can never be submitted twice. Then post a Slack confirmation to the operations channel with Send a Message that includes the row identifier, the confirmation number, and the timestamp.

If the task reports that it was not successful, leave the row unmarked. Do not set the status to Submitted and do not write a confirmation number, so the row will be retried on the next run. Instead, post a Slack alert to the operations channel with Send a Message so someone can step in and complete the submission manually.

Related prompts

Explore more prompts
Call overdue Xero customers with an AI collections agentLocal listing health board for every location you manageWin back LiveChat visitors whose chats went unansweredLet support send one-off Loops emails without an engineerStop cold emails to anyone with a live deal in PipedriveiMessage campaign console with pre-flight checks and delivery boardChat quality review board for LiveChat support leadsLinkedIn Ads budget pacing dashboard for every client accountFront desk appointment confirmation board for the next 3 daysGive your team Looker numbers without buying more seats