The agent checks the sender against a table of known senders, saves the file under a fixed name and hands it on. Mail it cannot place goes to a person with the reason.
The ERP keeps the ledger. Everything else keeps the work.
Across our catalog of 1,554 processes, 83 different companion systems show up, and every process touches at least five of them beside its ERP.
- 1,554
- processes
- 83
- companion systems
- 5 or more
- per process
- 9
- families
Nine families at a glance
| Family | Examples | What the agent does |
|---|---|---|
| Microsoft 365 | Outlook, Excel, SharePoint, Teams | Saves attachments, ties workbooks to the ERP, posts exceptions |
| Banks, payments and tax | Banking, tax, lockbox, payment portals | Downloads activity, uploads files, stops for the approver |
| Reporting and IT | BI, identity, ticketing, middleware | Refreshes reports, finds stale access, fixes dropped records |
| Construction platforms | Procore, ACC, Bluebeam, P6, DocuSign | Files logs and RFIs, exports markups, checks envelopes |
| Outside portals | Supplier, customer, carrier, vendor, insurance | Reads releases and dates, uploads notices, pulls proof of delivery |
| Government | Certified payroll, HUD, permits | Uploads after sign-off, reads every error file |
| People systems | HRIS, time, payroll, LMS | Compares records, flags missing punches, tracks lapsed training |
| Plant floor | MES, barcode, QMS, CAD/PLM, CMMS | Matches scans and completions to jobs, checks revisions |
| Sales, leasing and residents | CRM, SMS, listing sites, portals | Logs leads, updates listings, sends approved texts |
Microsoft 365: where work starts and ends
Every process touches Outlook, Excel and a shared drive. On Google Workspace, read those as Gmail, Sheets and Drive; the agent works either through the screen.
Spreadsheets
It reads only the cells it was shown, checks formulas still point where they did, and never pastes over a total.
Teams
It posts exception lists and collects answers. A chat reply is not an approval unless a written rule says so.
Bank and tax portals: built to distrust software
Each bank login belongs to a named person, usually with a token or second factor. The agent works in the session the treasury analyst opened, prepares and uploads the file, and stops. The approver approves. A changed vendor bank account always sends the payment to a person. More on Human review.
Portals you do not own
Customer release sites, carrier tracking pages, a general contractor's Procore or Textura, a vendor's dispatch app. The other company owns the portal, its login and its change calendar, and none of them asked your ERP vendor for an integration.
When a portal redesigns a page, the agent retrains one map for that portal and every workflow picks it up.
- Agent Signing in
- Their portal Reading a record
- Your ERP Writing it back
The API belongs to the buyer
In Procore or Autodesk, only the account owner can install an app. A subcontractor's integration has no door.
The login belongs to a person
Some state portals disable accounts after 30 days idle.
A second factor guards the door
Pay-app and government portals send codes by text, email or app.
What an agent does inside any portal
-
Open the portal in the user's own browser profile, already signed in, or with a credential from the encrypted vault.
-
At a one-time code prompt, pause and ask the named person. Codes are never stored.
-
Read the portal's totals back and compare them to the ERP to the cent.
-
Confirm each upload rendered, submit only after any required review, and save the confirmation.
Every action leaves before and after screenshots. Credentials and codes are never logged.
Which ones first?
Start where the count is high and the login is yours.
-
Inbox to folder: every attachment saved, named and logged.
-
Folder to ERP: the document read and posted, with rules deciding any amount.
-
ERP to workbook: the tie-out rebuilt and checked to the cent.
-
ERP to portal: one outside portal, with the owner's written consent where its terms require it.
Questions
Can an agent get past MFA on a government portal?
No, and it should not try. It pauses and asks the named user for the code, so those runs happen when that person is at a desk.
What should I ask a general contractor before automating its pay-app portal?
Whether its terms allow automated entry by an invited user, whether it will issue a separate login for an agent, and which second factor it uses.
Why not share one portal login across the team?
The portal's audit trail names one person, and lockout rules punish shared use. Use one login per person and a separate one for the agent where allowed.
What happens when a portal changes its layout overnight?
The agent finds each target again from the screen. If it cannot, it routes to a person or stops. It never guesses.
No prompts. No babysitting. No Integrations.