What problem does it solve? Setting up credentials for external services (GitHub, Stripe, Google, etc.) inside a Notion Worker involves choosing between API keys and OAuth, managing secrets, and handling redirect URLs — this guide walks through each decision and step so authentication works both locally and after deployment. ## Core Features & Use Cases - Decision Framework: Mechanically choose between personal API keys/PATs and OAuth based on what the provider offers and whether the worker should depend on one person's credential. - API Key Setup: Store tokens in .env, read them via process.env in execute, test with curl, and push secrets with ntn workers env push. - OAuth Setup: Declare worker.oauth(), register an OAuth app, configure the redirect URL from ntn workers oauth show-redirect-url, and run the flow with ntn workers oauth start. - Use Case: You are building a sync that pulls GitHub issues into Notion. The guide tells you to use a personal access token, add it to .env as GITHUB_API_TOKEN, verify it with curl, then push it before deploying. ## Quick Start Ask the assistant to set up authentication for the external service your Notion Worker integrates with, and it will recommend API key or OAuth and walk through the setup steps.
