All applications583

Find your application

583 applications

Open full catalog

Browse applications by category or open the full catalog.

RPA Task Manager · Available now

Keep every bot revision and run accountable.

RPA Task Manager organizes bot definitions by organization and automation queue. An Automation Operator owns a dated definition and its revision.

  • No per-user fees
  • Manual work is free
  • Configure it in Proto
OverviewScheduled bot definitions
RPA Task Manager · Bot definitions

Scheduled bot definitions

Bot definitions in one list

New bot definition
Bot definitions in view
6
Validated
3
Scheduled
3
Validated3
Invoice intake and validationBank reconciliation overnight queue
940
18 Oct
Supplier master update reviewBank reconciliation overnight queue
340
19 Oct
Customer statement deliveryCollections weekday queue
230
22 Oct
Add
Scheduled3
Daily bank file reconciliationExpense processing queue
840
03 Nov
Order exception routingCollections weekday queue
200
18 Oct
Expense receipt extractionCollections weekday queue
540
17 Oct
Add
Invoice intake and validationBot definitions · BD-52517
Validated
Scheduled date18 Oct
Revision940
OwnerHyejin Park
DefinitionBank reconciliation overnight queue
Review the revisionBD-52517 · Invoice intake and validation

Bot Reviewer decides whether the scheduled revision is Approved, Returned or Rejected.

Waiting for Bot Reviewer
ApproveReturn
Example screen with sample data
Tables, ready to use
14
Saved views
12
Roles with set permissions
6
Reports and dashboards
8
Features

See each bot's next action

Every feature works on the same records. Pick one to see the screen your team works in.

Queue and organization setup

Define the organization, queue policy and source mapping before scheduling bot work.

  • Organization
  • Queue policy
  • Mapping
  • Organizations
  • Automation queues
  • Source mappings
  • People
  • Bot definitions
Explore queue and organization setup
OverviewQueue policy register
RPA Task Manager · Queue and organization setup

Queue policy register

Automation queues

New
NameCodePolicy referenceEffective fromEffective toActive
Accounts payable morning queueAP-MORNINGAP control policy, revision 421 Oct24 Oct
Bank reconciliation overnight queueBANK-OVERNIGHTCash matching policy, revision 220 Oct27 Oct
Supplier change approval queueSUPPLIER-REVIEWSupplier approval policy, revision 323 Oct27 Oct
Order exceptions priority queueORDER-PRIORITYOrder exception policy, revision 519 Oct21 Oct
Customer billing evening queueBILLING-EVENINGBilling delivery policy, revision 214 Oct21 Oct
6 of 6 records
Accounts payable morning queueAutomation queues · AQ-94358
CodeAP-MORNING
Policy referenceAP control policy, revision 4
Effective from21 Oct
Effective to24 Oct
OrganizationCrestline Procurement
Example screen with sample data
Process

Follow a bot from plan to result

Bot definition to reviewed run ships ready to use. One step needs a named approval before the work moves on: Review the revision (Bot Reviewer).

Drag a card to another stage, or focus it and use the arrow keys. It updates to match the stage.

  1. Define the bot

    Assign an organization, queue, owner and scheduled date to the definition.

    Invoice intake and validationBD-52517 · Automation Operator
    Define the botBy Automation Operator
  2. Validate the revision

    Check the intended input and queue policy for this version.

    Invoice intake and validationBD-52517 · Automation Operator
    Validate the revisionBy Automation Operator
  3. Schedule the bot

    Record a durable schedule trace and raise a pending review decision.

    Invoice intake and validationBD-52517 · Automation Operator
    Schedule the botBy Automation Operator
  4. Review the revision

    Have an independent reviewer decide on the scheduled version.

    Invoice intake and validationBD-52517 · Bot Reviewer
    Review the revisionBy Bot Reviewer
    ApprovalBot Reviewer decides whether the scheduled revision is Approved, Returned or Rejected.
  5. Execute the run

    Claim the eligible run and record the attempt and observed result.

    Invoice intake and validationBD-52517 · Automation Operator
    Execute the runBy Automation Operator
  6. Reconcile and correct

    Confirm receipts, assign exceptions and preserve corrections.

    Invoice intake and validationBD-52517 · Exception Coordinator
    Reconcile and correctBy Exception Coordinator
Inside a record

Connect the provider and source

Open any bot definition to see its bot runs, the roles that work on it, its process stages and its approvals on one page.

  1. 1
    Record details

    Scheduled date, Revision, Owner and Definition.

  2. 2
    Bot runs

    Each line is linked to this bot definition.

  3. 3
    Who works on it

    Automation Operator, Bot Reviewer and Queue Administrator, each with their own permissions.

  4. 4
    Process stages

    Define the bot, with the role that acts.

  5. 5
    Approvals

    Review the revision, with who decides.

Scheduled bot definitionsInvoice intake and validation
RPA Task Manager · Bot definitions

Invoice intake and validation

Bank reconciliation overnight queue · Validated

Log activity
1
Record details
Scheduled date18 Oct
Revision940
OwnerHyejin Park
DefinitionBank reconciliation overnight queue
2
Bot runs

Invoice intake and validation

ParentSequenceObserved on
Supplier master update review2017 Oct
Inventory variance digest2003 Nov
Overdue invoice reminder3012 Oct
Bot runs
6
Total sequence
240
3

Who works on it

  • Automation OperatorManage bot definitions, execution attempts, bot runs
  • Bot ReviewerManage review decisions, evidence documents
  • Queue AdministratorManage Organizations, automation queues, source mappings, People
4

Process stages

  • Define the botAutomation Operator
5

Approvals

  • Review the revisionBot Reviewer
    Approved
Example screen with sample data
Approvals

Review the exact revision

OverviewApprovals
RPA Task Manager · Overview

Approvals

Signed in as Bot Reviewer

Waiting for you

4 To review1 Overdue2 Decided todayOnly mine
0 selectedApproveReturn
  • AQ-94358Accounts payable morning queue
    AP-MORNINGRequested by Automation Operator
    Waiting1dActions
  • AQ-60585Bank reconciliation overnight queue
    BANK-OVERNIGHTRequested by Automation Operator
    Waiting3dActions
  • AQ-97504Supplier change approval queue
    SUPPLIER-REVIEWRequested by Automation Operator
    Waiting3dActions
  • AQ-99177Order exceptions priority queue
    ORDER-PRIORITYRequested by Automation Operator
    Waiting6dActions

Who approves what

DecisionApprover
Review the revisionHave an independent reviewer decide on the scheduled version.Bot Reviewer
1 approval rule · set per role in Proto
Example screen with sample data
Roles

A workspace for each role

Everyone opens RPA Task Manager to the work that is theirs. Pick a role to see what it starts with.

Automation Operator

Owns bot definitions, schedules eligible revisions and follows execution results.

This is the first screen this role sees.

OverviewScheduled bot definitions

Scheduled bot definitions

Bot definitions · Automation Operator

Validated3
Invoice intake and validationBank reconciliation overnight queue
940
18 Oct
Supplier master update reviewBank reconciliation overnight queue
340
19 Oct
Customer statement deliveryCollections weekday queue
230
22 Oct
Add
Scheduled3
Daily bank file reconciliationExpense processing queue
840
03 Nov
Order exception routingCollections weekday queue
200
18 Oct
Expense receipt extractionCollections weekday queue
540
17 Oct
Add
Example screen with sample data
Reports

Read volume and turnaround

Read bot volume, turnaround, review decisions and exception work from traceable records.

Overview
RPA Task Manager · Overview

RPA Task Manager dashboard

This quarter

Execution attempts in view
6
Failed
3
Unknown
3

Bot definitions by status

How far records got this quarter

StageReachedStep
Draft38
Validated1437%
Scheduled429%
Running125%

Revision by status

Sample totals per stage

0
-2000Draft
0Validated
-4000Scheduled
-6000Running
-2000Completed
Example screen with sample data
  1. 01Bot throughput

    Compare completed definitions and observed run results by organization and scheduled date.

  2. 02Attempt outcomes

    Group execution attempts by status, bot definition and start date.

  3. 03Run turnaround

    Compare operation start and completion dates by result status.

  4. 04Revision review decisions

    Show decisions by reviewer, revision and decision date.

  5. 05Exception follow-up

    Show open and completed actions by assignee and due date.

  6. 06Queue activity

    Group bot definitions by organization and automation queue.

  7. 07Receipt coverage

    Show operation steps with external receipt IDs and receipt evidence.

  8. 08Observed result outcomes

    Compare accepted, rejected and pending bot results over time.

Controls

Keep receipts with the run

Each stage of bot definition to reviewed run names the role that acts and the status it records, so a change is never anonymous.

OverviewBot definition to reviewed run
RPA Task Manager · Process

Bot definition to reviewed run

Each stage, the role that acts and the status it records

Process stages
9
Approval steps
1
Roles involved
5
Tables touched
11
Validate the revision
Automation Operator
StatusDraft → Validated
Schedule the bot
Automation Operator
StatusValidated → Scheduled
RecordsReview decisions, Operation steps, Operation runs
Execute the run
Automation Operator
StatusScheduled → Running
RecordsExecution attempts, Operation steps, Operation runs
Bot definition to reviewed run
  1. Start
    Validate the revisionDraft → Validated
    Automation Operator
  2. Step
    Schedule the botValidated → Scheduled
    Review decisions
  3. Approval
    Review the revisionBot Reviewer
    Review decisions
  4. Step
    Execute the runScheduled → Running
    Execution attempts
  5. Step
    Confirm the receiptRunning → Succeeded
    Operation runs
Example screen with sample data
AI agent

Ask Proto to trace the work

Ask Proto to help prepare, inspect and explain bot work while people make the decisions.

It can

  • Automation Operator: Find scheduled definitions for a named owner and show their revision, queue and pending review decision.
  • Bot Reviewer: Gather the definition, mapping and evidence for a pending revision decision.
  • Exception Coordinator: Trace an uncertain attempt to its operation key, numbered step and follow-up assignee.
  • Operations Analyst: Explain a turnaround result by opening its definition and operation history.

Stays with a person

  • Proto can help prepare and inspect the records, but a Bot Reviewer makes the independent decision.
  • A provider result needs a confirmed external receipt before the durable operation is recorded as successful.
  • A correction needs a documented reason, preserved original evidence and verification of its successor revision.
Integrations

Connects to the tools you use

Set up connections through ERP.AI and Proto workflows, with every change logged.

  • RPA Task Manager
  • Bot provider
  • Source system
  • Evidence storage
Data model

Your data, in tables you can change

Every record lives in a table you can see, extend and export. Add fields or whole tables in Proto.

Browse all 14 tables
14tables
  • Queue and organization setup5
  • Bot definition planning8
  • Independent review7
  • Execution and attempts7
  • Receipts and provenance6
  • Exceptions and correction9
Implementation

Roll out one team at a time

Start with one team and one process, then add the rest once the basics are running.

  1. Set the scope

    Choose one recurring bot, its owning organization, operator, reviewer and external source.

  2. Prepare the queue

    Record policy reference, effective dates and source mapping; agree on the time zone used for scheduling.

  3. Define and review

    Create a dated definition, validate its revision, schedule it and have a separate reviewer decide.

  4. Execute and inspect

    Trace a claimed run through attempt, observed result, numbered step and confirmed receipt.

  5. Rehearse exceptions

    Investigate an unknown provider result, assign follow-up and test a correction with a successor revision.

Pricing

$0per user

The base account and everyday work in the ERP.AI app are free, for every user.

  • No per-user or per-seat fees
  • Viewing, editing, approving and exporting records in the app is free
  • Pay only for machine work: API calls, imports, workflows and AI agents
  • Prepaid credits from $5. Purchased credits never expire

Pricing details

Machine work rate card Included per $1 of credit

Machine work rate card
UsagePer $1
Record reads (list, filter, get)20,000
Search or aggregate queries4,000
Record writes4,000
Imported or synced records200,000
Workflow runs2,000
AI agent runs2,000
Scheduled jobs or webhooks20,000
File uploads (MB)2,000
CSV or PDF exports100
FAQ

Questions, answered

Scope, rollout and pricing for RPA Task Manager.

All questions
How do I get started?

Click Get started, then use Proto to configure RPA Task Manager for your business. Begin with one organization, one queue and a recurring bot whose external receipt you can inspect.

What does the queue control?

An automation queue carries its organization, policy reference and effective dates. The bot definition points to the queue used for its scheduled revision.

Who approves a scheduled revision?

A separate Bot Reviewer decides on the pending review decision raised by scheduling. The decision stays linked to its source revision.

Can an operator run a scheduled bot immediately?

Execution takes an eligible reviewed definition. The review decision should be Approved for the revision being executed.

How is a provider attempt recorded?

The execution attempt stores an operation key, attempt number, timing, status, provider reference and any failure reason.

What confirms a successful operation?

The execution workflow marks the durable operation Succeeded only when the external receipt is confirmed on the numbered step.

How are uncertain results handled?

The team traces the existing operation key, provider reference and step receipt before deciding on another action. A follow-up can assign the investigation.

Can an executed revision be corrected?

A documented correction preserves the prior revision and completed steps, records compensating output and creates a successor revision for verification.

What can the reports page show?

RPA Task Manager Reports covers operational volume and turnaround. The underlying definitions and operation records explain individual results.

Set up RPA Task Manager your way.

Start free, then use Proto to change fields, steps and approvals before your team goes live.

How to get started

A personal agent for your business

Get started with Proto

Your app is selected. Download Proto, then open it with this context.

Selected appRPA Task Manager

Choose your computer’s platform.

Download Proto

Install Proto, then return to this panel.

Already installed? Open Proto

Free to use. Your own model provider may charge for usage.