PipedreamHQ / PipedreamHQ/pipedream
[Feature] Support multiple auth strategies for apps where applicable
- Dominant language
- JavaScript
- Stars
- 11.7k
- Forks
- 5.8k
- Avg merge
- 3d 10h
- Merged PRs (30d)
- 102
Description
### Request
Users should have the ability to provide an _internal integration token_ for a "Notion account" (in Pipedream) as an alternative to opening the OAuth flow to generate an OAuth token.
### Explanation
When using the Notion actions, Pipedream offers a way to select a Notion account, or to create a new Notion account that opens the OAuth flow to authorise the Pipedream integration to access a Notion workspace.
However creating a custom "internal integration" is a common flow for branding the bot that will then integrate with your Notion content. To do this, there is very simple instructions [via Notion's API documentation](https://developers.notion.com/docs/getting-started) that [then leads to](https://www.notion.so/my-integrations) an _internal integration token_ that [can be used in place of an OAuth token](https://developers.notion.com/docs/authorization).
**Requested solution:** in addition to attaching a new Notion account, users should have the ability to provide the internal integration token instead of opening the OAuth flow, for Notion actions.
There is no current workaround I know of for using pre-built Notion actions. Instead one must directly interact with the Notion API within a node.js code step with axios included.
Contributor guide
Assessment
This issue has not been assessed yet.