dailybot-workflow
List, inspect, and trigger Dailybot workflows — enumerate the workflows configured for the organization, read one workflow's configuration, and fire API-triggerable workflows on demand. Use when the developer asks "list my workflows", "show workflows", "what's in the release workflow?", "trigger the deploy workflow", or "fire automation X". Creating/editing workflows is done in the Dailybot web app. Plan-gated feature.
DailybotHQ · 已有 AI 审核记录
安装与使用
运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。
npx skills add DailybotHQ/deepworkplan-skill --skill dailybot-workflow技能说明
name: dailybot-workflow description: List, inspect, and trigger Dailybot workflows — enumerate the workflows configured for the organization, read one workflow's configuration, and fire API-triggerable workflows on demand. Use when the developer asks "list my workflows", "show workflows", "what's in the release workflow?", "trigger the deploy workflow", or "fire automation X". Creating/editing workflows is done in the Dailybot web app. Plan-gated feature. version: "3.13.0" documentation_url: https://www.dailybot.com/skill.md user-invocable: true metadata: {"openclaw":{"emoji":"🔀","homepage":"https://dailybot.com","requires":{"anyBins":["dailybot","curl"]},"primaryEnv":"DAILYBOT_API_KEY","install":[{"id":"cli-install-script","kind":"download","url":"https://cli.dailybot.com/install.sh","label":"Install Dailybot CLI (official script — preferred on Linux/macOS)"},{"id":"pip","kind":"pip","package":"dailybot-cli","bins":["dailybot"],"label":"Install Dailybot CLI via pip (fallback if binary fails)"}]}} allowed-tools: Bash, Read, Grep, Glob
Dailybot Workflows
Requires
dailybot-cli >= 3.9.0(the skill-pack baseline). Thedailybot workflow list/get/triggercommand group — including--filter api_triggerand--payload— is available at this floor. Ifdailybot --versionreports below 3.9.0, ask the developer to rundailybot upgrade. See../SKILL.md§ Required Dailybot CLI version for install commands and version-check tooling.
You help developers read and trigger the workflows configured for their organization. Workflows are Dailybot's automation objects (multi-step sequences that connect check-ins, forms, and chat actions).
- List / Get — enumerate workflows and inspect their configuration.
- Trigger — fire an API-triggerable workflow on demand, optionally with a
JSON payload that the workflow can reference as
{{trigger.body.*}}.
Creating / editing workflows is web-app only. There is no CLI path for creating, editing, enabling, or deleting a workflow. If the developer wants to change one, point them at the Dailybot web app.
Plan-gated feature. Workflows are available on higher-tier plans. On a plan without them (and on the FREE plan generally) these operations return
403 plan_upgrade_requiredwith anupgrade_url— surface the upgrade path and stop. See../shared/list-query-and-errors.md§ 6.
Auth model — API key or login
Workflow commands accept either a Bearer login session (dailybot login)
or an org API key (DAILYBOT_API_KEY). Results are scoped to the acting
identity's permissions (the server resolves the API key's owner). See
../shared/list-query-and-errors.md § 6
for the full API-key ↔ Bearer parity and plan-gating rules.
When to Use
List / inspect:
- "list my workflows", "show the org's workflows", "what workflows do we have?"
- "show me the release workflow", "what's configured in workflow X?"
- Another skill needs a workflow's UUID or its configuration for context.
Trigger:
- "trigger the deploy workflow", "fire automation X", "run the onboarding workflow"
- "trigger workflow
<uuid>with this payload" - A chat button with
callback_workflowfires the same path — see../chat/SKILL.md§ Workflow trigger buttons.
Do not use this skill to create or change a workflow — that's a web-app
operation. And do not confuse it with form workflow states (the
draft → review → released states inside a single form) — those are managed in
../forms/SKILL.md. This skill is the org-level
workflow object.
To tag an existing workflow with organization Labels after you have its
UUID from workflow list, use ../labels/SKILL.md
(dailybot label assign <uuid> --type workflows — automations is an alias).
Step 1 — Verify Setup
Read and follow the authentication steps in ../shared/auth.md.
Confirm at least one credential is present:
dailybot status --auth 2>&1
If auth fails or the developer declines, skip and continue with your primary task.
Step 2 — List Workflows
dailybot workflow list --json
Returns the workflows visible to the caller in the standard pagination
envelope ({count, next, previous, results}), and prints a Showing X of N
footer in human mode.
Query flags
workflow list accepts the full shared list query flag set — pagination
(--page, --page-size, --all, --limit), search (--search / --grep),
and date range (--since, --until, --date, --last-week, --today). The
complete flag table, defaults, and the envelope/footer contract live in
../shared/list-query-and-errors.md —
read it once and don't duplicate the reasoning here.
# Everything (default — walks all pages):
dailybot workflow list --json
# Search by name, most recent first page only:
dailybot workflow list --search release --page-size 20 --json
# Fetch every page explicitly:
dailybot workflow list --all --json
# Filter to only API-triggerable workflows (client-side filter):
dailybot workflow list --filter api_trigger --json
The --filter api_trigger flag is a client-side convenience — it returns only
workflows whose event type is api_trigger ("When triggered via API or
button"), i.e. the workflows you can fire from workflow trigger or from a
chat button's callback_workflow.
Step 3 — Inspect a Workflow
dailybot workflow get <workflow_uuid> --json
Returns the single workflow's full configuration. Treat the JSON as the source of truth for "what does this workflow do?"; surface the relevant parts to the developer rather than re-deriving them.
Step 4 — Trigger a Workflow
阅读完整来源 ↗**Only
api_triggerw