PipedreamHQ / PipedreamHQ/pipedream

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

Open
#16,674 1 comment 0 reactions 0 assignees View on GitHub
bug triaged
Dominant language
JavaScript
Stars
11.7k
Forks
5.8k
Avg merge
3d 10h
Merged PRs (30d)
102

Description

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

**To Reproduce**
Steps to reproduce the behavior:

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

**Expected behavior**
Configuration kept as OAuth

**Screenshots**
Image

**Additional context**
Reported by a user

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.