Triage worthwhile issues

This recipe keeps an Agent from spending time on every new issue. A connected GitHub account starts the run when an issue opens, a Model block answers Yes or No to “Is this issue worth a maintainer’s time?”, and only Yes reaches the Triage Agent. A No ends the run.

opened (GitHub issues.opened) → worth_it (Yes/No) → yes → triage (Triage Agent)
                                                  → no  → ends

The Checkfu CLI and TypeScript SDK are private-alpha artifacts with no self-service public installation channel. Part of this flow is behind a rollout fence; a deployment that has not enabled it refuses the request rather than running it. Confirm capability status before making availability part of your application’s contract.

Before you start

You need:

An API key with the admin or root role in CHECKFU_API_KEY.
A service account for the Automation to run as (RUNS_AS) and the person who authors it (AUTHOR). An API key is not a person, so a create through an API key names the author.
A connected GitHub account (GITHUB_ACCOUNT, a conn_…).
The Triage Agent (TRIAGE_AGENT) and the Environment it runs in (ENVIRONMENT). When the Workspace has exactly one, delete the environment_id line and leave out ENVIRONMENT.
A model routing profile with the key fast-judge, or change route.profile to one you have.

export RUNS_AS=prin_0123456789abcdef0123456789abcdef
export AUTHOR=prin_fedcba9876543210fedcba9876543210
export GITHUB_ACCOUNT=conn_0123456789abcdef0123456789abcdef
export TRIAGE_AGENT=agent_0123456789abcdef0123456789abcdef
export ENVIRONMENT=env_0123456789abcdef0123456789abcdef

The CLI examples use CLI access and the TypeScript examples use the TypeScript SDK.

Create the draft

Save the recipe as proactivity.yaml. It is the published proactivity.yaml with created_by_principal_id added:

proactivity.yaml

# yaml-language-server: $schema=https://docs.checkfu.com/openapi.json#/components/schemas/CreateBlockAutomation
name: Triage worthwhile issues
runs_as: "${RUNS_AS}"
environment_id: "${ENVIRONMENT}"
created_by_principal_id: "${AUTHOR}"
blocks:
  - id: opened
    type: trigger
    trigger: { type: app_event, connection_id: "${GITHUB_ACCOUNT}", event: issues.opened }
  - id: worth_it
    type: model
    route: { profile: fast-judge }
    prompt: "Is this issue worth a maintainer's time? {{opened.issue.title}} {{opened.issue.body}}"
    format: { type: yes_no }
  - id: triage
    type: agent
    agent: "${TRIAGE_AGENT}"
    prompt: "Triage {{opened.issue.html_url}}. Why it matters: {{worth_it.reason}}"
wires:
  - { from: opened, to: worth_it }
  - { from: worth_it, port: "yes", to: triage }

checkfu automations create -f proactivity.yaml --var RUNS_AS=$RUNS_AS --var AUTHOR=$AUTHOR \
  --var GITHUB_ACCOUNT=$GITHUB_ACCOUNT --var TRIAGE_AGENT=$TRIAGE_AGENT --var ENVIRONMENT=$ENVIRONMENT

curl --request POST https://api.checkfu.com/v1/automations \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31" \
  --header "Idempotency-Key: $(uuidgen)" \
  --header "Content-Type: application/json" \
  --data '{
    "name": "Triage worthwhile issues",
    "runs_as": "'"$RUNS_AS"'",
    "created_by_principal_id": "'"$AUTHOR"'",
    "environment_id": "'"$ENVIRONMENT"'",
    "blocks": [
      {
        "id": "opened",
        "type": "trigger",
        "trigger": { "type": "app_event", "connection_id": "'"$GITHUB_ACCOUNT"'", "event": "issues.opened" }
      },
      {
        "id": "worth_it",
        "type": "model",
        "route": { "profile": "fast-judge" },
        "prompt": "Is this issue worth a maintainer\u0027s time? {{opened.issue.title}} {{opened.issue.body}}",
        "format": { "type": "yes_no" }
      },
      {
        "id": "triage",
        "type": "agent",
        "agent": "'"$TRIAGE_AGENT"'",
        "prompt": "Triage {{opened.issue.html_url}}. Why it matters: {{worth_it.reason}}"
      }
    ],
    "wires": [
      { "from": "opened", "to": "worth_it" },
      { "from": "worth_it", "port": "yes", "to": "triage" }
    ]
  }'

import { Checkfu, recipes } from "@checkfu/sdk"

const checkfu = new Checkfu({ apiKey: process.env.CHECKFU_API_KEY })

const document = recipes.proactivity({
  runsAs: process.env.RUNS_AS!,
  environmentId: process.env.ENVIRONMENT,
  account: process.env.GITHUB_ACCOUNT!,
  route: { profile: "fast-judge" },
  agent: process.env.TRIAGE_AGENT!,
})

const automation = await checkfu.automations.create(
  {
    ...document,
    created_by_principal_id: process.env.AUTHOR,
  },
  { idempotencyKey: crypto.randomUUID() },
)

Keep the auto_… id it returns in AUTOMATION.

Grant what it needs

The service account needs use_connection on the GitHub account, act_as on the Triage Agent and use_model on the route. GET /v1/automations/{id}/access lists each one with its status:

curl https://api.checkfu.com/v1/automations/$AUTOMATION/access \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31"

Grant a missing one with a PermissionAssignment:

curl --request POST https://api.checkfu.com/v1/permission-assignments \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31" \
  --header "Idempotency-Key: $(uuidgen)" \
  --header "Content-Type: application/json" \
  --data '{
    "subject": { "type": "principal", "id": "'"$RUNS_AS"'" },
    "resource": { "type": "connection", "id": "'"$GITHUB_ACCOUNT"'" },
    "permission": "use_connection"
  }'

A grant that already exists answers 409.

Test with a sample issue

The sample event has the shape GitHub sends, so {{opened.issue.title}} and the other references resolve.

checkfu automations test $AUTOMATION \
  --event '{"issue":{"title":"Login fails after upgrade","body":"Every sign-in returns 500 since v2.","html_url":"https://github.com/acme/api/issues/42"}}'

curl --request POST https://api.checkfu.com/v1/automations/$AUTOMATION/test \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31" \
  --header "Content-Type: application/json" \
  --data '{
    "event": {
      "issue": {
        "title": "Login fails after upgrade",
        "body": "Every sign-in returns 500 since v2.",
        "html_url": "https://github.com/acme/api/issues/42"
      }
    }
  }'

const test = await checkfu.automations.test(automation.id, {
  event: {
    issue: {
      title: "Login fails after upgrade",
      body: "Every sign-in returns 500 since v2.",
      html_url: "https://github.com/acme/api/issues/42",
    },
  },
})

Starting from an app’s events needs a deployment that registers provider triggers. Where it does not, test and publish refuse with automation.draft_has_problems and the problem “Starting from an app’s events is not available here”. Check capability status, or start the same blocks from a webhook trigger meanwhile.

Publish and watch

checkfu automations publish $AUTOMATION

curl --request POST https://api.checkfu.com/v1/automations/$AUTOMATION/publish \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31" \
  --header "Content-Type: application/json" \
  --data '{}'

const publication = await checkfu.automations.publish(automation.id, {})

List the runs and their status:

checkfu automations runs $AUTOMATION --limit 5

curl "https://api.checkfu.com/v1/automation-runs?automation_id=$AUTOMATION&limit=5" \
  --header "Authorization: Bearer $CHECKFU_API_KEY" \
  --header "Checkfu-Version: 2026-08-31"

const runs = await checkfu.automationRuns.list({ automation_id: automation.id, limit: 5 })

The publish summary names what it listens for. Each new issue starts a run; a No answer ends it on worth_it, and Yes starts a Triage Session. Pause and resume with checkfu automations pause and checkfu automations resume.

See Automations for every block and field, and Trigger Automations from providers for how provider events are delivered.

Get started

Agents

Environments

Context

Tools

Permissions

Automations

Sessions

Security & Billing

Triage worthwhile issues

Before you start

Create the draft

Grant what it needs

Test with a sample issue

Publish and watch

​Before you start

Create the draft

Grant what it needs

Test with a sample issue

Publish and watch

Before you start