This is a paid bot, and its usage will be counted toward your plan's credits limit. For more information about credit usage, refer to this article.
How the Invoke UiPath process on document completion bot works
Trigger UiPath automation processes when altaFlow documents are completed. The bot connects to your UiPath Orchestrator, kicks off a chosen process, and passes document field data as arguments — perfect for downstream RPA workflows in accounting, HR, or customer onboarding. Be sure to set up the UiPath process you need to initiate in advance.
Use case example: You collect customer data via altaFlow forms and need to transfer it into a legacy desktop system. Once a customer completes the document, the bot starts your UiPath process, which automatically enters the collected data into your desktop application — no manual copy-paste.
How to set up
When the bot works by default:
The bot activates after documents in a workflow have been completed by the step after which the bot is set. To add the bot to your workflow, click the plus icon.
Then, select Bot from the list.
Search for the Invoke UiPath process on document completion bot. Then, install the bot to your workflow by clicking the corresponding button.
Connection settings
To connect the bot to your UiPath organization, select Connect in the Connection settings section.
Then, select a UiPath account to connect.
You can also connect a new account by clicking Add new connection.
The Additional settings for UiPath window will open. Enter the UiPath Tenant URL, app ID, and app secret (see the article on how to generate these credentials). Save your settings by clicking Apply.
Once connected, select Continue to proceed.
In the UiPath process settings section, select the UiPath folder where the process you need to initiate is stored. Then, select the UiPath process from the list.
To locate the list of available UiPath folders, navigate to the UiPath app. Then, switch to the Orchestrator tab. You'll see the folders in the left sidebar.
Next, connect UiPath process arguments to the document fields that the data will be taken from. You can enter a custom value manually if the information is static, or use a data variable if you want to use the data from the completed documents.
Once set up, select Continue to proceed.
Conditions
Set conditions to invoke UiPath processes only in specific scenarios. Common use cases include:
Environment routing: Trigger a UiPath sandbox process when a "Test mode" field is set, or the production process otherwise — safe for QA and staged deployments.
Approved documents only: Kick off the RPA process only when a "Status" field equals "Approved" — avoids running expensive automations on drafts or declined documents.
Region-based processes: Invoke different UiPath processes based on the country field — one for EMEA compliance flow, another for US.
Threshold filtering: Only invoke UiPath for high-priority tickets (e.g., "SLA level" equals "Critical") to avoid overloading your robot pool.
Learn more about bot conditions usage in the dedicated bot execution conditions article.
Advanced settings
Fine-tune how the bot invokes UiPath processes:
Run frequency: The bot fires once per workflow completion by default. Enable per-revision if downstream RPA needs updates on every document iteration.
Failure handling: If UiPath Orchestrator is unreachable or the process is disabled, choose whether to skip silently or halt the altaFlow workflow for admin review.
Document tags: Tag documents that triggered a UiPath process (e.g., "uipath-invoked") for audit trails — critical when reconciling altaFlow signings with RPA logs.
Learn more about adjusting Advanced settings in the bot setup glossary.