📄️ Dynamic Inputs
When you start a Conductor workflow, you can pass inputs to the workflow - which can be used as parameters for various steps in the workflow. As the tasks progress in a workflow - each task will create its own outputs. So how can this data from previous tasks be used in the steps succeeding it? In Conductor, data can be passed to a task in different ways, such as from workflow inputs/outputs, prior task inputs/outputs, variables, and secrets.
📄️ Schema Validation
Create schemas to define and enforce the payload structure of workflow or task inputs/outputs.
📄️ Using Secrets
Sensitive information such as usernames, passwords, API keys, and authorization tokens is often required in workflows. To protect this sensitive data, secrets can be used to hide these values on the user interface. Secrets allow you to securely manage and use sensitive information within workflows without exposing it directly.
📄️ Using Environment Variables
Environment variables are essential for managing variables that need to be frequently accessed across multiple workflows. By storing these variables globally, they can be reused, making workflows more efficient and easier to manage.
📄️ Caching Task Outputs
Some task types support caching, which saves task outputs for reuse in subsequent task executions. This feature can be configured in the task configuration.