Zum Inhalt springen

Nango Release Notes

46 Einträge aus 2 Quellen. Zuletzt aktualisiert:

Folge Nango, um die Release Notes in deinen Feed zu holen.

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: Bessere Zusammenarbeit in gemeinsamer Entwicklungsumgebung

Teams können in Nango eine gemeinsame Entwicklungsumgebung nutzen, indem sie mit webhook_url_override Test-Webhooks lokal empfangen und mit nango deploy --sync, --action oder --integration gezielt nur einzelne Funktionen oder Integrationen deployen.

Teams can now use one shared development environment without routing local test webhooks to each other's machines or overwriting each other's function deployments.

  • Test webhooks locally: Set a webhook_url_override on your test connection to send its webhooks to your local endpoint. The shared environment webhook URLs stay unchanged for everyone else.
  • Deploy only what you changed: Use nango deploy --sync, nango deploy --action, or nango deploy --integration to update one function or integration without replacing teammates' work.

See the engineering collaboration guide for the recommended shared-environment workflow.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango 0.71.1: Metadaten und Tags in der UI bearbeiten, neue Integrationen

Nango v0.71.1 ermöglicht das Bearbeiten von Connection-Metadaten und Tags in der UI, bringt Audit-Trail-Grundlagen sowie neue Integrationen wie n8n, Workato, tripletex und baserow.

[v0.71.1] - 2026-07-20

Added

  • (integrations) Add support for phrase (#6766) by @hassan254-prog
  • (integrations) Add support for zero (#6767) by @hassan254-prog
  • (integrarions) Add support for embat (#6768) by @hassan254-prog
  • (integrations) Add support for workato (#6771) by @hassan254-prog
  • (integrations) Add support for n8n (#6772) by @hassan254-prog
  • (integrations) Add support for millionverifier (#6769) by @hassan254-prog
  • (integrations) Add support for ConnectSecure (#6720) by @rjinturkar-oai
  • (audit) Audit-log emit boundary + route wiring (NAN-6214) (#6755) by @pfreixes
  • (webapp) Add analytics events to the usage page (#6761) by @macko911
  • (integrations) Add support for tripletex (#6300) by @aisstephane
  • Add MCP Auth guide (#6785) by @rguldener
  • (integrations) Add support for baserow (#6781) by @hassan254-prog
  • (providers) Add an optional hostname to salesforce sandbox (#6797) by @hassan254-prog
  • (webapp) Edit connection metadata and tags via UI (#6760) by @rbwest
  • (providers) Add apple app store connect ui configurations (#6780) by @hassan254-prog
  • (audit) Add audit_trail_events ClickHouse table (NAN-6272) (#6787) by @pfreixes
  • (integrations) Add support for sage-member (#6717) by @hassan254-prog
  • (integrations) Allow client credentials for sage intacct to be defined at integration level (#6751) by @hassan254-prog
  • Add Control Plane MCP reference (#6757) by @marcindobry …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango Management MCP server (Beta) für Log-Zugriff

Nango bietet jetzt in der Beta einen gehosteten Management MCP server unter https://mcp.nango.dev/mcp, über den MCP-kompatible Clients wie Claude Code oder Cursor mit ersten Log-Tools (logs_list_operations, logs_get_operation) auf Nango-Logs zugreifen können.

Nango now hosts a Management MCP server at https://mcp.nango.dev/mcp that lets MCP-compatible clients, like Claude Code or Cursor, work with your Nango account through tools.

The first tools cover logs, so an agent can investigate failing syncs or actions by querying your Nango logs directly:

  • logs_list_operations: List and filter log operations.
  • logs_get_operation: Get an operation and its log messages.

Authenticate with a Nango API key sent as a Bearer token. The logs tools require the environment:logs:read scope. More tools are on the way, with the goal of supporting the full public API.

Learn more in the Management MCP reference and the coding agent setup page.

<img src="https://mintcdn.com/nango/SL--XTfmq0zlAmD1/images/changelog/nango-management-mcp-logs.png?fit=max&auto=format&n=SL--XTfmq0zlAmD1&q=85&s=68109389ecc6133245719fa0bfaa4271" alt="Claude Code querying Nango logs through the Management MCP server" width="2593" height="1680" data-path="images/changelog/nango-management-mcp-logs.png" />

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: Tags und Metadata von Verbindungen im Dashboard bearbeitbar

Tags und Metadata einer Verbindung lassen sich jetzt direkt im Auth-Tab des Dashboards bearbeiten, wofür bisher ein API-Aufruf nötig war.

Connection tags and metadata are now editable from a connection's Auth tab in the dashboard. Previously, updating them required an API call.

  • Tags: Add, edit, or remove a connection's key/value tags.
  • Metadata: Edit the metadata JSON in place. Saving overwrites the connection's existing metadata.

See the connection tags, configuration & metadata guide for how these fields work.

<img src="https://mintcdn.com/nango/SL--XTfmq0zlAmD1/images/changelog/editing-tags-connection-metadata.png?fit=max&auto=format&n=SL--XTfmq0zlAmD1&q=85&s=78a049b27a95d99a2232d6ddd0e4fad1" alt="Editing tags and connection metadata on the connection page" width="2556" height="1438" data-path="images/changelog/editing-tags-connection-metadata.png" />

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango 0.71.0: Neue Integrationen, gefilterte Nutzungsaufschlüsselung, Egress-Paket

Nango v0.71.0 fügt neue Integrationen wie ahrefs, SAP Ariba, Acumatica und sage-intacct-cc hinzu, erlaubt das Filtern von Nutzungsaufschlüsselungen auf einzelne Werte und ergänzt neue Orb-Pläne sowie ein Egress-Paket.

[v0.71.0] - 2026-07-14

Added

  • (integrations) Add support for ahrefs (#6610) by @hassan254-prog
  • (in-app) Change in app launcher icon (#6607) by @hassan254-prog
  • (integrations) Add support for microsoft-oauth2-cc-cert (#6609) by @hassan254-prog
  • (integrations) Add support for surecontact (#6623) by @hassan254-prog
  • (integrations) Add suppport for jamie (#6620) by @hassan254-prog
  • (integrations) Add support for dialpad-wfm (#6619) by @hassan254-prog
  • (integrations) Add support for acumatica (#6617) by @hassan254-prog
  • (integrations) Add support for sage-intacct-cc (#6616) by @hassan254-prog
  • Add SAP Ariba Integration (#5749) by @arsalazarjr
  • (connect-ui) Add a11y regression test suite (#6584) by @macko911
  • (egress) Introduce egress package (#6615) by @rossmcewan
  • Add new Orb plans (#6635) by @ErickRDev
  • Drill into usage breakdowns by filtering to a single value (NAN-5874) (#6528) by @macko911
  • Add changelog entry for usage breakdowns (#6658) by @sapnesh-nango
  • (server) Meter GET /records egress bytes (#6648) by @ErickRDev
  • (docs) Enhance integration configuration details for private API (#6656) by @agusayerza
  • Add custom timeouts per service (#6667) by @rossmcewan
  • (design-system) Align input and button sizing on one scale (#6645) by @macko911
  • (design-system) Add Field and Label, migrate webapp form fields (#6657) by @macko911
  • (design-system) Add interactive border token (#6655) by @macko911 …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: CIMD-Unterstützung für MCP-Authentifizierung

Nango unterstützt beim Verbinden mit MCP servern über die generische MCP-Integration jetzt Client ID Metadata Documents (CIMD) und greift nur bei fehlender Serverunterstützung auf dynamic client registration (DCR) zurück.

Nango now supports Client ID Metadata Documents (CIMD) when connecting users to MCP servers through the generic MCP integration. Nango hosts a client metadata document for each integration and uses its URL as the OAuth client ID, so no client registration step is needed. CIMD is used automatically when a server supports it, with dynamic client registration (DCR) as the fallback.

  • Connect to more MCP servers: The MCP spec now prefers CIMD over DCR, so your users can connect to servers that only support CIMD.
  • More reliable auth flows: Connecting no longer depends on a registration call that can fail or leave stale client records on the server.
  • Your branding on the authorization screen: The hosted document is built from your integration's OAuth client name, URI, and logo.

Learn more in the generic MCP provider docs and the MCP auth guide.

Originalquelle(öffnet in neuem Tab)Problem melden