Fit guide · workflow automation
Workflow automation without APIs: when browser, desktop, Citrix, and files all matter.
Many operational workflows are not API-shaped. They move from a browser portal to a spreadsheet, into a desktop application, through Citrix, and back to a system of record. The right approach is not to pretend every handoff is an integration. It is to use the strongest connection available at each step, keep the path reviewable, and stop when a check fails.
Short answer: APIs are preferred when they are reliable and expose the needed action. UI, desktop, Citrix, and file steps are reasonable when that is where the real work happens and the result can be verified.
The decision
Choose the connection by the work, not by the diagram.
Use an API when
- the required data or action is exposed;
- authentication and permissions are dependable;
- the response gives a clear success or failure state; and
- the API is more reliable than reproducing the user path.
Use browser, desktop, or Citrix when
- the team already completes the work through a visible interface;
- the system has no suitable API or the API misses the needed step;
- the path includes files, approvals, or legacy software; and
- the intended result can be checked after the action.
Do not automate yet when
- the “right” result depends on undocumented judgment;
- the interface changes without a detectable signal;
- there is no safe pause before a consequential change; or
- the team cannot define what completion means.
The operating model
One reviewed path across every system.
Record the real work
Start with one representative case from input to verified result. Capture the tools, handoffs, checks, and exceptions that a process document usually leaves out.
Review the boundaries
Inspect the drafted steps. Keep approval, judgment, and sensitive actions with a person. Define what should happen when a record, file, or screen does not match expectations.
Run only the eligible cases
Start from the UI, a schedule, or an event. Return completed results with evidence, and return exceptions with the context needed to resolve them.
The measurement
Measure the work returned, not just the run completed.
A fast run is not automatically a valuable run. Establish the manual baseline, then measure whether eligible cases complete without teammate handling and how much exception review remains.
Runtime, completion rate, review time, and cost per completed case should be reported separately. The workload examples on the main page are illustrative, not customer results.
The boundary
No-API does not mean no controls.
- Human approval: pause before consequential changes that need judgment.
- Observable completion: define the evidence that proves the intended result.
- Exception return: stop uncertain cases instead of guessing through a changed screen.
- Controlled pilot: increase volume only after completion, runtime, and cost meet the agreed bar.
Questions
Common no-API workflow questions.
Can workflow automation work without an API?
Yes, when the workflow has a stable visible path through a browser, desktop application, Citrix session, or file-based system and a result the team can verify. An API is useful where it is reliable, but it is not required for every step.
When should a team use UI automation instead of an API?
Use the UI when the real work lives in a portal, installed application, Citrix session, or file that has no suitable API. Prefer an API when it exposes the needed data or action reliably and with better controls.
Is desktop or Citrix automation safe for consequential work?
It needs a reviewed path, an observable success condition, and a human approval point before consequential changes. If the workflow cannot confirm the intended result, that case should stop and return its context.
What should a no-API automation pilot measure?
Measure the manual baseline, eligible cases, verified completions without teammate handling, exception review time, runtime, and cost per completed case. Report team hours returned separately from elapsed runtime.
Apply the guide
Bring the workflow that keeps crossing the gap.
In 30 minutes, map the real tools, handoffs, checks, exceptions, and pilot fit. No process document required.