[BUG] HTTP trigger in workflow created via API template does not keep OAuth configuration #16674

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Open

andrewjschuang opened this issue May 15, 2025 · 0 comments

Labels

bug

Collaborator

andrewjschuang commented May 15, 2025 •

edited

Loading

Describe the bug
HTTP trigger in workflow created via API template does not keep OAuth configuration

To Reproduce
Steps to reproduce the behavior:

Create a new workflow
Add an HTTP trigger, configure OAuth authorization
Click on Instantiate via API in the menu, include all props
Copy generated request data
Note "authorization": "OAuth"
Create a new workflow via API
See that the Authorization configuration is not OAuth

Expected behavior
Configuration kept as OAuth

Screenshots

Additional context
Reported by a user

The text was updated successfully, but these errors were encountered:

andrewjschuang added the bug label

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment