Skip to main content
← Back to list
01Issue
FeatureShippedSwamp CLI
Assigneeskeeb

Relationships

#700 Support trigger.inputs for scheduled workflows

Opened by bixu · 6/19/2026· Shipped 6/20/2026

Scheduled workflows (trigger.schedule) have no mechanism to supply input values at fire time. The trigger schema only accepts { schedule: string } with additionalProperties: false.

If a workflow has required inputs, the only workaround is to set default values in the input schema, which conflates "the value I want for cron runs" with "the schema's default for all callers." A trigger.inputs field would let cron supply values without hardcoding defaults.

Current workaround: set default on the input and remove it from required.

Proposed: add trigger.inputs to the trigger schema:

trigger:
  schedule: "* * * * *"
  inputs:
    projectId: "a6b254a2-0b57-4d0f-bf8b-fef767ab119e"

These would be merged as baseline inputs for scheduled runs, same as --input on swamp workflow run.

02Bog Flow
OPENTRIAGEDIN PROGRESSSHIPPED+ 1 MOREASSIGNED+ 5 MOREREVIEW+ 3 MOREPR_MERGED+ 1 MORECONTRIBUTOR_NOTIFIED

Shipped

6/20/2026, 3:34:22 PM

Click a lifecycle step above to view its details.

03Sludge Pulse
keeb assigned keeb6/20/2026, 2:34:16 PM
Editable. Press Enter to edit.

keeb commented 6/20/2026, 3:34:30 PM

Thanks @bixu for reporting this! The fix has been merged and a release is on its way. We appreciate your contribution to swamp.

Sign in to post a ripple.