Notes

2022-06-11

@David

• Syncing of a GitHub issues board and a Notion database has to happen via some external automated script w/ API calls
• Can be built custom using a GitHub workflow potentially
  • Workflows exist:
    • https://github.com/marketplace/actions/github-issues-on-notion
    • https://github.com/marketplace/actions/notion-x-github-action
      • The second one appears to be more feature-complete
• Pre-built 3rd party options exist:
  • https://zapier.com/apps/github/integrations/notion/607884/save-new-github-issues-in-notion-databases
  • https://automate.io/integration/github/notion
  • https://www.bardeen.ai/playbooks/export-issues-from-github-to-notion
  • https://githubnotionsync.com/
• @David would much rather not go with a third party and stick with a GitHub action

2022-06-13

@David

• Prototyped Notion X GitHub Action.
• Discovered manually-dispatched workflows are only discoverable by GitHub when they exist on main.
• Workflow fails. Seems like this is an issue with the Notion API having been changed since the last release of the Notion X GitHub workflow.
• Will investigate a 3rd party solution instead. They seem to be more feature-complete anyways.

• Issue seems to be API-related:
• But latest commit to Notion X GitHub appears to have been made after API-breaking Notion changes

Comparing v1.2.3...master · tryfabric/notion-github-action

• Maybe something is still wrong with the way I’ve configured it. Will investigate further.