RPA + API Automation

A critical system had no API. Every day someone logged into a portal, retrieved information, and re-entered it into the systems that did have one.

Make the daily session a scheduled job, use real APIs wherever they exist, and keep the brittle part isolated so it can't take the rest down.

Python RPA scripts drive the portal where no API exists. n8n orchestrates the schedule and the API calls for every system that does have one, and results sync to the destination with logging, retries, and alerts.

• Python automation for the portal, written to fail loudly and retry safely
• n8n orchestration for scheduling, API calls, and routing
• HTTP integrations for the systems with proper APIs
• Logging and alerting so a broken portal login is known within minutes, not days

• Python
• n8n
• APIs
• RPA
• HTTP Requests

The daily manual session became a scheduled job with error alerts, and the person who used to do it no longer needs to.

RPA is the last resort, so isolate it. Wrap it in a boundary with retries and alerts and let the rest of the system stay clean.