JoeGramcQ: Using with Salesforce
One of the RPA use cases I'd be interested in and want to understand how good of it a fit it would be and how challenging it would be to set up is connecting to our Salesforce instance and setting up RPA to help ensure data cleanliness. We use two managed packages on Salesforce as primary applications to run our business. I'm not too concerned with the ability to use it with the managed packages but I envision setting up more traditional RPA use cases around monitoring certain salesforce objects and potentially identifying and cleaning up duplicate accounts, contacts etc and merging them. Improving the data quality and identifying missing fields that should have values entered etc. Would this be a good use case?
The other use case is the challenge we have with uploading and indexing documents in Salesforce.
Faik_Robomotion
Sep 11, 2026A: Hi Joe,
Yes. Robomotion has a native Salesforce RPA package, so for most of this you would work directly through the Salesforce API rather than automating the Salesforce UI. The package supports SOQL queries, SOSL search, object metadata/field discovery, and Create, Get, Update, Delete, and Upsert operations on Salesforce records. This also means it can work with custom objects and objects created by managed packages.
For your data-cleanliness use case, you could schedule a robot to check Accounts, Contacts, or other objects, find missing fields, detect records that match your duplicate criteria, normalize values, enrich missing information from other sources, and update Salesforce automatically. You could also use Salesforce's own duplicate/matching rules and have Robomotion process the results. I would probably start with detection and reporting, then automate corrections once you are comfortable with the rules.
The one exception is merging duplicate records. Detecting duplicates is straightforward, but Salesforce record merging is not exposed through the normal REST operations in our package, so fully automated merging would require a small additional Salesforce-side integration or, alternatively, UI automation. For something destructive like merging, I would normally recommend a review/approval step anyway.
Document uploading and indexing is also a very good fit. A robot can create Salesforce "ContentVersion" records and link the uploaded files to Accounts, Contacts, Cases, or your custom objects. You can then add AI/document-processing steps to classify documents, extract fields or tables, and write that structured information back into Salesforce, so the documents become part of a larger automated process rather than simply files stored in Salesforce.
Best,