I know this is very new and was just released here recently. But the banner being displayed in Orchestrator has a pretty short time frame list May 5 to July 31st 2025.
I am unsure how to migrate and existing integration service trigger to the new API triggers section.
I have a trigger configured using a custom connector and a get request I put together in connector builder. The get request looks for newly added items to a sharepoint list and will trigger based on certain results being provided.
How do I transfer this from Integration service to the API Triggers section in Orchestrator?
go to orchestrator, navigate to api triggers, create a new api trigger using your connector, define the event conditions similar to your current get request, link the trigger to the desired process, and test it to ensure it works as expected.
If you found helpful please mark as a solution tick.
Happy Automation with UiPath
You can implement an event trigger on your process in Cloud Orchestrator and can configure the Microsoft OneDrive and SharePoint connector this connector supports the following pre-defined events.
Hey @david.rya.goderre1 To migrate your Integration Service trigger to the new API Triggers in UiPath Orchestrator, create a new API trigger in the Triggers section, configure it with the GET request pointing to your SharePoint API endpoint, set up authentication and conditions (e.g., new items), and link the trigger to your existing process. Finally, test it to ensure it fires correctly and adjust settings like polling frequency as needed.
Thanks for the info! I was actually unable to configure the ootb sharepoint integration connector and instead created my own using the connector builder. I didnt have all the permissions thats were required by the UiPath ootb sharepoint conenctor.
I guess my confusion stems from how to actually configure the trigger properly. You mentioned setting up authentication and conditions, but this is all already configured in integration service under the custom connector. And it handles the bearer token and reauthentication process.
Additionally there are no fields in the create api trigger for auth tokens etc.
Is there a guide on this setup? Again i know this is new so if there isnt I understand, but just trying to get a handle on this as it impacts one of our automations
Next, in regards to authentication, the recommendation is to set up a PAT Token. End result should look something like the following (I highlighted the minimal job scopes I gave my PAT token):
In short, API triggers are tied to the api call generated/the slug url you specify when creating the trigger and not IS connections specifically. Please let me know if this helps!
So this has helped explain it to me and the way it is configured. But I guess now I am not sure that i can create the trigger in Orchestrator, the way i have it created in Integration Service.
In Integration service i have a custom connector which connects to our sharepoint tenant (I used a custom one because UiPath requires permissions that i was not allowed to get approved at our company). I then created a get request to our Sharepoint site where we check for new items to be added to a sharepoint list. I then have a trigger built in Integration service that triggers a job process to start when there are new items. This trigger runs the get request every minute, and if it sees new items, it triggers the job, if not it does nothing.
Based on your explanation above, i would need to configure a webhook inside sharepoint with the PAT to trigger the job when a new item is added, do i have that correct? If so then this is a completely different way of triggering jobs. one is using UiPath and APIs to check on a polling interval, the other is UiPath waiting to be called from the 3rd party service
Correct. IS trigger can be set up to monitor your Sharepoint site and fire off a job by itself. While API Trigger can be set up to fire off a job, to trigger the job you will always need a third party service to make its API call.
If your struggle refers to the recent announcement about having the ability to create disconnected event triggers in Orchestrator, then you should not look at API triggers. You should go to Event Triggers and recreate the Integration Services triggers there, using your existing connections.
If instead you want sharepoint to call UiPath to start a job, then API triggers are for that.
Ahhhhh this is exactly what I was looking for. I apologize if my confusion made this more difficult. I appreciate your help in pointing me to the correct location in Orchestrator to recreate my IS trigger.
I have created my trigger in the Event Triggers section. It is running as expected.
