Github Actions
In the following example, we are point of sale SaaS company and we are creating two goals for our customers:- Customer making their first widget sale
- Customer receiving 6 payments
Single configuration file
You can create a single configuration file calledvalued.yaml or .valued.yaml either at the top level, or inside a directory called config or .config.
Valued’s configuration file supports .json, .toml, .yml and .yaml formats.
Example
.config/valued.yaml
Multiple files
You can also create individual configuration files for goals and signals. Create avalued, .valued, config/valued, or .config/valued directory, and add one goals.toml and one signals.toml file.
Example
.valued/goals.toml
.valued/signals.toml
Set up the GitHub Action
-
Obtain a token for the Valued API. In the Valued Dashboard, click Integrations and copy “API Key”. Store it in the
VALUED_API_KEYsecret. - Add the following step to your GitHub Action workflow: