Running skills
The recommended way to use a skill is to ask for what you want in plain language. For example, you can say things like:- “Review this release plan using our release process.”
- “Use our incident response skill to help triage this issue.”
- “Help me prepare an RCA in the format our team uses.”
Using a skill shortcut
If you know exactly which skill you want, you can also invoke it directly with its shortcut name. In the current TeamCopilot setup, this is typically written as:- you already know which skill should be used
- you want predictable behavior from a specific skill
- your team uses named skills regularly
If you are not sure which skill to use
You can simply describe the task. TeamCopilot will try to find the most relevant skill for you. That means you can say:- what you are trying to do
- what outcome you want
- any important constraints or context
Running workflows
You can also ask the AI Assistant to run a workflow for you in natural language. For example:- “Run the customer-report workflow for account 123.”
- “Use the deployment workflow for staging.”
- “Run our sync workflow with yesterday’s data.”
Other workflow entry points
Workflows can also be:- run manually from the workflow page
- run from cronjobs
- run remotely through a workflow API key
- resumed from a cronjob handoff session when the run pauses for attention
Calling workflows via APIs
TeamCopilot also supports API access for workflows through workflow-specific API keys. If you want the dashboard to show curl commands with the correct public host, setEXTERNAL_HOST in the TeamCopilot environment.
- When
EXTERNAL_HOSTis set, TeamCopilot uses it as the base URL for API examples. - When it is not set, TeamCopilot falls back to
TEAMCOPILOT_HOSTandTEAMCOPILOT_PORT. - Use a public or externally reachable host value here if people will copy the curl commands from the dashboard.
What workflow API keys do
A workflow API key lets an external caller:- trigger a workflow run
- query the run status
- stop a running workflow
Approval requirement
Workflow API keys are only available once the workflow’s current snapshot is approved. That prevents unreviewed workflow code from being exposed as an external API surface.Typical flow
- Open the workflow page.
- Generate an API key for the workflow.
- Use the key to submit a remote run.
- Poll the run status until it completes.
- Stop the run if needed.
API reference
Start a run
Check run status
run_handleworkflow_slugstatuslogserror_messagestarted_atcompleted_atinputs
Stop a run
Constraints
- the API key must belong to the same workflow being run
- the workflow must be approved before the key can be created or used
- each workflow must always keep at least one API key
Running a workflow manually
Workflows can also be run manually from the Workflows tab. This is useful when:- you want to choose the workflow yourself
- you want to provide inputs explicitly in the UI
- you want a more structured run flow than chat
- Open the Workflows tab.
- Select the workflow you want.
- Open the manual run screen.
- Fill in any required inputs.
- Start the workflow.
Recommended approach
For day-to-day use:- start with natural language in the AI Assistant
- use a named skill shortcut when you know the exact skill you want
- use manual workflow runs when you want explicit control over workflow inputs