Triggering Scripts
Scripts can be triggered in 6 ways.
On-demand triggers:
- Auto-generated UIs
- Customized UIs with the App Editor
- Trigger Scripts from Flows
- Schedule the Execution of a Script
- Trigger Scripts from CLI (Command Line Interface)
Triggers from external events:
- Trigger Scripts from Webhooks, including from Slack or Emails
Scripts are sequences of instructions that automates tasks or performs specific operations. In getOperate, they are hosted on workspaces.
On-demand triggers
Auto-generated UIs
getOperate automatically generates user interfaces (UIs) for scripts and flows based on their parameters.
By analyzing the main function parameters, it creates an input specification in the JSON Schema format, which is then used to render the UI. Users do not need to interact with the JSON Schema directly, as getOperate simplifies the process and allows for optional UI customization.
This feature is also usable directly in the script editor to test a script in the making:
Auto-generated UIs
getOperate creates auto-generated user interfaces for scripts and flows based on their parameters.
Customized UIs with the App Editor
getOperate provides a WYSIWYG app editor. It allows you to build your own UI with drag-and-drop components and to connect your data to scripts and flows in minutes.
App Editor
Detailed section on getOperate’s App Editor.
You can also automatically generate a dedicated app to execute your script.
Trigger Scripts from Flows
Flows are basically sequences of scripts that execute one after another or in parallel.
Flow Editor
Detailed section on getOperate’s Flow Editor.
Schedule the Execution of a Script
getOperate allows you to schedule scripts using a user-friendly interface and control panel, similar to cron but with more features.
You can create schedules by specifying a script or flow, its arguments, and a CRON expression to control the execution frequency, ensuring that your tasks run automatically at the desired intervals.
Schedules
Scheduling allows you to define schedules for Scripts and Flows, automatically running them at set frequencies.
CLI (Command Line Interface)
The getOperate CLI allows you to interact with getOperate instances right from your terminal.
Command-Line Interface
Interact with getOperate instances right from your terminal.
Triggers from external events
Webhooks
In getOperate, webhooks are autogenerated for each Script and Flow, providing either asynchronous or synchronous execution modes.
These webhooks accept incoming HTTP requests, allowing users to easily trigger their getOperate scripts and flows from external services by simply sending a POST request to the appropriate authentified webhook URL (requires passing a token as Bearer or query arg). Their purpose is to have the script run when it receives an input from its associated webhook.
Using webhooks, you could also trigger a script from other scripts.
Webhooks
Trigger scripts and flows from webhooks.
Webhooks: Trigger Scripts from Slack
One use case of webhooks is building a Slackbot with getOperate.
getOperate uses Slack to trigger scripts and flows by establishing Slackbots and creating specific commands. By connecting Slack with getOperate, parsing incoming Slack commands, and leveraging getOperate workflows, operational teams can trigger complex automations directly from Slack.
Slack Integration
Learn how to integrate Slack with getOperate.
Webhooks: Trigger Scripts from Emails
One use case of webhooks is triggering scripts via inbound emails using Mailchimp.
getOperate leverages Mailchimp Mandrill’s capabilities to initiate scripts and flows via email-triggered events. By parsing inbound emails and routing the content to getOperate through webhooks, scripts or flows are activated, enabling automation based on email content or just their arrival.
Mailchimp Mandrill Integration
Learn how to integrate Mailchimp Mandrill with getOperate.