- Getting started
- Notifications
- Licensing
- Troubleshooting
- Connector Builder
- Act! 365
- ActiveCampaign
- Active Directory - Preview
- Adobe Acrobat Sign
- Adobe PDF Services
- Amazon Bedrock
- Amazon Connect
- Amazon Polly
- Amazon SES
- Amazon Transcribe
- Amazon Web Services
- Anthropic Claude
- Asana
- AWeber
- Azure AI Document Intelligence
- Azure Maps
- BambooHR
- Box
- Brevo
- Calendly
- Campaign Monitor
- Cisco Webex Teams
- Citrix Hypervisor
- Citrix ShareFile
- Clearbit
- Confluence Cloud
- Constant Contact
- Coupa
- Customer.io
- Datadog
- Deputy
- Discord
- DocuSign
- Drip
- Dropbox
- Dropbox Business
- Egnyte
- Epic FHIR R4 - Preview
- Eventbrite
- Exchangerates
- Exchange Server - Preview
- Expensify
- Facebook
- Freshbooks
- Freshdesk
- Freshservice
- GetResponse
- GitHub
- Gmail
- Google Cloud Platform
- Google Docs
- Google Drive
- Google Maps
- Google Sheets
- Google Speech-to-Text
- Google Text-to-Speech
- Google Tasks - Preview
- Google Vertex
- Google Vision - Preview
- Google Workspace - Preview
- GoToWebinar
- Greenhouse
- Hootsuite
- HTTP Webhook - Preview
- Hubspot CRM
- HubSpot Marketing
- HyperV - Preview
- iContact
- Insightly CRM
- Intercom
- Jira
- Keap
- Klaviyo
- LinkedIn
- Mailchimp
- Mailgun
- Mailjet
- MailerLite
- Marketo
- Microsoft 365
- Microsoft Azure
- Microsoft Azure Active Directory
- Microsoft Azure OpenAI
- Microsoft Dynamics 365 CRM
- Microsoft OneDrive & Sharepoint
- Microsoft Outlook 365
- Microsoft Sentiment
- Microsoft Teams
- Microsoft Translator
- Microsoft Vision
- Miro
- NetIQ eDirectory
- Okta
- OpenAI
- Oracle Eloqua
- Oracle NetSuite
- PagerDuty
- PayPal
- PDFMonkey
- Pinecone
- Pipedrive
- QuickBooksOnline
- Quip
- Salesforce
- Salesforce Marketing Cloud
- SAP BAPI - Preview
- SAP Cloud for Customer
- SAP Concur
- SendGrid
- ServiceNow
- Shopify
- Slack
- SmartRecruiters
- Smartsheet
- Snowflake
- Stripe
- Sugar Enterprise
- Sugar Professional
- Sugar Sell
- Sugar Serve
- System Center - Preview
- TangoCard
- Todoist
- Trello
- Twilio
- UiPath GenAI Activities
- X (formerly Twitter)
- Xero
- watsonx.ai
- WhatsApp Business
- WooCommerce
- Workable
- Workday
- Workday REST - Preview
- VMware ESXi vSphere
- YouTube
- Zendesk
- Zoho Campaigns
- Zoho Desk
- Zoho Mail
- Zoom
- ZoomInfo
Triggers
Triggers provide a uniform mechanism for subscribing to events from the Connector platforms. It gives you the flexibility to automatically start automations or processes in Orchestrator.
Before you can configure triggers, make sure the following conditions are met:
- The Integration Service is enabled and provisioned for your tenant.
- The Triggers tab is displayed in the Integrations window.
- You have already setup an Unattended or Non-production Robot in your Orchestrator instance.
-
You are using modern folders (processes inside of classical folders are not visible when defining triggers).
Note:Triggers are only supported in Modern folders. Classic folders do not support the modern user identity paradigm, therefore cannot support connections in general, or triggers.
Create your process in UiPath® Studio as you would normally do. Using Integration Service, any automation can be triggered for any process.
To receive the details of a record, you can also follow the indications below:
-
If you want to know the actual Connector, Event, Record Type or Record that triggered the process in your workflow, you can define the following input arguments of type
String
in your process.Integration Service will populate them automatically when it starts the job.
- UiPathEventConnector
- UiPathEvent
- UiPathEventObjectType
- UiPathEventObjectId
Note: Find out more about how Arguments work and how to manage them here.
- To retrieve and work with a record that has a trigger on a job run, use the UiPathEventObjectId input argument to retrieve the record from the source system.
Here is an example of how the input argument values are passed by Integration Service.
Publish your process to Orchestrator to as you would normally do. You can publish it to a shared folder or a personal workspace. Make sure to create a process out of your package.
To add a trigger, take the following steps:
- Access Automation CloudTM.
- On the left-side menu, click on Integration Service. The Integration Service window includes three separate tabs: Connectors, Connections, and Triggers.
- Access the Triggers tab and click on the Add Trigger button.
- Select the desired Connector and Connection from their respective dropdown menus. If there is only one connection configured for that particular connector, it will be selected automatically.
-
Select the desired Event and Record from their respective dropdown menus.
Note: Event types may vary with the connector. - On the right, select the Process to execute.
-
Select the Runtime license (the runtime used to execute the jobs that are launched by the trigger) from the drop-down. Available options: NonProduction, Unattended, Headless, TestAutomation, AutomationCloud, Serverless, Development.
- The list of runtimes shown is based on the response received from Orchestrator, i.e. the “assigned” runtime licenses to that folder. For the selected runtime, a message indicates the number of runtimes assigned.
- For more information, see Managing Triggers in Orchestrator and Runtimes (robot licenses) documentation.
- Click the Add Trigger button to create your trigger and activate it.
Alternatively, you can create a new trigger from the Connections tab. To do that:
- Click on a connection's More Actions button.
- Select the Add trigger option.
- Select the desired Event and Record Type from their respective dropdown menus. In this case, the Connector and Connection are already selected and cannot be changed.
- On the right, select the Process to execute and the respective Runtime license.
-
Click the Add Trigger button to create your trigger and activate it.
Note:Event monitoring is currently set to poll every 5 minutes. As such, it could take up to 5 minutes before the associated process starts.
You can see a job's details under the Jobs tab in your Orchestrator Folder. A job started from Integration Service will show its source as Integration Trigger.
Connectors support events through a Polling mechanism. This is supported for the majority of the connector catalog.
Integration Service supports the following two types of events:
-
Generic, which represent typical Create, Update, and Delete operations. When you select a generic event, you must also define the event record to monitor. For example, New Record Created for Calendar record.
-
Predefined, which represent specific actions on specific objects. For example, Calendar event is created.
More information on events is available on each connector's page.
When you define an event for your trigger, you can add more specific filtering.
With Data filters, you can configure triggers that match specific data patterns. This means fewer launches of your robot and not having to apply additional filtering within your automation.
When you create a new connection and set up an event trigger on that connection, the polling interval is set by default to five minutes.
You can customize this interval using the Adjustable Polling Interval feature, which allows you to choose the interval on which event triggers check for new object events.
Polling runs on the connection at the selected interval. Once data has been retrieved, all active triggers for that connection are applied to the data set. If a poll is running when you change the interval, the service waits for the existing poll to finish, then starts another one.
You can change your polling interval either from a specific connector’s page or from the Connections tab.
- In Automation CloudTM, access Integration Service.
- Go to the Connectors page and select a connector.
- In the connector’s page, select a connection to open the connection details page.
-
Click on the interval found under the connection name, as follows. The polling interval is displayed only for connections with added triggers.
Alternatively, you can configure your polling interval from the Connections tab:
- In Automation CloudTM, access Integration Service.
- Go to the Connections tab.
- Select a specific connection to open the connection etails page.
- Click on the interval found under the connection name.
- The Update polling interval window is displayed.
-
You can choose one of the available options or set up a Custom interval, in minutes or hours. The polling interval must be more than one minute and not longer than 24 hours or 1440 minutes.
The following error message warns you if you enter an incorrect value: "The polling interval must be a natural number from 1 to 1440 minutes or 24 hrs."
- Select Update Interval.
You can view a trigger's run history by simply clicking on it in the Triggers tab. In the new page, the Attempts' history is displayed in the lower part of the interface.
This history shows events that were received by the Integration Service and whether the process was successfully launched, in which case it shows the word Successful in the State column.
To check if a job was successfully executed, click the View job logs button. It will redirect you to Orchestrator, where all the necessary information on job execution is displayed.
Go to the Triggers tab in the Integration Service window. Click the More Actions button corresponding to your trigger and select Delete.
To activate or deactivate a trigger, you will first have to click on it to view its details. Then click the switch located in the upper-left side of the window.
A trigger is disabled and set to error state if you are not able to start the job after 11 attempts (~34 hours) for a single event or if the job does not start for the last 100 events.
The 10 retries for every event are done with an exponential back-off strategy. Each subsequent retry attempt comes after a delay twice as long as the previous attempt.
Follow the steps below to rename a trigger:
- Access the Triggers tab.
-
Hover with the mouse cursor over the name of the trigger you wish to modify and you should now see the Edit button displayed.
Note: Alternatively, you can select your trigger from the list to access the detailed view. The Edit button is located on the right side of your trigger name. - Click the Edit button and you can choose a new name for your trigger.