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.

Feed abonnieren:RSS: Feed für Nango Release NotesAPI: Einträge von Nango Release Notes als JSON
Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Management MCP server im Connector-Verzeichnis von Claude verfügbar

Der Management MCP server ist jetzt im Connector-Verzeichnis von Claude verfügbar, sodass Claude Integrationen konfigurieren, APIs aufrufen, Syncs auslösen und Functions deployen kann, und er funktioniert auch mit Claude Code, Codex, VS Code und ChatGPT.

The Management MCP server is now available in Claude's connector directory. Claude can configure integrations, call APIs, trigger syncs, and deploy functions for you. It also works with Claude Code, Codex, VS Code, and ChatGPT.

<img src="https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/claude-connector-directory.png?fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=21ffe79c96f88ed27c660e0d5286ffd8" alt="The Nango connector in Claude's connector directory" width="2930" height="1102" data-path="images/changelog/claude-connector-directory.png" />

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Connection MCP server wird zugunsten von agent sessions abgekündigt

Der Connection MCP server wird zugunsten der neuen agent sessions abgekündigt, betroffen sind nur Agents mit Environment API key sowie den Headern connection-id und provider-config-key, und eine Migrationsanleitung zu scoped agent sessions liegt bereit.

We're deprecating the Connection MCP server in favor of the new and more capable agent sessions.

Am I impacted? Only if you have agents using the Connection MCP with an Environment API key and connection-id and provider-config-key headers.

What to do: Follow the migration guide to move to scoped agent sessions.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.12: Azure Key Vault, Agent Playground Chat API, neue Integrationen

Nango v0.71.12 ergänzt unter anderem Azure Key Vault als DEK-Wrapping-Provider, die Agent Playground Chat API, eine Option für unverifizierte Webhooks sowie neue Integrationen wie Discord Bot, Slack-App-Konfigurationstokens, modmed-fhir, Discogs und Mailtrap.

[v0.71.12] - 2026-10-02

Added

  • (webapp) Show startup-deal accounts the new billing metrics (#7566) by @macko911
  • (kms) Add Azure Key Vault as a DEK wrapping provider (#7717) by @pfreixes
  • (sanity-sync) Add integration templates sync (#7554) by @hassan254-prog
  • (webhooks) Add allow unverified webhooks integration option (NAN-7312) (#7726) by @agusayerza
  • (integrations) Add support for Discord Bot (#7678) by @arctic-char
  • (integrations) Add support for Slack app configuration tokens (#7669) by @arctic-char
  • (server) Add the Agent Playground chat API (#7697) by @macko911
  • (integrations) Add support for modmed-fhir (#7745) by @hassan254-prog
  • (integrations) Add Discogs OAuth1 and personal token providers (#7340) by @aquarazorda
  • (integrations) Add support for Mailtrap (#7150) by @mazu-rok
  • (runner-sdk) Support redirect error in nango.uncontrolledfetch (#7758) by @rbwest

Changed

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Webhook-Verifizierung für weitere Provider

Nango erweitert die Verifizierung eingehender Webhooks um eine optionale Einstellung für unverifizierte Webhooks, ein Unverified-Flag in weitergeleiteten Anfragen, Pflicht-Secrets für Provider ohne Signatur (Affinity, Fillout, ShipStation, Salesforce) und zusätzliche Signaturprüfungen für Airtable, Microsoft Teams und Halo PSA.

A second round of changes to how Nango verifies the webhooks it receives, following last month's:

  • Allow unverified webhooks: A new per-integration setting lets webhooks with a missing or unverifiable signature through (invalid signatures are always rejected). Available for providers that reject unverified webhooks, such as GitHub App, Gmail, Microsoft Teams, and Salesforce. It's off by default.
  • Unverified flag: When Nango forwards a webhook it could not verify, the request carries an X-Nango-Webhook-Unverified: true header and the Nango wrapper includes "unverified": true. Treat those payloads as untrusted. See unverified webhooks.
  • Providers that do not sign webhooks: Affinity, Fillout, ShipStation, and Salesforce now require a secret you set per connection, sent in the X-Nango-Webhook-Secret header or a nangoWebhookSecret query parameter. Webhooks without a matching secret are rejected. See providers that do not sign webhooks.
  • More signatures checked: Airtable notifications are verified against each webhook's MAC secret, Microsoft Teams activities must carry a valid Bot Framework token, and Halo PSA webhooks route to a connection with Basic auth.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

49 neue APIs im September

Im September sind 49 neue API-Integrationen hinzugekommen, darunter Airtable (MCP), Amplemarket, Apple Calendar, Epic (FHIR), MailerLite und bol.com.

<AccordionGroup> <Accordion icon="webhook" title="49 new APIs in September"> * [Airtable (MCP)](/docs/api-integrations/airtable-mcp) * [Amplemarket](/docs/api-integrations/amplemarket) * [Anarlog (MCP)](/docs/api-integrations/anarlog-mcp) * [Apple Calendar](/docs/api-integrations/apple-calendar) * [Astro (MCP)](/docs/api-integrations/astro-mcp) * [Autumn](/docs/api-integrations/autumn) * [Bandwidth](/docs/api-integrations/bandwidth) * [Beeline VMS](/docs/api-integrations/beeline-vms) * [Billit](/docs/api-integrations/billit) * [bol.com](/docs/api-integrations/bol-com) * [Clay (MCP)](/docs/api-integrations/clay-mcp) * [eClinicalWorks (FHIR)](/docs/api-integrations/eclinicalworks) * [Epic (FHIR)](/docs/api-integrations/epic) * [eWay-CRM](/docs/api-integrations/eway-crm) * [Finta](/docs/api-integrations/finta) * [Hex (MCP)](/docs/api-integrations/hex-mcp) * [HighQ](/docs/api-integrations/highq) * [HitPay](/docs/api-integrations/hitpay) * [Infor (ION API)](/docs/api-integrations/infor) * [Infor (ION API, Resource Owner Grant)](/docs/api-integrations/infor-cc) * [Inteliquent](/docs/api-integrations/inteliquent) * [JobNimbus](/docs/api-integrations/jobnimbus) * [Linkly](/docs/api-integrations/linkly) * [LiveSwitch](/docs/api-integrations/liveswitch) * [MailerLite](/docs/api-integrations/mailerlite) …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.11: OAuth für Management MCP, 2FA-Recovery, neue Integrationen

Nango v0.71.11 bringt OAuth für das Management MCP, das Deaktivieren von 2FA per Recovery-Code, automatisches Anlegen und Löschen von Schedules und Funktionen sowie neue Integrationen wie Simpplr, mailerlite und Anarlog MCP.

[v0.71.11] - 2026-09-30

Added

  • Create/delete schedules if needed when connection is created/deleted (#7584) by @TBonnin
  • Delete functions/schedules when integrations are deleted (#7589) by @TBonnin
  • (mcp) Hook up OAuth to Management MCP (#7550) by @marcindobry
  • (server) Ask for environment before OAuth MCP queries (#7601) by @marcindobry
  • (providers) Add Anarlog MCP provider (#7303) by @ComputelessComputer
  • (integrations) Support MCP_OAUTH2 across create/update/get for static, dynamic, and cimd (#7464) by @hassan254-prog
  • (webapp) Redirect from sign in/up pages when user already authenticated (#7580) by @macko911
  • (agent-sessions) Add the nango_create_connection meta tool (#7592) by @agusayerza
  • (mfa) Allow a recovery code to disable 2FA (NAN-7154) (#7597) by @agusayerza
  • (integrations) Add support for Simpplr (#7548) by @SvabhuG
  • (oauth2_cc) Fall back to JWT exp for OAUTH2_CC token expiry (#7605) by @hassan254-prog
  • Delete functions as part of the retention deletion logic (#7602) by @TBonnin
  • (mcp) Add missing hints to Management MCP tools (#7608) by @marcindobry
  • Add NANGO_ADMIN_KEY to env example (#7619) by @rossmcewan
  • (integrations) Add pleo api key to the api key regex (#7623) by @hassan254-prog
  • (halo-psa) Add authenticated webhook routing (#7615) by @neelS-hah
  • (authz) Authorize public routes through grants (#7490) by @kaposke
  • (integrations) Add support for mailerlite (#7618) by @alex-onepage …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Webhook-Signing-Keys lassen sich jetzt rotieren

Der Schlüssel, mit dem Nango gesendete Webhooks signiert, kann nun in den Environment Settings unter Webhooks oder per API mit dem Scope environment:webhook_signing_key:rotate rotiert werden, wobei der alte Key noch bis zu 5 Minuten gültig bleibt.

You can now rotate the key that signs the webhooks Nango sends to your app, from Environment Settings > Webhooks.

For webhooks already in flight, the old key will still work for up to 5 minutes after rotation.

You can also rotate the key using the API. Use the environment:webhook_signing_key:rotate scope for your Environment API key.

<img src="https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/webhook-signing-key-rotate.png?fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=9ae323a8ef1e1ab6c659d2e3976cc83c" alt="Rotate key button under Environment Settings > Webhooks" data-og-width="1940" width="1940" data-og-height="791" height="791" data-path="images/changelog/webhook-signing-key-rotate.png" data-optimize="true" data-opv="3" srcset="https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/webhook-signing-key-rotate.png?w=280&fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=7660ba5ceecefc08061bd96dd347abb3 280w, https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/webhook-signing-key-rotate.png?w=560&fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=aab8f61e6f958bb48bc7ae65c2451fa4 560w, https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/webhook-signing-key-rotate.png?w=840&fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=e39184005285d15b991f21c50e63d742 840w, https://mintcdn.com/nango/A2p4eyIhHedzqHH1/images/changelog/webhook-signing-key-rotate.png?w=1100&fit=max&auto=format&n=A2p4eyIhHedzqHH1&q=85&s=d6681…

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Kleinere Verbesserungen: MCP-Integrationen in der API und 2FA-Recovery-Codes

Integrationen für generische MCP-Server lassen sich jetzt auch über die integrations API anlegen und aktualisieren, und ein Recovery-Code kann die Zwei-Faktor-Authentifizierung deaktivieren, wenn die Authenticator-App verloren ging.

  • MCP integrations in the API: Integrations for generic MCP servers can now be created and updated through the integrations API, not just the dashboard. Fetching an integration with include=credentials also returns the configuration of providers with a custom config schema, with secret fields masked.
    • 2FA recovery codes: A recovery code can now disable two-factor authentication, for users who lost their authenticator app.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: OAuth für den Management MCP Server

Der Management MCP Server von Nango unterstützt jetzt OAuth-Anmeldung über https://mcp.nango.dev/mcp (API-Keys funktionieren weiterhin) und bietet zusätzliche Tools wie providers_get, actions_trigger, syncs_trigger, deploy_template und environments_list.

The Management MCP server now connects with OAuth. Add https://mcp.nango.dev/mcp to your MCP client, sign in to Nango in the browser, and approve access.

  • Supported clients: Claude Code, Codex, VS Code, ChatGPT or any other MCP client.
  • API keys still work: Environment API keys remain an option for non-interactive clients and clients without CIMD support.

<img src="https://mintcdn.com/nango/C6VwkFQwhw28Z7yh/images/changelog/management-mcp-oauth-screen.png?fit=max&auto=format&n=C6VwkFQwhw28Z7yh&q=85&s=f194b7ed405d8dbb1a4af93f10ff210b" alt="Nango consent screen for the Management MCP OAuth flow" style={{ maxWidth: "520px" }} width="1340" height="1340" data-path="images/changelog/management-mcp-oauth-screen.png" />

We also added more tools to the Management MCP:

  • Providers: providers_get, to look up a provider and its function templates
  • Actions and syncs: actions_trigger, syncs_trigger, syncs_set_state
  • Deployments: deploy_template, deploy_function, get_deployment_status
  • Environments: environments_list

See Management MCP reference for the full list.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Agent sessions: Verbindung mitten in der Session herstellen

Agents können Nutzer während einer Session über das neue, standardmäßig deaktivierte Meta-Tool nango_create_connection zum Verbinden einer Integration auffordern, und nango_tool_search sowie nango_execute geben bei fehlender Verbindung klarere Hinweise.

Agents can now ask the user to connect an integration during a session instead of dead-ending on it.

  • New nango_create_connection meta tool: When one of the session's integrations has no connection, the agent calls it and gets a connect link to hand to the user. Once the user authorizes, that integration's tools work for the rest of the session. It is off by default. Enable it per session with meta_tools, optionally with tags to stamp on the connections it creates so later sessions can select them.
  • Clearer guidance: When an integration is not connected, nango_tool_search and nango_execute tell the agent what to do next: call nango_create_connection if the session allows it, otherwise hand it to the user.

See nango_create_connection in the agent sessions guide.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.10: Rückkehr nach Login, geplante Funktionen, neue Integrationen

Nango v0.71.10 ermöglicht die Rückkehr zur angeforderten Seite nach dem Login, die Ausführung geplanter Funktionen und getVariant() und unterstützt neue Integrationen wie Linkly, Autumn, hex mcp und Apple Calendar.

[v0.71.10] - 2026-09-21

Added

  • (auth) Return to the requested page after login (#7520) by @macko911
  • (integrations) Add Linkly (API key) (#7516) by @chrism2671
  • Extend one-off PAYG migration script (#7553) by @ErickRDev
  • (oauth) Add dashboard login and consent flow (NAN-6924) (#7481) by @marcindobry
  • (tracking) Track plan_change:v2 (#7558) by @ErickRDev
  • Scheduled functions can execute (#7563) by @TBonnin
  • (integrations) Add Autumn (API key) (#7576) by @brf153
  • (providers) Move stripe-app-sandbox appDomain to integration_config (#7227) by @hassan254-prog
  • (integrations) Add support for hex mcp (#7578) by @hassan254-prog
  • (function) Implement getVariant() (#7569) by @TBonnin
  • (integrations) Add support for apple calendar (#7535) by @hassan254-prog

Changed

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: BYOC ist der empfohlene Weg für Self-Hosting

Bring Your Own Cloud (BYOC) ist jetzt der empfohlene Weg zum Self-Hosting von Nango: Nango betreibt eine dedizierte Instanz in Ihrem eigenen Cloud-Account (AWS, GCP oder Azure), setzt aber einen Enterprise-Plan voraus.

Bring Your Own Cloud (BYOC) is now the recommended way to self-host Nango. Self-hosting usually means operating the platform yourself in exchange for keeping data in your own infrastructure. BYOC removes that trade-off.

Nango deploys and operates a dedicated instance inside your own cloud account, so your end users' credentials, synced records, and logs never leave it. Nango handles deployments, upgrades, scaling, incident response, and support, and you get every feature of Nango Cloud.

The new BYOC guide covers this in full detail. BYOC supports AWS, GCP, and Azure.

If you prefer to run Nango yourself, see the Self-Managed guide. Both require an Enterprise plan. See the self-hosting overview for a comparison.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: Kleinere Verbesserungen bei MCP, CLI, Varianten und Webhooks

Kleinere Verbesserungen: OAuth-Scopes lassen sich bei generischen MCP-Integrationen festlegen, --sourcemap false lässt Source Maps in CLI-Bundles weg, nango.getVariant() liefert die Variante des aktuellen Laufs, und Webhooks von Zoom, Gong, Granola und Outlook werden unterstützt.

  • MCP integrations: For integrations that use the generic MCP OAuth provider, you can set the OAuth scopes Nango requests, in the integration settings or when creating the integration. Previously, scopes came only from the MCP server's metadata. See MCP auth.
    • CLI source maps: Pass --sourcemap false to nango compile, nango dryrun, or nango deploy to leave source maps out of compiled function bundles.
    • Functions: nango.getVariant() returns the variant of the current sync or action run.
    • New webhooks: Nango can receive and forward webhooks from Zoom, Gong, Granola, and Outlook.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.9: Bessere MCP-Fehlermeldungen und pleo-api-key

Nango v0.71.9 ergänzt agentenfreundliche Fehlermeldungen bei MCP-Tool-Fehlern und die Integration pleo-api-key und behebt Probleme bei der Umgebungsabfrage sowie beim Routing von TWO_STEP-Credentials.

v0.71.9 - 2026-09-16

Added

  • (agent-sessions) Give MCP tool failures an agent-facing message and code (NAN-6604) (#7473) by @agusayerza
  • (integrations) Add support for pleo-api-key (#7534) by @hassan254-prog

Changed

  • (shared) Coalesce customer key lookups (#7466) by @ErickRDev

Fixed

  • (shared) Propagate environment lookup failures (#7472) by @ErickRDev
  • (frontend) Route TWO_STEP credentials before OAuth2 client creden… (#7556) by @vdeez1
<!-- generated by git-cliff -->

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.8: Agent-Session-Filter, GCP- und Azure-Buckets, Integrationen

Nango v0.71.8 fügt einen Agent-Session-Filter auf der Logs-Seite, Unterstützung für GCP- und Azure-Buckets, das Deployment von Funktionen mit Schedule-Trigger, Audit von Agent-Sessions und mehrere neue Integrationen wie highq, infor und microsoft-dataverse hinzu.

[v0.71.8] - 2026-09-16

Added

  • (logs) Stamp the session actor on action runs (NAN-6949) (#7443) by @agusayerza
  • (logs) Add an agent session filter to the logs page (NAN-6606) (#7446) by @agusayerza
  • (integrations) Add support for highq (#7487) by @hassan254-prog
  • (integrations) Add support for pandadoc eu and mcp (#7500) by @hassan254-prog
  • (integrations) Add support for infor (#7513) by @hassan254-prog
  • (integrations) Add support for microsoft-dataverse (#7505) by @hassan254-prog
  • (integrations) Add support for scavio (#7165) by @scavio-ai
  • Add OAuth authorization server package (#7463) by @marcindobry
  • (mcp) Support static server URL and configurable scopes for MCP_OAUTH2_GENERIC (#7465) by @hassan254-prog
  • (shared) Add support for GCP and Azure buckets (#7519) by @rossmcewan
  • (agent-sessions) Reap expired sessions and their tokens (NAN-6599) (#7511) by @agusayerza
  • (integrations) Add SalesCaptain (#7149) by @yogii-sc
  • (audit) Audit agent session creation and termination (NAN-6751) (#7508) by @agusayerza
  • (agent-sessions) Log a tool search operation (NAN-6605) (#7509) by @agusayerza
  • (functions) Support deployment of function with schedule trigger (#7512) by @TBonnin
  • (jobs) Emit function execution health metric at the source (NAN-6988) (#7527) by @pfreixes
  • Add one-off Orb pay-as-you-go migration scheduler (#7494) by @ErickRDev
  • (plans) Growth add-on management cron (#7530) by @ErickRDev …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: nango.yaml wird nicht mehr akzeptiert

Nango akzeptiert keine Deployments mit einer nango.yaml mehr (sie schlagen mit einem Fehler fehl), bereits deployte Functions laufen weiter, und die Migration erfolgt per nango migrate-to-zero-yaml.

Nango no longer accepts deployments that use a nango.yaml configuration file. The deprecation was announced in July 2025, when TypeScript-based function configuration replaced it.

Am I impacted? Only if you still deploy custom functions from a nango.yaml. Those deployments now fail with an error that links to the migration guide. Functions that are already deployed keep running.

What to do: Upgrade the Nango CLI, run nango migrate-to-zero-yaml, and redeploy. The migration guide explains each change.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: Neuerungen bei Agent sessions

Agent sessions erhalten das optionale Meta-Tool nango_proxy, eine API DELETE /sessions/{session_id} zum Beenden von Sessions, einen Agent-session-Filter in den Logs und verständlichere Fehlermeldungen bei fehlgeschlagenen Tool-Aufrufen.

Improvements to agent sessions since launch:

  • Proxy tool: A new nango_proxy meta tool lets the agent call any endpoint of a connected integration when no tool in the session fits. Nango authenticates the request, so the agent never sees credentials. It is off by default; turn it on per session. See meta tools.
  • Terminate a session: A new DELETE /sessions/{session_id} API to end a session before it expires and revoke its token. See terminating a session.
  • Logs filter: The Logs page has an Agent session filter that shows the operations a session ran. Each operation also shows which session drove it.
  • Clearer tool errors: Failed tool calls return a message that says what failed and what the agent should do next.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango unterstützt jetzt über 1.000 APIs

Nango unterstützt jetzt mehr als 1.000 APIs, jeweils mit vorgefertigter Autorisierung, Proxy und Logs, viele zusätzlich mit vorgefertigten Tools, Triggern und Syncs.

Nango now supports more than 1,000 APIs. Each comes with pre-built authorization, the proxy, and logs, and many include pre-built tools, triggers, and syncs.

Browse the full list. If an API you need is missing, you can request it or contribute it.

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango: Strengere Webhook-Verifizierung

Nango verifiziert mehr eingehende Webhooks: Gmail-Pushes ohne OIDC-Token und GitHub-App-Webhooks ohne Signatur werden standardmäßig abgelehnt, und für Google Drive und Calendar lässt sich ein Webhook-Secret hinterlegen.

Nango now verifies more of the webhooks it receives from external APIs before forwarding them to your app.

  • Gmail: Nango already verified the OIDC token that Google attaches when authentication is enabled on your Pub/Sub subscription. Pushes without one are now rejected by default and not forwarded, so enabling authentication is a required step in the Gmail webhook guide. If you need time to enable it, contact us and we can temporarily allow unsigned pushes for your account.
  • Google Drive and Calendar: You can now save a webhook secret on the integration. Once set, Nango checks each notification's X-Goog-Channel-Token header against it and rejects mismatches. Without a secret, notifications are forwarded unverified, so set the secret before creating channels and pass it as the channel token. See the Drive and Calendar guides.
  • GitHub App: Webhooks without an x-hub-signature-256 header are now rejected by default. GitHub only signs payloads when a webhook secret is set on your app, so it must match the secret shown on your Nango integration page. See the GitHub App setup guide. …

Originalquelle(öffnet in neuem Tab)Problem melden

Angaben zum Datum

Datum aus der Quelle.

Erstmals gesehen am .

Nango

Nango v0.71.7: Postgres-Audit-Trail, Sessions beenden, Outlook-Webhooks

Nango v0.71.7 bringt einen Postgres-basierten Audit-Trail für Self-Hosting, das Beenden von Agent-Sessions per DELETE /sessions/{id}, das Growth-Add-on für Pay-as-you-go sowie Outlook-Webhook-Unterstützung.

[v0.71.7] - 2026-09-11

Added

  • (mcp) Add providers get tool (#7283) by @marcindobry
  • (server) Tag internal callers instead of excluding them from deprecated endpoint metric (#7353) by @hassan254-prog
  • (audit) Day-partitioned Postgres schema for the self-hosted audit trail (#7335) by @pfreixes
  • (audit) Daily partition lifecycle for the self-hosted audit table (#7343) by @pfreixes
  • Add deploy all workflow (#7380) by @rossmcewan
  • (audit) Show how many events a read matches (#7365) by @macko911
  • (agent-sessions) Add DELETE /sessions/{id} to terminate a session (NAN-6598) (#7336) by @agusayerza
  • (webhooks) Back off throttled groups on jobs SQS consumer (NAN-6407) (#7328) by @agusayerza
  • (webhooks) Defer saturated dispatch messages in SQS (NAN-6406) (#7334) by @agusayerza
  • (orch) Add executeFunctionBatch (#7374) by @TBonnin
  • (audit) Postgres writer and reader for the self-hosted audit trail (#7346) by @pfreixes
  • (plans) Add the growth add-on for pay-as-you-go (#7301) by @ErickRDev
  • (audit) Run the Postgres migration and partition daemon from the server (#7355) by @pfreixes
  • (webapp) Rework the audit trail filter UI (#7397) by @macko911
  • Add screenshot to the agent sessions changelog entry (#7411) by @sapnesh-nango
  • (providers) Add outlook webhook support (#7389) by @rbwest
  • (webapp) Let customers add and remove the Growth add-on (#7402) by @macko911 …

Originalquelle(öffnet in neuem Tab)Problem melden

Ähnlich wie Nango, mit neuen Einträgen