OpenAPI schema: execution.workflowId incorrectly typed as number instead of string

[poodle64]

Summary

The OpenAPI schema at /api/v1/openapi.yml defines execution.workflowId as type: number, but n8n returns alphanumeric string workflow IDs.

Schema Location

components/schemas/execution/properties/workflowId

Current (incorrect)

workflowId:
  type: number
  example: '1000'

Expected (correct)

workflowId:
  type: string
  example: '2tUt1wbLX592XDdX'

Evidence

The same schema correctly types workflowId as string in other locations:

• sharedWorkflow.workflowId: type: string, example: 2tUt1wbLX592XDdX
• workflowVersion.workflowId: type: string
• importResult.tags.mappings[].workflowId: type: string
• Path parameter workflowId: type: string

Only execution.workflowId is incorrectly typed as number.

Impact

API clients generated from this schema fail to deserialize execution responses because workflow IDs like hykP7o8yHNvRiyOP cannot be parsed as numbers.

n8n Version

Observed in n8n v1.1.1 OpenAPI schema (current public API)

[n8n-assistant]

Hey @poodle64,

Thank you for reaching out! We’ve received your issue and are looking into it. To help us track this internally, we’ve created a Linear ticket with the reference: "GHC-6265".

We’ll keep you updated as we make progress, but if you have any additional details or context to share, feel free to add them here - it’s always helpful!

Thanks for your patience and for bringing this to our attention.

---

For INTERNAL use only: GHC-6265

[MookieLian]

Thank you for bringing this up! It looks like this issue is a duplicate of #24122, where we're already tracking progress and updates. To keep things organised, we'll close this issue and continue the discussion over there.

If you have any additional details or context that might help, please feel free to add them to the original issue. Your input is always appreciated!

Thanks again for your contribution, and let us know if there's anything else we can assist with.

#closed:duplicate