Skip to main content


Targets define where a Task will run and using what credentials, after which teams review them.

The Target Object#


The name of the Target.


A description for the Target.


The type of the integration for the Target.


The name of the Slack channel to send the review messages.


The review configuration for Target: none, default, or teams.

Review ModeDescription
noneThe default mode. Skips reviews and new Tasks are ready to run.
anyoneAnyone with access to the review message in Slack can review the Task. You can control who can review the Task by using a private Slack channel.
teamOnly people from specific teams can review the Tasks. Requires a list of team names in the reviewers option. At least one person from each team has to approve the Task.


A comma-separated list of names with the Teams that must review Tasks on this Target.


The name of the Slack channel to send review messages. Optional when review=none


A list of key-value pairs with passwords and keys required to run tasks. The required secret names are defined on the type of Integration in the Target.


Where tasks will run.

runops-hosted: runners will access resources reachable from the internet, like AWS or GCP APIs. They require no additional setup.

self-hosted: require additional setup to reach resources running on private networks.


The secret token used to setup self-hosted runners

For runops V2 runner, below configuration is required


The entity responsible for executing the tasks.

runopsRunops open source runner. Faster and can run "on premise".
githubDefault runner, if not provided.


If using runops runner, then a third party secret provider is required. AWS secrets maneger, Hashcorp vault (databases and KV engines supported).)

awsIf using AWS secrets manager.
hashcorp/dbIf using hashcorp vault databases engine (dynamic secrets).
hashcorp/kvIf using hashcorp vault KV engine (static secrets).


The name or the path of the secret. For AWS, the secret name. For vault, the path, including the engine (i.e. '/v1/secret/foo' or '/databases/creds/my-postgres')


Tags are used to bind the runner to run only specific targets. Normally this is related to environments, such as 'dev' or 'prod', but can be any string.


Configs are mostly used for hashcorp vault databases engines. Since this engine does not return the HOST and the PORT of the DB, some extra config is required (JSON format)

--config '{"PG_HOST":"", "PG_PORT":5432}'

Custom markup