| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
docs: add changelog entry for two-factor authentication (CON-159) (#6949) ## What Adds a changelog entry announcing two-factor authentication for the Nango dashboard ([CON-159](https://linear.app/nango/issue/CON-159/update-changelog-for-mfa-redesign)). Covers what shipped across the MFA project (#6814, #6822, #6832, #6878, #6894): - TOTP enrollment from the Profile settings page - Single-use recovery codes as a backup sign-in method - Per-member 2FA status on the Team settings page Dated July 27, 2026 — when the final piece (#6878) merged and the feature was announced internally. `mintlify broken-links` passes. | 1 个月前 | |
docs: changelog for audit trail, agent sessions beta, new pricing, and August roundup (#7409) ## Description Four new changelog entries: - **Audit trail (Sep 3)** — control-plane audit trail, Enterprise plan, with a dashboard screenshot. - **Agent sessions public beta (Sep 2)** — session model (tenant / toolset / discovery) and the dedicated MCP server, linking to the new guide. - **Simpler plans, lower prices (Sep 2)** — 71% lower connection price, simpler plans, credits included. - **August 2026 roundup (Sep 1)** — 49 new APIs and new blog posts (listicles/comparisons excluded). Also includes a re-exported `account-api-keys.png` (smaller file, same content). `mintlify broken-links` passes; all 49 provider pages verified under `/api-integrations/`. No llms regen needed (changelog content is not embedded in the LLM indexes). Closes CON-222 <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7409?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 10 天前 | |
docs: add changelog entries for account API keys, team join at signup, and Japanese Connect UI (#7234) Adds three changelog entries for recently shipped features: - **Account API keys & environment management API** (Aug 21) — new account-scoped API keys managed from the profile menu, and public endpoints to create/delete environments and their Environment API keys (#7025, #6973, #7007, docs in #7148). - **Join your team at signup** (Aug 4) — new signups with a matching email domain are offered to join the existing account instead of creating a duplicate (#6879, invite prefill in #7093). - **Japanese support in the Connect UI** — adds `ja` alongside en/fr/de/es, settable via the `lang` parameter of `openConnectUI` (#6721). Each entry includes a dashboard/Connect UI screenshot. `mintlify broken-links` passes: `success no broken links found`. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7234?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 20 天前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: add screenshot to the agent sessions changelog entry (#7411) ## Description Adds a screenshot to the agent sessions changelog entry: an AI agent working a support ticket through tools exposed by an agent session. Follow-up to #7409. `mintlify broken-links` passes. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7411?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 10 天前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: add product changelog update for API keys (CON-60) (#5932) ## Summary - Adds an Apr 22, 2026 changelog entry to `docs/updates/product.mdx` announcing the move from environment secret keys to scoped API keys. - Covers scoped permissions, safe rotation, RBAC visibility for the Support role, and the "no migration required" default key. - Links to the [API keys reference](/reference/api-keys) for the full scope list and advised profiles. - Adds `docs/images/changelog/api-keys.jpg` for the entry. | 4 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: changelog for audit trail, agent sessions beta, new pricing, and August roundup (#7409) ## Description Four new changelog entries: - **Audit trail (Sep 3)** — control-plane audit trail, Enterprise plan, with a dashboard screenshot. - **Agent sessions public beta (Sep 2)** — session model (tenant / toolset / discovery) and the dedicated MCP server, linking to the new guide. - **Simpler plans, lower prices (Sep 2)** — 71% lower connection price, simpler plans, credits included. - **August 2026 roundup (Sep 1)** — 49 new APIs and new blog posts (listicles/comparisons excluded). Also includes a re-exported `account-api-keys.png` (smaller file, same content). `mintlify broken-links` passes; all 49 provider pages verified under `/api-integrations/`. No llms regen needed (changelog content is not embedded in the LLM indexes). Closes CON-222 <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7409?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 10 天前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: changelog for Management MCP tools, connection recovery webhook, and 2FA on password changes (#7238) ## Description Adds three changelog entries: - **New Management MCP tools** (Aug 25) — the Management MCP server now exposes 14 tools: integrations CRUD, connections, connect sessions, proxy requests, functions, and the new documentation tools (#6977–#7182, #7211). - **Connection recovery webhook** (Aug 24) — a follow-up webhook with `"success": true` when a token refresh succeeds after a previous failure (#7202). - **2FA on password changes** (Aug 20) — changing or resetting a password now requires an authenticator code when 2FA is enabled (#7110). Also reorders the recently added Japanese Connect UI and Account discovery entries so dates stay newest-first. Each entry includes a screenshot where relevant. `mintlify broken-links` passes: `success no broken links found`. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7238?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 20 天前 | |
docs: add changelog entry for dashboard password change (#7141) ## Description Adds a changelog entry for the password change feature shipped in #6931: accounts that sign in with email and password can now change their password from Profile settings in the dashboard. Includes a screenshot of the change password dialog. [Loom demo](https://www.loom.com/share/cb8e36ecd6a9445ca28f5b102ca4ac6e) `mintlify broken-links` passes: `success no broken links found`. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7141?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 28 天前 | |
docs: add changelog entries for account API keys, team join at signup, and Japanese Connect UI (#7234) Adds three changelog entries for recently shipped features: - **Account API keys & environment management API** (Aug 21) — new account-scoped API keys managed from the profile menu, and public endpoints to create/delete environments and their Environment API keys (#7025, #6973, #7007, docs in #7148). - **Join your team at signup** (Aug 4) — new signups with a matching email domain are offered to join the existing account instead of creating a duplicate (#6879, invite prefill in #7093). - **Japanese support in the Connect UI** — adds `ja` alongside en/fr/de/es, settable via the `lang` parameter of `openConnectUI` (#6721). Each entry includes a dashboard/Connect UI screenshot. `mintlify broken-links` passes: `success no broken links found`. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7234?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 20 天前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: add June 2026 changelog entries (#6685) Add three changelog entries: - June 2026 roundup (37 new APIs + 5 blog posts) - Synced records view — connection Records tab - In-app chat support <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6685?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 2 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: add changelog entries for Management MCP, editable tags/metadata, CIMD (#6821) Adds three changelog entries: - **Management MCP server (Beta)** — hosted at `mcp.nango.dev/mcp`, launching with the logs tools (`logs_list_operations`, `logs_get_operation`), authenticated with an API key using the `environment:logs:read` scope. Includes a screenshot of Claude Code querying Nango logs through it. - **Editable connection tags and metadata** — both are now editable from a connection's Auth tab in the dashboard. Connection config editing was cut from the original PR (#6760) and is intentionally not mentioned. Includes an annotated screenshot. - **CIMD support for MCP auth** — the generic MCP integration now uses Client ID Metadata Documents when the authorization server supports them, with dynamic client registration as the fallback (#6708). Validation: - `mintlify broken-links`: success, no broken links found (covers links, anchors, and image paths) - Prettier passes; no `llms.txt` regen needed for a content-only changelog change CON-131: https://linear.app/nango/issue/CON-131/add-changelog-entry-for-cimd-for-mcp-logs-mcp-and-editing <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6821?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 1 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Changelog and Dev update for February 2026 (#5556) Add Product changelog and a Dev update for February 2026 CON-7 Preview Links: - Product - https://nango-con-7-prepare-monthly-announcements.mintlify.app/updates/product - Dev - https://nango-con-7-prepare-monthly-announcements.mintlify.app/updates/dev <!-- Summary by @propel-code-bot --> --- It adds a new product update section with integration listings, feature highlights, images, and blog links, plus a dev update entry describing sync checkpoints and migration guidance. <details> <summary><strong>Key Changes</strong></summary> • Added February 2026 product update content in `docs/updates/product.mdx`, including new integrations list, feature highlights, images, and blog links • Added February 2026 dev update entry covering checkpoints, migration guidance, and docs links in `docs/updates/dev.mdx` • Adjusted formatting and spacing across existing dev update entries in `docs/updates/dev.mdx` • Updated changelog images in `docs/images/changelog/hubspot-mcp-connect-ui.png` and `docs/images/changelog/nango-ai-integration-builder-cursor.png` </details> <details> <summary><strong>Possible Issues</strong></summary> • Checkpoint example uses `contacts.at(-1)` without guarding for empty arrays, which could throw if no records are returned. • New links or image paths could render incorrectly if paths or titles are inconsistent. </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: add June 2026 changelog entries (#6685) Add three changelog entries: - June 2026 roundup (37 new APIs + 5 blog posts) - Synced records view — connection Records tab - In-app chat support <!-- Describe the problem and your solution --> <!-- Issue ticket number and link (if applicable) --> <!-- Testing instructions (skip if just adding/editing providers) --> <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6685?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 2 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: changelog for light mode (#6505) Added changelog for light mode on the Nango dashboard. fixes CON-112 <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6505?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> --------- Co-authored-by: cubic-dev-ai[bot] <191113872+cubic-dev-ai[bot]@users.noreply.github.com> | 2 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: changelog for Management MCP tools, connection recovery webhook, and 2FA on password changes (#7238) ## Description Adds three changelog entries: - **New Management MCP tools** (Aug 25) — the Management MCP server now exposes 14 tools: integrations CRUD, connections, connect sessions, proxy requests, functions, and the new documentation tools (#6977–#7182, #7211). - **Connection recovery webhook** (Aug 24) — a follow-up webhook with `"success": true` when a token refresh succeeds after a previous failure (#7202). - **2FA on password changes** (Aug 20) — changing or resetting a password now requires an authenticator code when 2FA is enabled (#7110). Also reorders the recently added Japanese Connect UI and Account discovery entries so dates stay newest-first. Each entry includes a screenshot where relevant. `mintlify broken-links` passes: `success no broken links found`. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/7238?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 20 天前 | |
docs: Changelog and Dev update for February 2026 (#5556) Add Product changelog and a Dev update for February 2026 CON-7 Preview Links: - Product - https://nango-con-7-prepare-monthly-announcements.mintlify.app/updates/product - Dev - https://nango-con-7-prepare-monthly-announcements.mintlify.app/updates/dev <!-- Summary by @propel-code-bot --> --- It adds a new product update section with integration listings, feature highlights, images, and blog links, plus a dev update entry describing sync checkpoints and migration guidance. <details> <summary><strong>Key Changes</strong></summary> • Added February 2026 product update content in `docs/updates/product.mdx`, including new integrations list, feature highlights, images, and blog links • Added February 2026 dev update entry covering checkpoints, migration guidance, and docs links in `docs/updates/dev.mdx` • Adjusted formatting and spacing across existing dev update entries in `docs/updates/dev.mdx` • Updated changelog images in `docs/images/changelog/hubspot-mcp-connect-ui.png` and `docs/images/changelog/nango-ai-integration-builder-cursor.png` </details> <details> <summary><strong>Possible Issues</strong></summary> • Checkpoint example uses `contacts.at(-1)` without guarding for empty arrays, which could throw if no records are returned. • New links or image paths could render incorrectly if paths or titles are inconsistent. </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: add changelog entries for Management MCP, editable tags/metadata, CIMD (#6821) Adds three changelog entries: - **Management MCP server (Beta)** — hosted at `mcp.nango.dev/mcp`, launching with the logs tools (`logs_list_operations`, `logs_get_operation`), authenticated with an API key using the `environment:logs:read` scope. Includes a screenshot of Claude Code querying Nango logs through it. - **Editable connection tags and metadata** — both are now editable from a connection's Auth tab in the dashboard. Connection config editing was cut from the original PR (#6760) and is intentionally not mentioned. Includes an annotated screenshot. - **CIMD support for MCP auth** — the generic MCP integration now uses Client ID Metadata Documents when the authorization server supports them, with dynamic client registration as the fallback (#6708). Validation: - `mintlify broken-links`: success, no broken links found (covers links, anchors, and image paths) - Prettier passes; no `llms.txt` regen needed for a content-only changelog change CON-131: https://linear.app/nango/issue/CON-131/add-changelog-entry-for-cimd-for-mcp-logs-mcp-and-editing <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6821?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 1 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: changelog for agent-led onboarding, JIT APIs (#6313) Preview: https://nango-sapnesh-con-90-announce-new-onboarding-flow-and-remot.mintlify.app/updates/changelog Adds a new changelog entry (dated **June 1, 2026**) to `docs/updates/changelog.mdx` announcing the recently public agent-led onboarding flow and remote function building, plus the May roundup: - **Agent-led onboarding** — the AI-assisted quickstart: paste the quickstart prompt into a coding agent (Claude, Cursor, Codex, …) to get walked through signup, API key setup, connection authorization, and the first function call. Includes a screenshot. - **Agents can build and deploy integrations (just-in-time)** — coding agents, and agents inside your product, can build, test, and deploy integrations through the Functions API without a local project, via the new Remote Function Builder skill and the compile / dry run / deploy endpoints. - **50 new APIs in May** — monthly provider roundup. - **New blog posts** — 6 recent posts from the team. Implements [CON-90](https://linear.app/nango/issue/CON-90/announce-new-onboarding-flow-and-remote-functions-docs). --------- Co-authored-by: Bastien Beurier <bastienbeurier@gmail.com> | 3 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: product chnagelog update for Playground (#5868) For: https://linear.app/nango/issue/CON-49/playground-release-notes-update Preview Link: https://nango-con-49-playground-release-notes-update.mintlify.app/getting-started/intro-to-nango ## Summary - Add April 14, 2026 changelog entry for the new Playground feature - Covers: integration/connection/function selection, input validation, inline results, log navigation, and RBAC gating ## Test plan - [x] Verify the changelog renders correctly on the docs site - [x] Confirm doc links resolve: `/guides/primitives/functions#actions`, `/guides/primitives/functions#syncs`, `/guides/platform/logging`, `/guides/platform/security#team-and-roles` | 4 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: add March 2026 product changelog: RBAC, 34 new APIs, blog posts (#5768) ## Summary - Add March 2026 product changelog with RBAC, 34 new APIs, and blog posts ## Tests - Verify changelog renders correctly at `/updates/product` - Verify all 34 API links resolve - Verify changes look ok in the preview URL Ticket: https://linear.app/nango/issue/NAN-5167/march-feature-announcements Preview: https://nango-nan-5167-march-feature-announcements.mintlify.app/updates/product#march-27-2026 <!-- Summary by @propel-code-bot --> --- This change specifically adds a new March 27, 2026 section at the top of the product updates doc and is strictly a documentation update for display on `/updates/product`, with no runtime, API, or backend/frontend behavior changes. It also introduces a supporting changelog image asset alongside the new content. --- *This summary was automatically generated by @propel-code-bot* | 5 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: CON-6/backfill-product-updates - October, November, December 25 and January 26 (#5520) Summary: - Added changelogs for Oct, Nov, Dec 2025, and Jan 2026. - Included New APIs, Features, and Blog Posts for each month. - Verified all links (APIs and docs); no company updates included. Preview link: https://nango-con-6-backfill-product-updates.mintlify.app/updates/product Editor Feedback (Mintlify WYSIWYG) Tried out the new Mintlify web editor! Accessible from the Mintlify dashboard It's solid, with a few minor quirks: - Attribution: Commits show as Mintlify[bot] instead of my GH user. I'll check if this can be changed. - Messages: Couldn't find a way to customize the commit message on save. - Diff: The product.mdx diff shows more changes than intended because inserting at the top shifted/reformatted existing lines. I've verified that all older content is still intact and unchanged. <!-- mintlify-editor-comments:start --> Mintlify --- 0 threads from 0 users in Mintlify - No unresolved comments <!-- mintlify-editor-comments:end --> <!-- mintlify-comment--> <a href="https://dashboard.mintlify.com/nango/nango/editor/CON-6%2Fbackfill-product-updates?source=pr_comment" target="_blank" rel="noopener noreferrer"><picture><source media="(prefers-color-scheme: dark)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg"><img src="https://d3gk2c5xim1je2.cloudfront.net/assets/open-mintlify-editor-light.svg" alt="Open in Mintlify Editor"></picture></a> <!-- /mintlify-comment --> <!-- Summary by @propel-code-bot --> --- The update also reorganizes existing 2024–2025 entries to maintain chronological order and applies consistent formatting across update blocks, images, and separators in `docs/updates/product.mdx`, focusing purely on documentation presentation while preserving existing content. <details> <summary><strong>Possible Issues</strong></summary> • January 2026 section references “37 new APIs in December,” which may be a month mismatch • Mixed image paths (e.g., `../images/...` vs `/images/...`) could break under `/updates/product` • Potential typo in image filename `advanced-sonnection-settings.gif` • Headings immediately following `</AccordionGroup>` may affect MDX rendering • Horizontal rules `---` inside update blocks could alter spacing or component rendering • Existing typos remain (e.g., “environemnts”, “achived”, “ouputs”, “periodicaly”) • Integration link path inconsistencies (`/api-integrations/*` vs `/integrations/all/*`) could cause 404s </details> --- *This summary was automatically generated by @propel-code-bot* --------- Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com> | 6 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 | |
docs: add changelog entry for usage breakdowns (#6658) Adds a changelog entry announcing usage breakdowns on the Billing & usage page. Fixes: CON-126 Preview: https://nango-sapnesh-con-122-changelog-for-billing-usage-charts.mintlify.app/updates/changelog#usage-breakdowns ### Validation - `mintlify broken-links`: success, no broken links found. - No `llms.txt` regen needed — content-only changelog entry; nav and frontmatter unchanged. <!-- This is an auto-generated description by cubic. --> <a href="https://cubic.dev/pr/NangoHQ/nango/pull/6658?utm_source=github" target="_blank" rel="noopener noreferrer" data-no-image-dialog="true"><picture><source media="(prefers-color-scheme: dark)" srcset="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"><source media="(prefers-color-scheme: light)" srcset="https://www.cubic.dev/buttons/review-in-cubic-light.svg"><img alt="Review in cubic" src="https://www.cubic.dev/buttons/review-in-cubic-dark.svg"></picture></a> <!-- End of auto-generated description by cubic. --> | 2 个月前 | |
docs: Rename docs-v2 to docs (#4855) Change name of the root folder for docs <!-- Summary by @propel-code-bot --> --- **Rename Documentation Root Directory from `docs-v2` to `docs`** This pull request renames the root documentation directory from `docs-v2` to `docs` and updates all internal references accordingly. The update is a structural change that standardizes the main documentation folder and all internal edit/contribution links, ensuring consistency across the project. No documentation content or code has been changed except for the updated references and reorganization. <details> <summary><strong>Key Changes</strong></summary> • Renamed documentation root directory from `docs-v2` to `docs`. • Updated all documentation files and internal edit/contribution links to point to the new `docs/` directory. • Reorganized the docs structure so that all files and subdirectories previously under `docs-v2/` now reside under `docs/`. • Adjusted any hard-coded paths within markdown files (e.g., edit/contribution links) from `docs-v2` to `docs` throughout the documentation. </details> <details> <summary><strong>Affected Areas</strong></summary> • `docs-v2/` (now renamed to `docs/`) • All documentation markdown (`.mdx`) files referencing the docs root folder • Paths within contribution, edit, and helper links in documentation • Any tooling, scripts, or integrations that rely on the previous docs path (potentially in CI, build pipelines, or static site generators) </details> --- *This summary was automatically generated by @propel-code-bot* | 10 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 1 个月前 | ||
| 10 天前 | ||
| 20 天前 | ||
| 6 个月前 | ||
| 10 天前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 4 个月前 | ||
| 10 个月前 | ||
| 10 天前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 20 天前 | ||
| 28 天前 | ||
| 20 天前 | ||
| 10 个月前 | ||
| 2 个月前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 1 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 2 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 2 个月前 | ||
| 10 个月前 | ||
| 20 天前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 6 个月前 | ||
| 1 个月前 | ||
| 10 个月前 | ||
| 3 个月前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 4 个月前 | ||
| 10 个月前 | ||
| 5 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 6 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 10 个月前 | ||
| 2 个月前 | ||
| 10 个月前 |
