well_create_portal_fetch

io.github.WellApp-ai/well-mcp · Verify this server

Start one Well cloud browser run, in the background, that signs in to each named supplier's portal with the person's saved login, finds the invoices of the named payments, downloads their PDFs and attaches each one to its payment. Use it only on WhatsApp, and only when the person explicitly asked to fetch the receipts as a background task (« en tâche de fond », « in the background »): without that ask, a supplier's portal goes through the Well extension. Use it for leads of well_list_missing_invoices whose `available_routes` holds `cloud_portal_fetch` and that the person picked, by number or by name, from the numbered recap you sent in an earlier turn. The background ask is not a pick: send the recap with its numbered leads first, and start nothing in that turn. Call it once per workspace with every picked portal lead of that workspace: at most 5 suppliers. For each supplier pass the row's `company_id` and the `id` of each of its `transactions`, never a transaction of another row. Well reads the portal address of the supplier itself. Never pass a supplier the person did not pick. The run never pays and never clicks a button of the site. Well sends the outcome to the person on WhatsApp itself, with each supplier it has no saved login for and the way to fetch it through the Well extension. Never ask the person to send a login or a password in the conversation. Follow the result's `message`: never say a receipt was found or attached. On a later question about these receipts, read well_list_missing_invoices again: the report reaches the person outside this conversation. When the token authorizes one workspace, call this directly — no workspace call is needed first. When it authorizes several, this read will not guess which one you mean: pass `workspace_id` on the call.