Skip to main content
T1 starter · e-commerce / personal: no infer: anywhere in this file. A workflow engine is not an LLM wrapper: the DAG, the tools and one CEL comparison do the whole job, deterministically, for free.

The job

You’re waiting for a price to drop. Checking the page every day is a robot’s job. This workflow pulls one structured field from the shop’s API, compares it to your target, and pings your webhook only when it’s time to buy.

The shape

The file

price-watch.nika

How it works

1

Fetch ONE field, not a page

mode: jq extracts structured JSON from the API response, and the extract: block binds named fields: ${{ tasks.check.price }} is a number, not a blob of HTML.
2

CEL gates the alert

The named binding crosses in with: (price: ${{ tasks.check.price }}), then when: ${{ with.price < const.alert_below }} is a plain CEL comparison. False → the task is skipped, not failed.
3

The webhook stays secret

secrets: declares an env-backed reference (source: env; file is the other store 0.124.3 resolves). A vault source is withdrawn from the contract: the check stays green with a hint that names NIKA-VAR-001, and the run fails with it, an unresolved secrets.<name>. The URL is masked in logs: ${{ secrets.alerts_webhook }} never appears in a trace.

Constructs you just used

Run it

What it needs: Nothing: the placeholder shop host resolves nowhere, and the recover: sample sits above the target, so the alert is skipped. No model, no key.
1

Rehearse it

Nothing is written in your folder. Before it runs, nika try names the hosts a step may reach: may reach: api.shop.example.com · hooks.slack.com — the mock replaces the model, not the network.
2

Get your own copy

Save the file above as price-watch.nika in a new folder. It reads no sample file.
3

Check it, then run it

The run writes no file: it pings your webhook only when the price drops below the target.To watch a real product, point const.product_api at it, add its host to permits.net.http, and set ALERTS_WEBHOOK_URL.

Make it yours

  • Watch N products: lift the URL into a list input and for_each over it. See Competitor radar for the fan-out pattern.
  • Schedule it: workflow files describe a run. Your host’s cron (or nika serve) decides when runs start.
  • Add a second when: branch that notifies on price INCREASES above a ceiling.

Next · Social repurpose

The last starter introduces the diamond: one source fanning into three parallel rewrites.