Skip to content

Invoking run_workflow within actions_run_trigger doesn't recognize inputs field and not passed when triggering workflow #1877

@klakshmikantha

Description

@klakshmikantha

Describe the bug

Invoking run_workflow within actions_run_trigger doesn't recognize inputs field and not passed when triggering workflow although it is passed in call to remote MCP server. It returns error - 'Limitation: the MCP actions_run_trigger tool does not expose an 'inputs' parameter; the dispatch succeeded (204 queued) but inputs were not transmitted and may default within the workflow.'

Is there a way to ensure it identifies and passes the inputs?

Affected version

Remote version

Steps to reproduce the behavior

Included below text in prompt to agent/model with remote github MCP server - payload schema: { method: 'run_workflow', owner: 'REDACTED', repo: 'REDACTED', workflow_id: 'REDACTED.yaml', ref: 'REDACTED', inputs: { FIELD1: REDACTED, FIELD2: REDACTED, FIELD3: REDACTED, FIELD4: REDACTED } }

Expected vs actual behavior

Input fields should be recognized and passed when invoking the workflow. All other fields are recognized.

Appreciate any assistance.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions