Systems and methods for asynchronous multi-threaded robotic process automation
Abstract
Systems and methods of robotic process automation including: receiving a multi-threaded task request from a messaging application; automatically dividing the multi-threaded task request into a plurality of subtasks based on metadata associated with the multi-threaded task requests; generating a queue comprising one or more subtasks from the plurality of subtasks; identifying an application programming interface associated with the one or more subtasks from the queue; routing the one or more subtasks to the application programming interface; receiving a response from the application programming interface associated with executing the one or more subtasks; and providing the response to the messaging application.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A method of asynchronous multi-threading comprising:
receiving a multi-threaded task request from a messaging application; dividing the multi-threaded task request into a plurality of subtasks based on metadata associated with the multi-threaded task requests; generating a queue comprising one or more subtasks from the plurality of subtasks; identifying an application programming interface associated with the one or more subtasks from the queue; routing the one or more subtasks to the application programming interface; receiving a response from the application programming interface associated with executing the one or more subtasks; and providing the response to the messaging application.
2 . The method of claim 1 , further comprising:
converting the multi-threaded task request into a text format.
3 . The method of claim 1 , further comprising:
polling the messaging application for an additional multi-threaded task request.
4 . The method of claim 1 , wherein the plurality of subtasks include one or more of: gathering user data, editing forms with the user data, generating a document, verifying identity of a user, creating user data, generating a profile based on the user data, updating user data, and deleting user data.
5 . The method of claim 1 , wherein the response includes information associated with an error in execution of one or more subtasks.
6 . The method of claim 1 , further comprising:
receiving a request from the messaging application to execute a failed subtask.
7 . A system comprising:
one or more processors configured to:
receive a multi-threaded task request from a messaging application;
divide the multi-threaded task request into a plurality of subtasks based on metadata associated with the multi-threaded task requests;
generate a queue comprising one or more subtasks from the plurality of subtasks;
identify an application programming interface associated with the one or more subtasks from the queue;
route the one or more subtasks to the application programming interface;
receive a response from the application programming interface associated with executing the one or more subtasks; and
provide the response to the messaging application.
8 . The system of claim 7 wherein the one or more processors are further configured to:
convert the multi-threaded task request to a text format.
9 . The system of claim 7 , wherein the one or more processors are further configured to:
poll the messaging application for an additional multi-threaded task request.
10 . The system of claim 7 , wherein the plurality of subtasks include one or more of: gathering user data, editing forms with the user data, generating a document, verifying identity of a user, creating user data, generating a profile based on the user data, updating user data, and deleting user data.
11 . The system of claim 7 , wherein the response includes information associated with an error in execution of one or more subtasks.
12 . The system of claim 7 , wherein the one or more processors are further configured to:
receive a request from the messaging application to execute a failed subtask.
13 . The system of claim 7 , wherein the one or more processors receive the multi-threaded task request from the messaging application using one or more of: a publish-subscribe model of communication or by streaming.
14 . A non-transitory computer readable medium comprising instructions that when executed by one or more processors cause the one or more processors to:
receive a multi-threaded task request from a messaging application; divide the multi-threaded task request into a plurality of subtasks based on metadata associated with the multi-threaded task requests; generate a queue comprising one or more subtasks from the plurality of subtasks; identify an application programming interface associated with the one or more subtasks from the queue; route the one or more subtasks to the application programming interface; receive a response associated with executing the one or more subtasks from the application programming interface; and provide the response to the messaging application.
15 . The non-transitory computer readable medium of claim 14 , comprising further instructions that when executed by one or more processors cause the one or more processors to:
convert the multi-threaded task request into a text format.
16 . The non-transitory computer readable medium of claim 14 comprising further instructions that when executed by one or more processors cause the one or more processors to:
poll the messaging application for an additional multi-threaded task request.
17 . The non-transitory computer readable medium of claim 14 , wherein the plurality of subtasks include one or more of: gathering user data, editing forms with the user data, generating a document, verifying identity of a user, creating user data, generating a profile based on the user data, updating user data, and deleting user data.
18 . The non-transitory computer readable medium of claim 14 , wherein the response includes information associated with an error in execution of one or more subtasks.
19 . The non-transitory computer readable medium of claim 14 comprising further instructions that when executed by one or more processors cause the one or more processors to:
receive a request from the messaging application to execute a failed subtask.
20 . The non-transitory computer readable medium of claim 14 , wherein the multi-threaded task request from the messaging application is received using one or more of: a publish-subscribe model of communication or by streaming.Join the waitlist — get patent alerts
Track US2025291627A1 — get alerts on status changes and closely related new filings.
We store only your email — no account needed. See our privacy policy.