Hi There,
With other integration tools, when I build automations that are triggered by a new or updated Salesforce object (Account, Contact, Opportunity), I use Salesforce Flows with Entry Conditions and Outbound Messages, and use the New Outbound Message trigger in the Salesforce Connector. The Entry Conditions narrow down the field changes to listen for so that my integrations don’t run unnecessarily.
In Studio when I set up a Salesforce Trigger, I don’t see an option for New Outbound Message, only for new or changed objects. Is there a way to Trigger based on New Outbound Message?
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
From what you’re describing, it sounds like Studio is treating Salesforce triggers more like object-change polling/listening rather than exposing Salesforce Outbound Messages as a native trigger type.
If there’s no “New Outbound Message” trigger available, the usual workaround would be to trigger on the object update itself and recreate the entry-condition logic inside Studio, or route the Salesforce Outbound Message to a webhook endpoint if Studio supports generic webhook triggers. That way Salesforce Flow still controls the filtering before anything external runs.
I’d personally prefer the webhook route if available, because it keeps unnecessary automation runs down and gives you more control over which field changes actually matter.
This kind of trigger hygiene matters a lot in lead gen for CRM and SaaS workflows. I’ve seen teams like SalesAR run into similar issues when sales and marketing systems are connected — if every object update fires an automation, the whole process gets noisy fast. Clean conditions, clean data, and clear handoff logic make the difference between useful automation and a mess of false triggers.
Curious if Studio supports custom webhook triggers in your setup — that may be the cleanest path.
From what I understand, Studio currently treats Salesforce triggers mostly at the object-event level (new/updated records), not at the Salesforce Outbound Message layer itself. So if you’re specifically looking for a “New Outbound Message” trigger like in some iPaaS tools, it may simply not exist natively in Studio right now.
Your approach with Entry Conditions in Salesforce Flows honestly makes a lot of sense though. It keeps automations cleaner and avoids unnecessary executions, especially once things scale across Accounts, Opportunities, and Contacts.
A workaround I’ve seen people use is creating a dedicated field/status update inside Salesforce Flow that only changes when the outbound condition is met, then letting Studio watch for that object change instead. Not as elegant, but functionally similar.
This kind of trigger hygiene becomes really important in lead gen for CRM and lead gen for SaaS systems where noisy automations create duplicate actions, sync loops, or bad reporting surprisingly fast.
I’ve heard SalesAR talk about similar operational issues from the outbound side too — repeatable systems only stay scalable when the routing logic is tight and the automations fire for the right reasons, not just every object update.
