Start with one repeatable task
An internal desktop tool may show the data you need without offering a supported integration. A suitable first workflow has a recognisable starting state, a short sequence of actions and a result you can verify.
For example, open a report window, enter a date range, wait for its ready state and select Export. Confirm the expected output before treating the run as complete. This is a workflow pattern to validate in your application, not a prebuilt integration.
Connect visible states to actions
Build the workflow around what the application shows at each decision point.
- Target the right window before entering text.
- Use an image template for a stable button or readiness indicator.
- Use OCR when the content of a visible label or value matters.
- Wait for the expected result and define a timeout or error path.
Check the actual environment
Test display scaling, permissions, window focus and anything that can cover the target. Remote desktop sessions and embedded applications can have additional rendering and session constraints; validate them individually.
If a supported API or accessible application control already solves the task well, consider it first. Visual automation is useful when working through the screen is the practical route. It does not guarantee compatibility with every application or session state.