trigger-workflow

Skill for triggering a deployed Codika workflow and optionally polling for execution results

When to use

• Test a deployed workflow
• Execute a workflow via the CLI instead of the platform UI
• Automate workflow execution in scripts or CI

Prerequisites

• Use case deployed (project.json contains devProcessInstanceId)
• Authenticated via codika-helper login or CODIKA_API_KEY env var
• API key with workflows:trigger scope

Resolving the workflow ID

The workflowId is the workflowTemplateId from config.ts. If the user provides a use case folder path, read config.ts to find the available workflow IDs and their trigger types. Only workflows with trigger.type === 'http' can be triggered with this command.

Command

codika-helper trigger <workflowId> [options]

Arguments

Argument	Description
<workflowId>	The workflowTemplateId from config.ts

Options

Option	Description	Default
--payload-file <path>	Read payload from JSON file, or - for stdin	—
--process-instance-id <id>	Explicit process instance ID	Auto from project.json
--path <path>	Path to folder with project.json	Current directory
--poll	Wait for execution to complete	Fire-and-forget
--timeout <seconds>	Max poll time	120
-o, --output <path>	Save result to file (with —poll)	stdout
--json	JSON output	—

Examples

With payload (recommended: heredoc via stdin)

codika-helper trigger search --poll --payload-file - <<'EOF'
{"query": "test"}
EOF

Using --payload-file - with a heredoc avoids shell escaping issues with inline JSON.

Fire-and-forget

codika-helper trigger search

Returns immediately with execution ID.

Payload from file

codika-helper trigger analyze --payload-file ./test-input.json --poll

Save result

codika-helper trigger search --poll -o result.json --payload-file - <<'EOF'
{"query": "test"}
EOF

Custom timeout

codika-helper trigger generate --poll --timeout 300

Process instance ID resolution

1. --process-instance-id flag
2. devProcessInstanceId in project.json at --path
3. devProcessInstanceId in project.json in current directory

Result statuses

Status	Meaning
success	Workflow completed, resultData contains output
failed	Error occurred, errorDetails.message describes failure
pending	Still running (during polling)

Error reference

HTTP	Error	Fix
401	Invalid API key	Re-login with codika-helper login
403	Missing scope	Create key with workflows:trigger scope
404	Workflow not found	Check workflowTemplateId in config.ts
412	Instance inactive	Re-deploy or activate in platform

Important notes

• Only HTTP-triggered workflows can be triggered via CLI
• The workflowId is the workflowTemplateId, not the n8n ID
• Payload is wrapped in {"payload": {...}} automatically
• File uploads are not supported via CLI — use the platform UI