Default Actions

this category contains default nodes, designed to facilitate common automation activities and implement business logic directly out of the box these predefined nodes cover a wide array of functionalities, making them immediately useful for many standard automation tasks bash the bash node in kubeark is a type of execution node designed for running bash scripts or commands within a workflow it allows users to incorporate shell scripting into their data processing or automation tasks, facilitating operations like file manipulation, system administration, and execution of software or commands available in a bash environment by leveraging the bash node, users can execute custom scripts or commands on a linux based executor, enabling a wide range of operations that can be scripted in bash, such as data processing tasks, like file sorting, filtering, and aggregation system operations, including file system management, process control, and environment configuration interfacing with other software tools or services that can be controlled via command line interfaces to use the bash node, you would typically specify the script or commands to be executed, along with any necessary input parameters or environment variables here is a detailed breakdown of the configuration options name the identifier for this particular bash node in your workflow condition this field is where you specify the condition under which this node will be executed if you set a condition, the node will run its script only when that condition evaluates to true on error determines what happens if an error occurs during the execution of the bash script options might include stopping the workflow, retrying the node, skipping it, or executing a compensatory action vault the vault reference please refer local vault docid 6uoo8pp2iygibumgrcnwi input environment variables here, you can declare environment variables that the bash script will use these could be paths, configuration settings, or any other data that shouldn't be hardcoded into the script script the main field where you input the actual bash commands or script to be executed this script can perform a wide array of tasks, from file manipulation to running applications and services when this node is activated, the bash script provided will be run in a shell environment the ability to execute bash commands adds powerful capabilities to your workflow, allowing for complex operations that take full advantage of the host system's features and installed tools deno deno is a javascript/typescript runtime with secure defaults and great developer experience it's similar to node js but includes some key differences, like security defaults that restrict file, network, and environment access unless explicitly enabled here is a description of the deno arguments required for configuring this node name this is where you name your deno node for identification within your workflow condition conditions determine when this node will execute within your workflow if a condition is set, the deno script will only run when the condition is met on error this defines the behavior of the workflow if the deno node encounters an error during execution the action could be to stop the workflow, skip the error, retry, and so forth vault this would be used to select secure storage for sensitive data like api keys or passwords scopes can be defined to limit access please refer to local vault docid 6uoo8pp2iygibumgrcnwi input here, you would provide any input data the deno script needs inputs are typically key value pairs that the script can use environment variables similar to inputs but specifically for environment variables that your deno script may require to run, such as configuration settings that should not be hard coded into the script packages while deno doesn't use npm, and thus does not have a package json file like node js, this section might be used to specify third party modules or dependencies that your script requires in deno, modules are imported directly from urls to use this node, you would need to provide the necessary script, configure any inputs or environment variables your script requires, and set up error handling according to your workflow's needs the configured node can then execute typescript or javascript within the secure deno environment as part of a larger automated process dotnet a dotnet ( net) node allows you to run c# (or other net compatible language) scripts or programs within the context of an automation or data processing workflow here's a breakdown of the configuration options available name this is the identifier for the net node within the workflow it helps you distinguish between different nodes when managing or reviewing workflows condition this optional field allows you to specify a condition under which the net node will be executed if a condition is given, the node will only run its net script when that condition is true on error here, you can define what should happen if the net node encounters an error during its execution options might include stopping the workflow, skipping the node, retrying, etc vault if your net script needs to use sensitive data, such as passwords or api keys, you would use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input in this section, you would specify any input data that the net script requires inputs are generally in the form of key value pairs that the script can consume environment variables these are key value pairs that the net node's environment will recognize they are similar to inputs but are used specifically for environmental configuration rather than script inputs nuget packages since net applications often rely on external libraries, this section allows you to specify any nuget packages that your script depends on nuget is the package manager for net, providing a collection of libraries and tools for net developers when you use this node, you would write a net script or program and input it into the system, specify any dependencies it has via nuget, and configure any inputs or environment variables required this node then processes the net code within the context of the larger workflow, which can involve multiple other nodes, potentially written in different languages or performing different tasks golang this node is designed to run code written in the go programming language, often referred to as golang here’s a breakdown of the configuration options shown name this is where you give your golang node a unique identifier for reference within your workflow condition if specified, this determines the conditions under which the golang node will execute you can configure this to run the node only when certain criteria are met within your workflow on error this configuration dictates the course of action if the golang node encounters an error during its execution options might include actions like stopping the workflow, skipping the node, retrying the operation, etc vault use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input here you would input any data that the golang script requires to run, such as parameters for functions within the go code environment variables these are the environmental parameters that your go code will use during execution they are system level information that can affect how your script runs modules since go uses modules to manage dependencies, this section would be where you specify external packages or modules that your go code depends on in practice, after setting the name and, if necessary, the condition for the execution, you would provide your go code, ensure that all necessary modules and environment variables are specified, and set your on error action this golang node can then be used as part of your workflow to automate tasks using go, integrating with other nodes and services as required httprequest this type of node is designed to perform http requests to communicate with web services here is the breakdown of the configuration fields name you assign a unique identifier to the node, in this case, it's node d6d57f0e , which helps you identify it within your workflow condition this optional field allows you to define a condition under which the httprequest node should be triggered if set, the node will only execute the http request when the condition evaluates to true on error here you decide what action should be taken if an error occurs during the http request options might include stopping the workflow, retrying the request, or proceeding with the next steps without taking any action vault use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input under this section, you configure the details of the http request method this is where you specify the http method to use for the request, such as get, post, put, delete, etc in your screenshot, get is selected url you enter the url to which the http request will be sent authentication if the endpoint requires authentication, you select the type here in your screenshot, basic authentication is selected, which requires a username and password username you provide the username required for authentication password you provide the password corresponding to the username headers http headers can be specified here to include additional information with the request, such as 'content type' or 'authorization' information body if the request method is one that allows a body, such as post or put, you can provide the data to be sent with the request here this field isn’t visible in your screenshot but would typically be included for methods that support a request body once configured, the httprequest node will perform the specified http request when triggered within the workflow the node can handle the response, pass data to subsequent nodes, and integrate with different parts of the system or external services as part of an automated process kubectl kubectl is a command line tool that allows you to run commands against kubernetes clusters to deploy applications, inspect and manage cluster resources, and view logs here's what each part of the node configuration is for name this is the identifier for the node within your workflow here, it is set to node edd3d087 condition this is where you can define conditions that must be met for the kubectl node to execute it acts as a form of flow control, executing the kubectl command only when specific criteria are satisfied on error this setting dictates what should happen if an error occurs during the execution of the kubectl command you can typically choose to stop the workflow, ignore the error, or retry the command vault the vault is used for securely storing and accessing secrets, like passwords or api tokens this could be necessary if your kubectl command interacts with a kubernetes cluster that requires authentication please refer local vault docid 6uoo8pp2iygibumgrcnwi input cluster id this refers to an identifier for a kubernetes cluster within the system the kubectl commands will be executed against the cluster with this id api token this is the authentication token that kubectl will use to authenticate against the kubernetes cluster api args here, you would specify additional arguments or parameters to pass to the kubectl command this field might include the specific kubectl commands and options you want to run by configuring and running this node, you can automate kubernetes operations as part of a larger workflow, for instance, deploying applications, managing resources, or gathering information from your kubernetes cluster playwright the playwright node configuration screens you've provided are for setting up a node that uses playwright within a workflow playwright is a node library that enables developers to automate browser tasks such as testing web applications across various browsers let's go through the configuration options name this field is for the unique identifier of the playwright node in your workflow, here named node 807b0760 condition this optional field allows you to define conditions for the node's execution if specified, the node will execute its actions only when the set condition(s) is true on error this determines what should happen if an error occurs during the playwright node's execution you might choose to stop the process, ignore the error, retry the action, etc vault use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input this section contains various configuration options config this sub section typically contains settings for how playwright should operate device specifies the device emulation settings for the browser, e g , 'desktop chrome' retries the number of times the node should retry the action in case of failure timeout sets the maximum time to wait for the action to complete storage state contains settings related to browser state like cookies and local storage cookies you might be able to specify particular cookie data here origins this could refer to the origin urls for which the storage state (like cookies, local storage) applies storage state path the path to the file with saved storage state that playwright can use to initialize the browser context environment variables here you can set up environment variables that your playwright scripts may require setups specify custom setup scripts or configurations that need to be run before the main playwright actions spaces a workspace or a specific area within the workflow platform where this playwright node is applicable the playwright node allows you to automate browser actions as part of your workflows you could use it for tasks like scraping web data, automating form submissions, or performing end to end tests on web applications python this node is designed to execute python code as part of an automated sequence or data processing pipeline here’s a rundown of the configuration options shown name this is the unique identifier for the node in your workflow, which you can use to reference the node condition an optional setting where you can specify conditions that must be met for the node to execute if a condition is provided, the node will only run its python script when that condition is true on error here, you define what should happen if the node encounters an error while executing the python code options typically include stopping the workflow, skipping the node, or attempting to retry vault use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input under this section, you configure the inputs that the python script needs environment variables these are variables that the python environment will recognize and can affect script execution you can add environment specific variables that your script needs here packages if your python script depends on third party packages, you can list them here this ensures that the necessary packages are available to the python environment when the script runs script this is the most important part it's where you input the actual python code to be executed this script can do anything that python is capable of, given the node's permissions and available libraries, such as data manipulation, calling apis, processing files, and more when this node is executed within a workflow, it will run the specified python script with the given environment variables and packages this allows you to automate tasks using python's powerful capabilities directly within your workflow ssh this node is designed to execute commands on a remote server through an ssh protocol, which provides a secure channel over an unsecured network here’s how you would use the fields in this configuration name assign a unique identifier to this ssh node in your workflow, in this case, node ed726d50 condition define a condition that determines when this node should be executed if set, the node will only perform its action when the specified condition evaluates to true on error decide the behavior of the workflow if there's an error during the ssh command execution options usually include stopping the workflow, retrying the command, or continuing with subsequent actions vault if the ssh login credentials or private keys are stored in a secure vault, you can specify which vault to access use this section to select the appropriate secure storage see local vault docid 6uoo8pp2iygibumgrcnwi input provide the necessary information to make an ssh connection username the ssh username for the remote server address the address of the remote server you want to connect to, typically an ip address or a domain name password the password associated with the ssh username it's one way to authenticate the ssh session private key an alternative to using a password, you can authenticate via a private key if the remote server supports key based authentication script the actual shell commands or a script that you want to execute on the remote server it's entered in the large text field when triggered, the ssh node will establish a secure connection to the specified remote server using the provided credentials once connected, it will execute the given commands or script this can be useful for automating deployment tasks, system administration, or any situation where remote server control is needed within a workflow