fix(monday): document API key auth setup (not OAuth)#612
Merged
laurenzlong merged 2 commits intoMay 26, 2026
Conversation
Monday is API-key authenticated per the live provider catalog and the connector source (providers/monday.go: AuthType: ApiKey, header Authorization). The existing guide walked users through creating an OAuth app and entering Client ID/Secret into the Ampersand Dashboard's provider-app form, but that form shows 'No options' for Monday in the current Dashboard. Users following the prior guide would hit a dead end. Changes: - Replace OAuth provider-app setup with an API-token setup section that mirrors Monday's official auth docs verbatim (profile picture -> Developers -> API token > Show). - Remove the 'Add Monday app details in Ampersand' section entirely; API-key providers do not need a provider app in Ampersand. - Note that the InstallIntegration component prompts the customer for their Monday API token directly. - Fix '# Using the connector' -> '## Using the connector' (was H1 inside an H2-only structure). Out of scope for this PR: - Write Actions support claim (tracked in amp-labs/connectors#3003). - Cleanup of the now-orphaned monday-amp-project.png screenshot; the file is left on disk and can be removed in a separate sweep. Also: add .env to .gitignore so local secrets don't surface in PRs.
Compressed via gifsicle (-O3 --lossy=300 --colors 64 --scale 0.7) to 2.0 MB at 514x336. Lands within the peer api-key GIF size range (1.2-2.6 MB existing in repo).
laurenzlong
approved these changes
May 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
The current
monday.mdxwalks users through creating a Monday OAuth app and entering Client ID + Client Secret into the Ampersand Dashboard's provider-app form. That form doesn't exist for Monday in the current Dashboard — selecting Monday from the Create OAuth Provider App dropdown shows "No options" because Monday is API-key authenticated, not OAuth.Verified against three sources:
/v1/providers:monday.authType == "apiKey",apiKeyOpts.header.name == "Authorization".amp-labs/connectors/providers/monday.go:AuthType: ApiKey.Authorizationheader.Users following the prior guide would hit a dead end at the "Enter Client ID / Client Secret" step.
Changes:
InstallIntegrationflow.InstallIntegrationcomponent prompts the customer for their Monday API token.# Using the connector→## Using the connector(was H1 inside an H2-only structure)..envto.gitignore.Out of scope:
support.write: falsewhile a real Write API call toboardssucceeds — that's tracked separately in amp-labs/connectors#3003.monday-amp-project.pngbecomes orphaned after this change but is left on disk; cleanup of orphaned images can be a separate sweep.Screenshot