You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@wsxiaoys i have read the notion api. Notion has elements like Database, Page, Block. It does not have any knowledge about issues. They are just database and pages to notion view.
So, i think we need another type of integration called notion besides github/gitlab, webdocument.
it has the following property.
name string
database_id string
access_token string
Alternately, we can treat Notion and WebDocument as the same, just different kind of documents with different api(notion api vs webcrawler). If so, the table web_documents should add more columes, e.g. access_token, document_type.
I prefer adding a notion integration type. What do u suggest?
Hi, a common practice in Notion is using a database to store data. The linked template in the thread is an example. For the initial PR, it's fine to use fixed column names (title/summary) and import them (similar to syncing GitHub issues).
We can iterate on this in future steps, such as allowing the front end to decide which columns should be indexed.
Notion database is popular as one kind of issue tracker: https://www.notion.so/templates/notion-issue-tracker
We'd like to integrate it as one kind of web document source.
References:
The text was updated successfully, but these errors were encountered: