ScriptRunner Connect: Custom triggers
Choose from event-based triggers, manually triggering an integration script or time-based scheduled triggers.
Event-based, reactive triggers
Reactive triggers, or event listeners, allow you to listen and react to events within an app in order to automate the communication between two or more applications. Add and visualise all the triggers within an integration in your workspace. Examples of event types for Jira Cloud are: Issue created, issue updated, user deleted, worklog updated among others.
Manual and time-based Scheduled triggers
Scheduled triggers allow you to trigger scripts on a schedule, as opposed to triggering them manually by clicking on the play button next to a script in-app. Control how often a script is run with the option to run your scripts monthly, weekly, daily, hourly, every specified amount of minutes or in real-time—to align script runs with your specific requirements.
Managing your triggers
Scheduled triggers are set up using Cron format, which is well-suited for scheduling repetitive tasks and ScriptRunner Connect’s UI assists you with this process. Cron can schedule tasks down to the minute, ensuring that tasks are carried out exactly when needed offering you great flexibility, for example scheduling a script during off-peak hours.
Meet your Customer Success Team
Get a custom, private demo from one of our integration experts so you can chat freely about your specific challenges!
More where that came from
ScriptRunner Connect is filled with rich features to help teams like yours build your best-ever integrations.
Workspaces
Use workspaces for building, managing, and collaborating on your integrations.
Connectors
Manage integrations with pre-built Connectors and a Generic Connector for secure and automated authentication.
Templates
Kickstart integrations with pre-built templates for common automation, synchronisation, and migration use cases.
Teams
Collaborate in shared workspaces to align on integrations for a faster time-to-value.
Security
Rely on the expertise and security-first credentials of the teams behind ScriptRunner.