ποΈ Event
An Event task is used to publish an event into one of the supported eventing systems. The supported eventing models include:
ποΈ Call an HTTP Service (APIs, Rest)
HTTP task allows for making calls to remote services exposed over HTTP/HTTPS.
ποΈ HTTP Poll
HTTP Poll task is used to invoke HTTP API endpoints until the specified condition matches.
ποΈ Inline
Inline tasks enable the execution of essential logic during workflow runtime by evaluating a JavaScript expression using an evaluator like GraalJS.
ποΈ Transformation using JQ
A system task that allows the processing of JSON data supplied to the task by using the popular JQ processing toolβs query expression language.
ποΈ Rules Engine Execution
The Business Rule task allows the evaluation of business rules defined in spreadsheets. Supported formats include CSV, XLS, and XLSX.
ποΈ Wait For Webhook
Webhook is an HTTP-based callback function that facilitates the communication between the Conductor and other third-party systems. It can be used to receive data from other applications to the Conductor. Conductor currently supports Webhook integration with the following platforms:
ποΈ JDBC Task
A JDBC task is a system task used to execute or store information in SQL databases.
ποΈ Update Secret
A system task that updates the value of any secret, given that the user has permission to update the secret.
ποΈ Get Signed JWT
A system task that allows signing a JWT token.
ποΈ Update Task
A system task to update the status of other tasks.
ποΈ Opsgenie
A system task to send alerts to Opsgenie in the event of workflow failures. This task can be used with the Query Processor task, which fetches metadata details to trigger alerts to Opsgenie as required.
ποΈ Query Processor
A system task designed to execute queries across various systems, primarily used for alert generation.