*** We overhauled the underlying execution infrastructure to be fully serverless. [Function](/guides/functions/functions-guide) executions now run in isolated AWS Lambda environments rather than using a single VM per customer. This provides dedicated resources and an isolated runtime for every Function execution, significantly improving tenant isolation, execution fairness, reliability, and performance scaling. This change is at the infrastructure level; your function code and APIs are unaffected. *** We released a new AI skill for writing and testing Nango [Actions](/getting-started/use-cases/actions) & [Syncs ](/getting-started/use-cases/syncs)using your favorite AI coding agent. The skill is compatible with over 18 different AI frameworks, including Claude Code, Cursor, GitHub Copilot, Gemini CLI, Codex, OpenCode, and more. Building Nango integrations with Cursor

See the [Functions guide](/guides/functions/functions-guide#guide) for instructions on building integrations with AI. *** We added full platform support for Model Context Protocol (MCP) Auth integrations, starting with [HubSpot MCP](/api-integrations/hubspot-mcp) and [Granola MCP](/api-integrations/granola-mcp).\ You can now authenticate and connect your AI Agents with providers that support MCP Auth. Hubspot Mcp Connect Ui

*** * [3CX](/api-integrations/3cx) * [8x8](/api-integrations/8x8) * [Adobe Commerce](/api-integrations/adobe-commerce) * [Atlassian Service Account (API Token)](/api-integrations/atlassian-service-account-api-token) * [Atlassian Service Account (OAuth 2.0)](/api-integrations/atlassian-service-account-oauth2) * [Bird](/api-integrations/bird) * [Canvas LMS](/api-integrations/canvas-lms) * [Cloudbeds](/api-integrations/cloudbeds) * [Constant Contact](/api-integrations/constant-contact) * [DemoDesk](/api-integrations/demodesk) * [Crisp (Plugin Install)](/api-integrations/crisp-plugin-install) * [ECU360 (Test)](/api-integrations/ecu360) * [ECU360 (Production)](/api-integrations/ecu360-production) * [FreeAgent](/api-integrations/freeagent) * [FreeAgent (Sandbox)](/api-integrations/freeagent-sandbox) * [Google Meet](/api-integrations/google-meet) * [Greenhouse Harvest Partner (V3)](/api-integrations/greenhouse-harvest-partner) * [Greenhouse Harvest (Client Credentials V3)](/api-integrations/greenhouse-harvest-oauth2-cc) * [Looker](/api-integrations/looker) * [Meta Marketing API](/api-integrations/meta-marketing-api) * [Juniper Mist](/api-integrations/juniper-mist) * [Mollie](/api-integrations/mollie) * [ModMed](/api-integrations/modmed) * [Nerdio](/api-integrations/nerdio) * [nocrm.io](/api-integrations/nocrm) * [Oomnitza](/api-integrations/oomnitza) * [Perdoo](/api-integrations/perdoo) * [Pylon](/api-integrations/pylon) * [Procore](/api-integrations/procore) * [Reapit Connect](/api-integrations/reapit) * [Schwab](/api-integrations/schwab) * [ServiceNow (Client Credentials)](/api-integrations/servicenow-oauth2-cc) * [Stripe (API Key)](/api-integrations/stripe-api-key) * [Wiseagent](/api-integrations/wiseagent) * [WorkOS](/api-integrations/workos) * [Workday (Refresh Token Auth)](/api-integrations/workday-refresh-token) * [Wise (API Key)](/api-integrations/wise-api-key) ## New blog posts We published a series of debugging guides detailing what causes OAuth refresh token `invalid_grant` or `BAD_REFRESH_TOKEN` errors and how to fix them across various providers: * [QuickBooks OAuth refresh token invalid\_grant](https://www.nango.dev/blog/quickbooks-oauth-refresh-token-invalid-grant) * [Airtable OAuth refresh token invalid\_grant](https://www.nango.dev/blog/airtable-oauth-refresh-token-invalid-grant) * [GitHub App OAuth BAD\_REFRESH\_TOKEN](https://www.nango.dev/blog/github-app-oauth-refresh-token-bad-refresh-token) * [Microsoft OAuth refresh token invalid\_grant](https://www.nango.dev/blog/microsoft-oauth-refresh-token-invalid-grant) * [LinkedIn OAuth refresh token invalid\_grant](https://www.nango.dev/blog/linkedin-oauth-refresh-token-invalid-grant) * [Slack OAuth refresh token invalid\_grant](https://www.nango.dev/blog/slack-oauth-refresh-token-invalid-grant) * [Stripe OAuth refresh token invalid\_grant](https://www.nango.dev/blog/stripe-oauth-refresh-token-invalid-grant) * [Shopify OAuth refresh token invalid\_grant](https://www.nango.dev/blog/shopify-oauth-refresh-token-invalid-grant) * [Xero OAuth refresh token invalid\_grant](https://www.nango.dev/blog/xero-oauth-refresh-token-invalid-grant) * [Linear OAuth refresh token invalid\_grant](https://www.nango.dev/blog/linear-oauth-refresh-token-invalid-grant) * [PostHog OAuth refresh token invalid\_grant](https://www.nango.dev/blog/posthog-oauth-refresh-token-invalid-grant) * [Notion OAuth refresh token invalid\_grant](https://www.nango.dev/blog/notion-oauth-refresh-token-invalid-grant) * [Zendesk OAuth refresh token invalid\_grant](https://www.nango.dev/blog/zendesk-oauth-refresh-token-invalid-grant) * [Jira OAuth refresh token invalid\_grant](https://www.nango.dev/blog/jira-oauth-refresh-token-invalid-grant) * [Gong OAuth refresh token invalid\_grant](https://www.nango.dev/blog/gong-oauth-refresh-token-invalid-grant) * [Confluence OAuth refresh token invalid\_grant](https://www.nango.dev/blog/confluence-oauth-refresh-token-invalid-grant) ***

We added automatic data retention policies for records stored in the Nango sync cache. These policies apply to synced records produced by syncs (our replication-oriented functions) and ensure that record payloads are not retained indefinitely. **Retention lifecycle:** 1. **Automated payload pruning.** If a record has not been updated for **30 days**, Nango automatically prunes its payload. The record still exists and its metadata remains intact, including record ID, sync state, and payload hash (used for change detection). After pruning, the record's data fields are no longer retrievable from the Nango cache, but Nango can still track the record and detect future changes. This pruning does not impact sync execution or delta-detection. 2. **Automated hard deletion.** If a sync has not executed for **60 days**, records belonging to that sync will be permanently deleted (payload and metadata). **Timeline:** Policies start on **January 8, 2026**. Record payload pruning starts **30 days later**. Record hard deletion for inactive syncs starts **60 days later**. **Am I impacted?** Most customers (including most sync users) are not impacted, in particular if you use syncs for replication, receive updates via Nango webhooks, and replicate records into your own system shortly after they arrive in the Nango cache. You are impacted if you use Nango sync's cache as a long-term persistent data store, reading or editing record payloads from the Nango cache long after they were updated. **What to do:** If you fetch record payloads from Nango long after they were updated (30+ days), reach out. We will make sure you do not experience breaking changes. **Why:** These retention policies are part of our broader commitment to helping customers meet modern data compliance and security expectations. They ensure that sensitive user data is not stored indefinitely in the Nango sync cache when it is no longer needed for syncing. See the [Records cache documentation](/guides/functions/syncs/records-cache). We also introduced a new endpoint to manually prune records. You can use `PATCH /records/prune` to empty record payloads on demand while preserving the metadata. See the [Prune records API reference](/reference/backend/http-api/sync/prune-records). *** You can now authenticate with Salesforce using the JWT Bearer flow. This enables server-to-server authentication using a dedicated "API user" inside the customer's Salesforce org.

This auth mode bypasses the interactive OAuth consent screen, which enterprise customers often prefer for easier onboarding and stronger governance. See the [Salesforce JWT documentation](/api-integrations/salesforce-jwt) for the setup guide and implementation snippets. *** You can now generate and copy a shareable Connect UI link directly from the Nango dashboard. This enables you to create a link in Nango and share it with another person to complete the auth flow.

The UI displays an expiry notification when you copy the link to your clipboard. Links expire after 30 minutes. *** We updated the Authorization flow UI to optimize the layout for mobile/tablet devices. Nango Auth Mobile Support

*** Nango webhooks now include a new `X-Nango-Hmac-Sha256` header that uses HMAC-SHA256 for improved security. The legacy `X-Nango-Signature` header (plain SHA-256 with key concatenation) is still sent for backwards compatibility but should no longer be used. HMAC-SHA256 is cryptographically more secure than plain SHA-256 with concatenation. HMAC provides better protection against length extension attacks and is the industry standard for webhook signature verification. **Timeline:** * **Now available:** The `X-Nango-Hmac-Sha256` header is already included in all webhook requests. * The `X-Nango-Signature` header will continue to be sent for backwards compatibility, with no current deprecation timeline. **Am I impacted?** * If you currently verify webhooks using the `X-Nango-Signature` header. * If you are implementing webhook verification for the first time. **For new integrations:** verify webhook signatures using the `X-Nango-Hmac-Sha256` header. See the updated [webhook documentation](/guides/platform/webhooks-from-nango#verifying-webhooks-from-nango) for code examples. **For existing integrations:** migrate to `X-Nango-Hmac-Sha256` when convenient. The old `X-Nango-Signature` header will continue to work, but we recommend migrating for better security. *** * [Availity](/api-integrations/availity) * [BetterContact](/api-integrations/bettercontact) * [ConductorOne](/api-integrations/conductorone) * [Drata](/api-integrations/drata) * [Fanvue](/api-integrations/fanvue) * [Fathom (OAuth)](/api-integrations/fathom-oauth) * [Firstbase](/api-integrations/firstbase) * [Google Search Console](/api-integrations/google-search-console) * [Grist](/api-integrations/grist) * [Justworks](/api-integrations/justworks) * [Lumos](/api-integrations/lumos) * [Onlogist](/api-integrations/onlogist) * [Oracle Cloud Identity](/api-integrations/oracle-cloud-identity) * [Paylocity (NextGen)](/api-integrations/paylocity-nextgen) * [Recall.ai](/api-integrations/recall-ai) * [SAP S/4HANA Cloud (Client Credentials)](/api-integrations/sap-odata-oauth2-cc) * [SAP S/4HANA Cloud (Basic Auth)](/api-integrations/sap-odata-basic) * [Slab](/api-integrations/slab) * [Sophos Central](/api-integrations/sophos-central) * [Torii](/api-integrations/torii) * [Vanta](/api-integrations/vanta) * [Veeva Vault](/api-integrations/veeva-vault) ## New blog posts New posts from the Nango team in December: * [Finding traction without a product: Our process](https://www.nango.dev/blog/our-process-for-finding-initial-traction-pre-product) * [How to find the best integrations partner](https://www.nango.dev/blog/how-to-find-the-best-integrations-partner) *** Connections now support tags. Tags are key/value strings you attach when creating a Connect session to tie a Nango connection to a specific user, organization, or entity in your system. When a user completes an auth flow, Nango copies these tags to the resulting connection and includes them in the success webhook. This replaces the need for the legacy `end_user` and `organization` objects. Tags also enhance the Nango UI: * `end_user_display_name` and `end_user_email` are shown directly in the connections list. * The domain from the `end_user_email` is used to automatically display the corresponding company logo on the connection detail page. Connection Tags Ui

You can also filter connections by tags via the API. See the [Connection tags documentation](/guides/auth/connection-tags-configuration-metadata). **Migration Note:** If you currently use `end_user` or `organization` in Connect sessions or webhooks, follow the [migration guide](/guides/platform/migrations/migrate-from-end-user) to move to tags. *** We rebuilt the callback experience to provide better visibility into OAuth errors. Provider error messages are now rendered directly inside the Connect UI form and the pop-up window. Enhanced OAuth error messaging

The new UI for the callback renders structured success and error states. It also surfaces provider query parameters in an expandable debug panel. Additionally, provider errors are now delivered via WebSocket for improved logging on your end. *** We have overhauled the Integrations tab to streamline how you manage and scale your catalog. This update focuses on faster discovery and a more intuitive setup flow. * **Improved Search:** The search on the Integrations page now considers display names, auth modes, and categories to bring you the most relevant results.

* **Decoupled Creation Flow:** Selecting an API in the catalog now leads to a dedicated form where you configure credentials (Client ID, Secret, Scopes) before the integration is created. This prevents empty integrations from cluttering your dashboard. * **Improved Navigation:** Added breadcrumbs to the header for better context in nested routes and a new search bar for your active integrations list.

*** New behavior: * **Timeout:** 20s (instead of 60s) * **Retries:** 2 (instead of 7) Effective **December 3, 2025**. **Am I impacted?** Most customers — in particular anyone consuming webhooks for auth, syncs, async actions, or webhook forwards. **Action required:** None. **Why:** The previous long timeout and many retries created incidents when webhook endpoints were unavailable. The new behavior is in line with other popular APIs (e.g., Stripe, Hubspot). *** * [Apify](/integrations/all/apify) * [Auvik](/integrations/all/auvik) * [Breezy HR](/integrations/all/breezy-hr) * [CrowdStrike](/integrations/all/crowdstrike) * [Cursor Admin](/integrations/all/cursor-admin) * [Crisp](/integrations/all/crisp) * [DrChrono](/integrations/all/drchrono) * [ContactOut](/integrations/all/contactout) * [Fellow](/api-integrations/fellow) * [GitLab (Personal Access Token)](/integrations/all/gitlab-pat) * [HeyReach](/integrations/all/heyreach) * [Icypeas](/integrations/all/icypeas) * [LeadMagic](/integrations/all/leadmagic) * [Mimecast](/integrations/all/mimecast) * [NinjaOne RMM](/integrations/all/ninjaone-rmm) * [Passportal](/integrations/all/passportal) * [Rocketlane](/integrations/all/rocketlane) * [Prospeo](/api-integrations/prospeo) * [PracticeFusion](/api-integrations/practicefusion) * [Semrush (v3)](/integrations/all/semrush) * [Shipstation (v2)](/integrations/all/shipstation-v2) * [TikTok Personal](/integrations/all/tiktok-personal) * [Valley (API Key)](/integrations/all/valley-api-key) * [Valley (OAuth)](/integrations/all/valley) * [Wiza](/integrations/all/wiza) * [Zendesk Sell](/integrations/all/zendesk-sell) * [Zoho Recruit](/integrations/all/zoho-recruit) ## New blog posts New posts from the Nango team in November: * [How to build integrations you and your customers love](https://www.notion.so/blog/how-to-build-integrations-you-and-your-customers-love) * [The hidden costs of building product integrations in-house](https://www.notion.so/blog/the-hidden-costs-of-building-product-integrations-in-house) * [Product integrations: Build or buy?](https://www.notion.so/blog/product-integrations-build-or-buy) *** You can now set advanced configurations directly in the Nango UI when creating a connection. This form is split into two distinct sections. Firstly, you can specify end-user data. This includes setting a custom ID, email, and display name for the connection. Advanced connection settings

Secondly, you can also override the integration's default configuration, like authorization parameters, customize OAuth scopes, and override developer app credentials. This allows you to test connections and initiate the authorization flow even if default credentials are not fully configured in your environment. *** The [Nango CLI](/reference/functions/functions-cli) now includes a `nango clone` command. This automates the process of pulling function templates and their dependencies from the Nango integration templates repository. This replaces the manual process of copying and pasting configuration and TypeScript code. You can clone an entire integration directory, a specific category of functions, or an individual template. ```bash theme={null} nango clone github nango clone github/actions nango clone github/actions/list-repos ``` See the guide on [customizing a function template](/guides/functions/functions-guide#guide). *** We’ve improved how the Nango CLI detects and interacts with your environment, specifically for non-NPM setups: * **Monorepo detection**: The CLI now traverses parent directories to find your lockfile or `package.json`. If you run `nango init` in a subdirectory, it will correctly identify and use your root `pnpm`, `yarn`, or `bun` configuration. * **Opt-out of auto-installs**: To prevent the CLI from modifying `package.json` in sensitive environments (like CI or projects using pnpm catalogs), use the new `--no-dependency-update` flag or set the `NANGO_CLI_DEPENDENCY_UPDATE=false` environment variable. * **Yarn compatibility**: `nango init` now works out of the box for Yarn users, correctly flagging projects as standalone and using the `node-modules` linker. *** Function custom logs are calls to `nango.log(...)` in your functions (action functions, sync functions, webhook functions, and event functions). Starting in November, only `warn` and `error` level logs will be ingested by default for remote environments. Debug and info level logs will no longer be ingested automatically. When you call `nango.log(...)` without an explicit level (which defaults to `info`), these logs will not appear in the Nango UI logs tab for remote environments. All function custom logs, regardless of log level, will continue to surface in your local console when using the `nango dryrun` CLI command. Effective **November 1, 2025**. **Am I impacted?** * If you use custom logs in your syncs and actions with `nango.log(...)`. * If you rely on viewing debug and info level logs in the Nango UI logs tab for remote environments. ### Keeping logs visible in the Nango UI **Option 1: Raise the log level on individual calls** ```ts theme={null} nango.log('Important information', { level: 'warn' }); nango.log('Critical error occurred', { level: 'error' }); ``` **Option 2: Set a minimum level for the entire function run** ```ts theme={null} nango.logger({ level: 'info' // info-level logs and above (warn & error) will be indexed }); // Now all your regular nango.log() calls will be ingested nango.log('This will now appear in the UI'); ``` **Option 3: Set an environment variable to revert to the original behavior** While this is the simplest way to restore the previous behavior, we recommend Options 1 or 2 for better cost control. In your environment settings in the Nango UI, create an environment variable with key `NANGO_LOGGER_LEVEL` and value `'info'` (or `'debug'`, `'warn'`, `'error'`). **Warning:** Option 3 ingests all function logs across all syncs and actions. Carefully monitor your log volume starting in November to avoid unexpectedly high bills. **Important notes:** * Options 1 and 2 require changes in your function code and must be deployed using the Nango CLI. * Option 3 can be configured directly in the Nango UI without code changes. * Local development is unaffected — all logs continue to appear when using `nango dryrun`. * This change helps ensure you're only billed for logs you actively use in production. **Why:** Many customers generate a large number of custom logs for local development purposes without using them in remote environments. With the new pricing model starting in November (which includes generous included usage for function custom logs), this change ensures that customers don't get billed for logs they're not actively using. *** * [Adobe Workfront](/integrations/all/adobe-workfront) * [Affinity (v2)](/integrations/all/affinity-v2) * [Aimfox](/integrations/all/aimfox) * [Aimfox (OAuth)](/integrations/all/aimfox-oauth) * [Atlassian Government Cloud](/integrations/all/atlassian-government-cloud) * [Folk](/api-integrations/folk) * [Ironclad](/integrations/all/ironclad) * [Loop Returns](/integrations/all/loop-returns) * [MCP Server OAuth2 (Generic)](/integrations/all/mcp-generic) * [Microsoft (Admin)](/integrations/all/microsoft-admin) * [Microsoft Excel](/integrations/all/microsoft-excel) * [Momentum.io](/integrations/all/momentum-io) * [OneDrive Personal](/integrations/all/one-drive-personal) * [OneLogin](/integrations/all/onelogin) * [Pennylane (Company API)](/integrations/all/pennylane-company-api) * [PingOne](/integrations/all/pingone) * [PingOne (Client Credentials)](/integrations/all/pingone-cc) * [SAP Fieldglass](/integrations/all/sap-fieldglass) * [SAP Business One](/integrations/all/sap-business-one) * [Statista](/integrations/all/statista) * [Streak](/api-integrations/streak) * [Teamleader Focus](/integrations/all/teamleader) * [Snipe-IT](/integrations/all/snipe-it) ## New blog posts New posts from the Nango team in October: * [Best practices for building a unified API](https://www.nango.dev/blog/best-practices-build-unified-api) * [HubSpot OAuth BAD\_REFRESH\_TOKEN — What it means & how to fix it](https://www.nango.dev/blog/hubspot-oauth-bad-refresh-token) * [Best iPaaS for API Unification](https://www.nango.dev/blog/best-ipaas-for-api-unification) * [Paragon's pricing: What You Should Know Before Signing Up](https://www.nango.dev/blog/paragon-pricing) * [Merge pricing: What you should know before you commit](https://www.nango.dev/blog/merge-pricing) * [The 4 most popular Paragon alternatives](https://www.nango.dev/blog/4-most-popular-paragon-alternatives) * [The 4 most popular Merge.dev alternatives](https://www.nango.dev/blog/4-most-popular-merge-dev-alternatives) *** The Nango CLI now supports an [interactive mode](/reference/functions/functions-cli#interactive-mode) that prompts for missing arguments. For example, run `nango create` without specifying the function type, integration, or name, and the CLI will ask for them. Interactive mode is on by default in interactive terminal sessions. Nango_CLI_interactive_mode

You can still provide all arguments upfront to skip prompts (e.g., for scripting): test `nango create --sync --integration my-api --name get-contacts` To turn off interactive mode, use the `--no-interactive` flag, or set the `CI` environment variable for CI/CD environments. *** We have moved from a multi-file mock format to a single `.test.json`. When you generate mocks for your Nango syncs or actions, a single `.test.json` file is generated next to your test file. The file contains input, output, Nango stubs, and API response mocks, organized by method and path. This keeps test data in one place, making tests easier to run and maintain. See [mock file structure](/guides/functions/testing#mock-file-structure). **Migration Note:** See [migrating from the old format](/guides/functions/testing#migrating-from-the-old-format) if you have tests still using the old multi-file mocks. *** * [CI/CD for Nango integrations](/guides/functions/ci-cd): A complete guide on integrating Nango into your CI/CD processes. *** Currently, if multiple connections share the same `end_user_id`, they also share the same end-user object in Nango. After the change, each connection will always get its own independent copy of the end-user object, even if they use the same `end_user_id`. We are changing the old behavior because it was confusing for some developers, and because it was impossible to declare multiple organizations for a given user. Effective **September 8, 2025** — end-user updates will stop being replicated across connections. **Am I impacted?** * If your users can be tied to multiple organizations. * If you were relying on end-user auto-replication to maintain data freshness. **What to do:** End-user fields are mostly for display and tagging purposes. * If you are not using them, you can safely ignore this update. * If you are using them and wish to keep them in sync across connections (e.g., display name), patch each connection when your end-user is updated on your side: ```ts theme={null} await nango.patchConnection({ connectionId, provider_config_key }, { end_user: { id: '123', email: 'new-email@nango.dev' } }); ``` If you don't keep them in sync, the only side effect is that data will be stale in the Nango platform. There is no batch endpoint for this operation. If you need one, please reach out on Slack. *** * [Addepar (OAuth)](/integrations/all/addepar) * [Addepar (Basic Auth)](/integrations/all/addepar-basic) * [ADP Lyric](/integrations/all/adp-lyric) * [ADP Workforce Now](/integrations/all/adp-workforce-now) * [Bullhorn](/integrations/all/bullhorn) * [Clerk](/integrations/all/clerk) * [Cursor](/integrations/all/cursor) * [DataCandy](/integrations/all/datacandy) * [Fillout (API Key)](/integrations/all/fillout-api-key) * [Fillout (Oauth)](/integrations/all/fillout) * [Google Workspace Admin](/api-integrations/google-workspace-admin) * [Google Service Account](/integrations/all/google-service-account) * [Hover](/integrations/all/hover) * [Jobber](/integrations/all/jobber) * [Kintone](/integrations/all/kintone) * [Kintone User API](/integrations/all/kintone-user-api) * [Pax8](/integrations/all/pax8) * [Recruitee](/integrations/all/recruitee) * [Sellsy](/integrations/all/sellsy) * [Sellsy (Client Credentials)](/integrations/all/sellsy-oauth2-cc) * [Skio](/integrations/all/skio) * [Snapchat (Ads API)](/integrations/all/snapchat) * [Tailscale (OAuth)](/integrations/all/tailscale) * [Tailscale (API Key)](/integrations/all/tailscale-api-key) * [Webex](/integrations/all/webex) ***

Customize the Connect UI, which your users see when they authorize integrations. We've added a dark mode and the ability to change the primary color to fit your brand. You can also toggle the light/dark mode based on the user's system preference. Access the Connect UI settings in your [Environment settings](https://app.nango.dev/dev/environment-settings). We will continue adding customization options over time. *** For APIs that don't support deletion detection, we've added a new interface to detect deletions on Nango's side when syncing data ([docs](/guides/functions/syncs/deletion-detection)). Inside your sync function, you can now call `nango.deleteRecordsFromPreviousExecutions('ModelName')` to detect deletions. Please note that you should only use this function if you are performing a full sync. If you are syncing data incrementally, you can periodicaly resync the whole dataset to benefit from deletion detection. *** We added the ability to customize the credentials verification script, which is called when a new connection is created. For this, use the new `validate-connection` hook ([docs](/guides/functions/event-functions)). This lets you verify your customers’ API credentials by testing them against specific endpoints that correspond to particular API scopes. *** Nango actions currently have a documented output limit of 10MB. We are further restricting that limit to 2MB. Instead of using an action for large payloads, use the Nango [proxy](/guides/platform/proxy-requests). We will also soon restrict action inputs, so please take note of your inputs. Effective **October 1, 2025** — actions exceeding the 2MB output limit will throw an error. **Am I impacted?** * If you use actions with heavy outputs. Typical large-output actions include [`fetch-attachment`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/outlook/actions/fetch-attachment.ts), [`fetch-call-transcripts`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/gong/actions/fetch-call-transcripts.ts), and in general anything fetching an object from an external system. We've added dedicated proxy code to help with the migration: [`fetch-document`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/google-drive/proxy/fetch-document.ts), [`fetch-spreadsheet`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/google-sheet/proxy/fetch-spreadsheet.ts), [`fetch-file`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/box/proxy/fetch-file.ts), [`fetch-database`](https://github.com/NangoHQ/integration-templates/blob/main/integrations/notion/proxy/fetch-database.ts). * If you're using a now-deprecated template function that fetches objects from an external system. **What to do:** * Check your action logs for a warning that you've exceeded the action output limitation. * Verify the actions you're using and log the output size of the action. * Migrate the action to use the proxy instead. If your action logs exceed the 2MB limitation, you'll see a warning like this: Action output size warning

Reach out with any questions or concerns in our Slack community. *** In this release, we've made some changes to the API that are breaking for some users. * All endpoints under `/connection` are now deprecated. Use the new `/connections` endpoint instead. All endpoints except one take and return the same data — only the base path has changed. * The endpoint `POST /connections` (previously `POST /connection`) now takes a different body but returns the same data. This new body is more flexible and ensures stricter typings on your side and validation on ours. * The endpoints `POST /connection/:connectionId/metadata` and `PATCH /connection/:connectionId/metadata`, which have been deprecated for a while, will not be migrated to `/connections` and will be removed at the end of the grace period. Effective **January 20, 2026** — all `/connection` endpoints will be removed. **Am I impacted?** * If you manually use any endpoint under `/connection`. * If you use the CLI. * If you use the official Nango SDKs. **What to do:** * If you use the CLI, upgrade to `>=0.67.0`. * If you use the official Nango SDKs, upgrade to `>=0.67.0`. * If you manually use any endpoint under `/connection`, migrate to `/connections`. * If you use the `POST /connection/:connectionId/metadata` or `PATCH /connection/:connectionId/metadata` endpoints, migrate to `/connections/metadata`. * If you specifically use the `POST /connection` endpoint to import connections, see the migration section below. ### Migrating to `POST /connections` Only this endpoint requires a manual migration. Previously, credentials were all at the root of the body: ```bash theme={null} curl -X POST https://api.nango.dev/v1/connection \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "provider_config_key": "slack", "access_token": "some-access-token", [...] }' ``` Now they are nested under the `credentials` key: ```bash theme={null} curl -X POST https://api.nango.dev/v1/connections \ -H "Authorization: Bearer " \ -H "Content-Type: application/json" \ -d '{ "provider_config_key": "slack", "credentials": { "type": "OAUTH2", "access_token": "some-access-token", [...] } }' ``` Please report any inconsistencies or issues with the new endpoints in our Slack community. *** * [RUN Powered by ADP](/integrations/all/adp-run) * [ADP Workforce Now Next Generation](/integrations/all/adp-workforce-now-next-gen) * [AutoTask](/integrations/all/autotask) * [Avoma](/integrations/all/avoma) * [Dayforce](/api-integrations/dayforce) * [Datto RMM](/integrations/all/datto-rmm) * [Datto RMM (Password Grant)](/integrations/all/datto-rmm-password-grant) * [Fairing](/integrations/all/fairing) * [Float](/integrations/all/float) * [Heap](/integrations/all/heap) * [IT Glue](/integrations/all/itglue) * [JobDiva](/integrations/all/jobdiva) * [JumpCloud](/integrations/all/jumpcloud) * [Paycor](/integrations/all/paycor) * [Paycor (Sandbox)](/integrations/all/paycor-sandbox) * [Pipedream (API Key)](/integrations/all/pipedream) * [Pipedream (Client Credentials)](/integrations/all/pipedream-oauth2-cc) * [Private API (Bearer Auth)](/integrations/all/private-api-bearer) * [Private API (Basic Auth)](/integrations/all/private-api-basic) * [Roller](/integrations/all/roller) * [Sage People](/integrations/all/sage-people) * [Yotpo](/integrations/all/yotpo) * [Zoho Calendar](/integrations/all/zoho-calendar) *** TypeScript-based script configs illustration

TypeScript-based script configs illustration

Integration scripts now use TypeScript for configuration, colocated with your script code. Benefits: * Strong type safety * Better tooling (auto-complete, linting) * No custom syntax to learn This makes writing and maintaining custom integrations simpler, whether you code them manually or generate them with an LLM. [Migration guide](/guides/platform/migrations/migrate-to-zero-yaml). *** You’ll now receive important developer updates about deprecations, breaking changes, and other integration-impacting news in a more structured way: * **Email**: Sent to everyone who signs up (with the option to unsubscribe). * **Private Slack channels**: Delivered directly if your team has a dedicated channel with us. * **Community Slack**: Shared in the `#dev-updates` channel. * **Docs**: This [changelog](/updates/changelog). *** Script API calls and Public API calls are now rate-limited separately. This prevents heavy script usage from affecting your ability to use the Public API (and vice versa). Both limits are soft and can be increased per customer. Limits are now properly reported in the Nango logs. *** A redesigned onboarding screen helps you set up your first integration and call an API right after signup. This makes it easier to experience Nango’s value in just a few minutes. *** The new script format is now officially released under CLI `>=0.64.0`. If you are already using it or have tried before, the only big change between beta and now is that we now use Zod v4. By upgrading to `>=0.64.0` and running `nango compile`, the CLI will update the dependency automatically; otherwise, you need to install Zod `4.0.5` manually. Effective **December 1, 2025** — `nango.yaml` support will be removed. **Am I impacted?** Anyone using custom scripts. **What to do:** Follow the [migration guide](/guides/platform/migrations/migrate-to-zero-yaml). *** * [Atlassian Cloud Admin](/integrations/all/atlassian-admin) * [AWS (SCIM)](/integrations/all/aws-scim) * [Azure Blob Storage](/integrations/all/azure-blob-storage) * [Fathom](/integrations/all/fathom) * [Google Chat](/api-integrations/google-chat) * [Google Cloud Storage](/api-integrations/google-cloud-storage) * [KnowBe4](/api-integrations/knowbe4) * [Paycom](/integrations/all/paycom) * [Setmore](/integrations/all/setmore) *** Nango-provided OAuth apps for testing illustration

Nango-provided OAuth apps for testing illustration

When testing OAuth APIs, you can now use Nango-provided developer apps instead of setting up your own. * Available for top APIs (more being added over time). * Select this option when creating a new integration. * For **testing only**—production apps should still use your own credentials to keep Nango fully white-labeled. *** You can now edit the user and organization information attached to a connection. This info is visible in the Nango dashboard, helping you manage connections more easily.\ [API reference](/reference/backend/http-api/connections/patch). *** Action execution latency has been reduced from **more than 200ms+** to **less than 50ms**. This makes actions feel much more responsive, especially when a human is waiting for the result. *** Each API-specific doc now includes a “Getting Started” section so you can: 1. Run the auth flow 2. Make a first successful API request All in **under 5 minutes**. Example: [Google Calendar docs](/api-integrations/google-calendar). *** * [Jobvite](/integrations/all/jobvite) * [Roam (SCIM API)](/integrations/all/roam-scim) * [Sage HR](/integrations/all/sage-hr) * [Sentry (Public Integrations)](/integrations/all/sentry-oauth) * [Trafft](/integrations/all/trafft) * [UKG Pro](/integrations/all/ukg-pro) * [UKG Ready](/integrations/all/ukg-ready) *** Generate integrations with AI illustration

Generate integrations with AI illustration

We published a new guide on using AI to generate integrations faster than coding them manually. You can still edit the generated code as needed.\ [Guide](/guides/functions/functions-guide#guide). *** You can now upgrade or downgrade your plan directly in the Nango UI, under **Usage & Billing**.\ *Note: Legacy plans still require contacting us.* *** The **Usage & Billing** tab now includes detailed usage reports: * Track all metrics that affect billing. * See past invoices with a full breakdown. *** We’ve formalized the release process for self-hosted Enterprise customers: * Two-month release cadence * Semantic versioning adopted * Clearer update process in the [self-hosting docs](/guides/platform/self-hosting#updates). *** * [Canva](/integrations/all/canva) * [Codegen](/integrations/all/codegen) * [Confluence Data Center](/integrations/all/confluence-data-center/) * [Dropbox Sign](/integrations/all/dropbox-sign) * [Grammarly SCIM](/integrations/all/grammarly-scim) * [Google Slides](/api-integrations/google-slides) * [Jamf Pro (Client Credentials)](/integrations/all/jamf) * [Jamf Pro (Basic Auth)](/integrations/all/jamf-basic) * [JazzHR](/integrations/all/jazzhr) * [Jobadder](/integrations/all/jobadder) * [Kandji](/integrations/all/kandji) * [Open Hands](/integrations/all/open-hands) * [Paychex](/integrations/all/paychex) * [PreciseFP](/integrations/all/precisefp) * [Recruitcrm](/integrations/all/recruitcrm) * [Recruiterflow](/integrations/all/recruiterflow) * [Supabase](/api-integrations/supabase) * [Terraform](/integrations/all/terraform) *** Nango as an MCP server illustration

Nango can now act as a remote MCP server, exposing third-party API actions as tools for your AI agents. * Build and enable/disable tools with Nango actions. * Use them via the MCP protocol.\ [Guide](/getting-started/use-cases/tool-calling). *** You can now localize the Connect UI: * Choose a language. * Override links to end-user guides with your own versions.\ [Docs](/reference/frontend/frontend-sdk#connect-using-nango-connect-ui). *** You can now run actions asynchronously—triggering them without waiting for an immediate result. This is useful when: * Tasks take a long time to complete. * You don’t need the response right away. * Actions should be retried for reliability. * You’re sending many actions at once.\ [Docs](/guides/functions/action-functions#trigger-asynchronously). *** You can now filter logs by precise time windows, making it easier to drill down into specific events for debugging. *** * [ADP](/integrations/all/adp) * [Auth0 (Client Credentials)](/integrations/all/auth0-cc) * [Azure DevOps](/integrations/all/azure-devops) * [ClickSend](/integrations/all/clicksend) * [CompanyCam](/integrations/all/companycam) * [Confluence (Basic Auth)](/integrations/all/confluence-basic) * [Cyberimpact](/integrations/all/cyberimpact) * [Devin](/integrations/all/devin) * [DocuWare](/integrations/all/docuware) * [Employment Hero](/integrations/all/employment-hero) * [Gem](/integrations/all/gem) * [Grammarly](/integrations/all/grammarly) * [Github (Personal Access Token)](/integrations/all/github-pat) * [Incident.io](/integrations/all/incident-io) * [Jira Data Center (Basic Auth)](/integrations/all/jira-data-center-basic) * [Namely](/integrations/all/namely) * [Namely (PAT)](/integrations/all/namely-pat) * [Redtail CRM (Sandbox)](/integrations/all/redtail-crm-sandbox) * [Rock Gym Pro](/integrations/all/rock-gym-pro) * [Rootly](/api-integrations/rootly) * [Sentry](/integrations/all/sentry) * [Shopify Partner](/integrations/all/shopify-partner) * [Smartlead.ai](/integrations/all/smartlead-ai) * [Snowflake (JWT)](/integrations/all/snowflake-jwt) * [UKG Pro (Workforce Management)](/integrations/all/ukg-pro-wfm) * [Vercel](/api-integrations/vercel) * [Workday (OAuth)](/api-integrations/workday-oauth) *** Usage-based pricing illustration

Nango now offers transparent, usage-based pricing starting at \$50/month. * Pricing scales with usage: connections, action executions & record syncs * Volume discounts up to 100x included * 1,000 free connections still available on the Free plan (unlimited on Free Self-Hosted) * Add-ons are priced individually on a monthly basis—no large annual commitments ***

The *Logs* tab is now much more powerful with full-text search and performance improvements. * Search across log and sub-log contents via the top-level search bar * Filter logs using record IDs to investigate when records were synced * Improved navigation and load times across the tab *** Enterprise self-hosting with ECS + Terraform illustration

Enterprise self-hosting with ECS + Terraform illustration

We’ve published a new [guide](/guides/platform/self-hosting) for self-hosting Nango on AWS ECS, including a ready-to-use Terraform configuration. * Automates installation for Enterprise customers * Complements our existing Helm chart for Kubernetes * Ongoing work to further simplify self-hosting The Terraform configuration is available upon request. *** Create, edit & delete environments illustration

Create, edit & delete environments illustration

You can now manage multiple environments directly from the Nango dashboard. This makes it easier to isolate development stages or segment customer-specific setups. * Growth plan includes 3 environments by default * Additional environments available via paid add-on *** * [ActiveCampaign](/integrations/all/active-campaign) * [Anthropic Administrator](/integrations/all/anthropic-admin) * [Blackbaud (Basic Auth)](/integrations/all/blackbaud-basic) * [Callrail](/integrations/all/callrail) * [Figma (SCIM)](/integrations/all/figma-scim) * [Microsoft (Client Credentials)](/api-integrations/microsoft-oauth2-cc) * [Missive](/integrations/all/missive) * [Oracle Fusion Cloud (HCM)](/integrations/all/oracle-hcm) * [Pandadoc (API Key)](/integrations/all/pandadoc-api-key) * [Razorpay](/integrations/all/razorpay) * [Readwise](/integrations/all/readwise) * [Readwise Reader](/integrations/all/readwise-reader) * [Rippling Shop App](/integrations/all/rippling-shop-app) * [SharePoint Online (Client Credentials V2)](/integrations/all/sharepoint-online-oauth2-cc) * [Trakstar Hire](/integrations/all/trakstar-hire) * [tl;dv](/integrations/all/tldv) * [Xero (Client Credentials)](/integrations/all/xero-oauth2-cc) *** Authorization logs illustration

Gain visibility into how your users interact with the Connect UI during the authorization process. Nango now tracks and logs key authorization events: * User opened or closed the Connect UI * User opened or closed the OAuth modal * User viewed a new screen (integration list, input form, success/failure) You can explore these events in the *Logs* tab of the Nango UI. We also added a chart summarizing all authorization attempts by outcome: * Success * Cancelled * Technical failure This chart is available on the *Home* tab. Watch the demo: