Trigger is the starting point of every automation. It looks for a specific event or a condition to happen, and launches the automation flow when it occurs. The automation can be run manually, based on the schedule or the event. There is a trigger type for each case.
Webhook triggers are not available in the early beta. You will be able to use them in the upcoming releases.
Skyvia provides Manual, Connection, Run on Schedule, and Webhook trigger types. Choose one of them to define what type of event triggers the automation.
Choose Manual to start automation on demand by pressing Run on the automation management pane.
Run on Schedule
Сhoose Run on Schedule to set a schedule for the automation runs or create a delayed run.
|Includes two options: One-Time and Recurring, to either set a delayed start or create a schedule
|Defines the frequency of the automation runs.
|Defines the time of the day to run the automation.
|Defines the starting date of the schedule.
|Required Parameter. Defines the time zone to line up with a schedule.
Connection trigger is set up to monitor a specific event or condition in the chosen data source. When the event occurs, trigger detects it and creates a queued execution. If there is no active execution, it starts the automation. You can check and modify the queue and status of executions on the monitor tab.
Connection triggers are connector-specific, trigger availability depends on the chosen connection.
Connection Trigger Types
Currently, only the Polling Trigger type is available in Connection triggers. Polling triggers check the data source for events according to the time interval specified in the Polling Interval setting. For example, the New Record trigger below checks the Account object for new records every 30 minutes and compares the start date of the check with the record’s CreatedDate value. If it finds a record that appeared since the last check, Skyvia creates a queued execution for each new record and adds it to the end of the queue. If there are no active executions, Skyvia runs the Automation. If there is an active execution, newly added executions will run according to their position in the queue. You will get the values of the selected columns in the Trigger payload.
When the check starts, Skyvia creates a current check timestamp, looks for the updates since the last check, and makes the current check timestamp a starting point for the future checks. When you disable the automation, polling trigger stops checking for the events. Next time you enable the automation it starts checking from either the last check date or the last event found depending on the Connector used in your automation.
Connection Trigger Settings
Trigger settings differ from trigger to trigger, while also depending on the chosen Connector. For example, New Record trigger will have a different set of settings for SQL Server and Salesforce connections.
Each polling trigger has a polling interval setting that determines the time interval between the event checks. Note, that the less the interval is, the more API calls will be involved.
Each trigger can have its payload generated by the event. To return field values to the automation scope, select them from the columns dropdown. In the example below ID, Name, and Rating values will be added to the automation scope. You can check the payload in the Tigger’s output.