@nangohq/providers 0.69.38 → 0.69.40

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nangohq/providers",
-    "version": "0.69.38",
+    "version": "0.69.40",
     "description": "Nango's providers.yaml and getters",
     "type": "module",
     "main": "./dist/index.js",
@@ -16,7 +16,7 @@
         "js-yaml": "4.1.1"
     },
     "devDependencies": {
-        "@nangohq/types": "0.69.38",
+        "@nangohq/types": "0.69.40",
         "vitest": "3.2.4"
     },
     "files": [

package/providers.yaml

@@ -2566,22 +2566,23 @@ builder-io-private:
                 content-type: application/json
             endpoints:
                 - /api/v1/write/page
-    docs: https://nango.dev/docs/integrations/all/builder-io-private
-    docs_connect: https://nango.dev/docs/integrations/all/builder-io-private/connect
+    docs: https://nango.dev/docs/api-integrations/builder-io-private
+    docs_connect: https://nango.dev/docs/api-integrations/builder-io-private/connect
     connection_config:
         domain:
             type: string
             title: Domain
-            description: The domain used to access your Builder.io API
-            example: cdn.builder.io
+            description: The domain used to access your Builder.io write API.
+            example: builder.io
             format: hostname
             prefix: https://
+            order: 1
             doc_section: '#step-1-finding-your-api-domain'
     credentials:
         apiKey:
             type: string
             title: API Key
-            description: The API key for your Builder.io account
+            description: The private key for your Builder.io account.
             pattern: '^bpk-[a-f0-9]+$'
             example: bpk-****************************
             doc_section: '#step-2-finding-your-api-key'
@@ -2603,22 +2604,23 @@ builder-io-public:
                 content-type: application/json
             endpoints:
                 - /api/v1/content/page
-    docs: https://nango.dev/docs/integrations/all/builder-io-public
-    docs_connect: https://nango.dev/docs/integrations/all/builder-io-public/connect
+    docs: https://nango.dev/docs/api-integrations/builder-io-public
+    docs_connect: https://nango.dev/docs/api-integrations/builder-io-public/connect
     connection_config:
         domain:
             type: string
             title: Domain
-            description: The domain used to access your Builder.io API
-            example: builder.io
+            description: The domain used to access your Builder.io content API.
+            example: cdn.builder.io
             format: hostname
             prefix: https://
+            order: 1
             doc_section: '#step-1-finding-your-api-domain'
     credentials:
         apiKey:
             type: string
             title: API Key
-            description: The API key for your Builder.io account
+            description: The public api key for your Builder.io account.
             pattern: '^[a-zA-Z0-9]+$'
             example: bb209fb71eh2412dbe0114bdae18fd15
             doc_section: '#step-2-finding-your-api-key'
@@ -6432,6 +6434,32 @@ granola:
             pattern: '^grn_[A-Za-z0-9]+_[A-Za-z0-9]+$'
             doc_section: '#step-1-generating-your-granola-api-token'
 
+granola-mcp:
+    display_name: Granola (MCP)
+    categories:
+        - productivity
+        - knowledge-base
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://mcp-auth.granola.ai/oauth2/authorize
+    token_url: https://mcp-auth.granola.ai/oauth2/token
+    registration_url: https://mcp-auth.granola.ai/oauth2/register
+    default_scopes:
+        - offline_access
+    authorization_params:
+        response_type: code
+        resource: https://mcp.granola.ai/
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        headers:
+            accept: application/json,text/event-stream
+        base_url: https://mcp.granola.ai
+    docs: https://nango.dev/docs/api-integrations/granola-mcp
+
 guru:
     display_name: Guru
     categories:
@@ -6860,6 +6888,33 @@ glyphic:
             description: Your Glyphic API key
             doc_section: '#step-1-getting-your-api-key'
 
+gamma:
+    display_name: Gamma
+    categories:
+        - productivity
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://public-api.gamma.app
+        headers:
+            x-api-key: ${apiKey}
+            content-type: application/json
+        verification:
+            method: GET
+            headers:
+                accept: application/json
+            endpoints:
+                - /v1.0/folders
+    docs: https://nango.dev/docs/api-integrations/gamma
+    docs_connect: https://nango.dev/docs/api-integrations/gamma/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Gamma API key.
+            example: 'sk-gamma-xxxxxxxx'
+            pattern: '^sk-gamma-'
+            doc_section: '#step-1-getting-your-gamma-api-key'
+
 google:
     display_name: Google
     categories:
@@ -6898,6 +6953,16 @@ google-analytics:
     docs: https://nango.dev/docs/api-integrations/google-analytics
     setup_guide_url: https://nango.dev/docs/api-integrations/google-analytics/how-to-register-your-own-google-analytics-api-oauth-app
 
+google-bigquery:
+    display_name: Google BigQuery
+    categories:
+        - productivity
+    alias: google
+    proxy:
+        base_url: https://bigquery.googleapis.com
+    docs: https://nango.dev/docs/api-integrations/google-bigquery
+    setup_guide_url: https://nango.dev/docs/api-integrations/google-bigquery/how-to-register-your-own-google-bigquery-api-oauth-app
+
 google-calendar:
     display_name: Google Calendar
     categories:
@@ -6992,6 +7057,16 @@ google-drive:
     docs: https://nango.dev/docs/api-integrations/google-drive
     setup_guide_url: https://nango.dev/docs/api-integrations/google-drive/how-to-register-your-own-google-drive-api-oauth-app
 
+google-forms:
+    display_name: Google Forms
+    categories:
+        - productivity
+    alias: google
+    proxy:
+        base_url: https://forms.googleapis.com
+    docs: https://nango.dev/docs/api-integrations/google-forms
+    setup_guide_url: https://nango.dev/docs/api-integrations/google-forms/how-to-register-your-own-google-forms-api-oauth-app
+
 google-meet:
     display_name: Google Meet
     categories:
@@ -7796,6 +7871,19 @@ hibob-service-user:
     docs: https://nango.dev/docs/integrations/all/hibob-service-user
     docs_connect: https://nango.dev/docs/integrations/all/hibob-service-user/connect
 
+heygen:
+    display_name: HeyGen
+    categories:
+        - video
+    auth_mode: OAUTH2
+    authorization_url: https://app.heygen.com/oauth/authorize
+    token_url: https://api2.heygen.com/v1/oauth/token
+    refresh_url: https://api2.heygen.com/v1/oauth/refresh_token
+    proxy:
+        base_url: https://api2.heygen.com
+    docs: https://nango.dev/docs/api-integrations/heygen
+    setup_guide_url: https://nango.dev/docs/api-integrations/heygen/how-to-register-your-own-heygen-oauth-app
+
 highlevel:
     display_name: HighLevel
     categories:
@@ -9689,6 +9777,21 @@ metabase:
             description: The API key for your Metabase account
             doc_section: '#step-1-generating-an-api-key'
 
+mercury:
+    display_name: Mercury
+    categories:
+        - accounting
+    auth_mode: OAUTH2
+    scope_separator: ' '
+    authorization_url: https://oauth2.mercury.com/oauth2/auth
+    token_url: https://oauth2.mercury.com/oauth2/token
+    default_scopes:
+        - offline_access
+    proxy:
+        base_url: https://api.mercury.com
+    docs: https://nango.dev/docs/api-integrations/mercury
+    setup_guide_url: https://nango.dev/docs/api-integrations/mercury/how-to-register-your-own-mercury-oauth-app
+
 meta-marketing-api:
     display_name: Meta Marketing API
     categories:
@@ -9942,6 +10045,7 @@ maximizer:
     auth_mode: OAUTH2
     authorization_url: https://${connectionConfig.region}.maximizercrmlive.com/oauth2/${connectionConfig.company_alias}/authorize
     token_url: https://${connectionConfig.region}.maximizercrmlive.com/oauth2/${connectionConfig.company_alias}/token
+    disable_pkce: true
     authorization_params:
         response_type: code
     token_params:
@@ -9973,6 +10077,7 @@ maximizer-on-premise:
     auth_mode: OAUTH2
     authorization_url: https://${connectionConfig.hostname}/MaximizerWebAuthentication/OAuth2/Authorize
     token_url: https://${connectionConfig.hostname}/MaximizerWebAuthentication/OAuth2/Token
+    disable_pkce: true
     authorization_params:
         response_type: code
     token_params:
@@ -13542,6 +13647,7 @@ salesforce:
     post_connection_script: salesforcePostConnection
     docs: https://nango.dev/docs/api-integrations/salesforce
     setup_guide_url: https://nango.dev/docs/api-integrations/salesforce/how-to-register-your-own-salesforce-api-oauth-app
+    docs_connect: https://nango.dev/docs/api-integrations/salesforce/connect
     connection_config:
         instance_url:
             type: string
@@ -13558,6 +13664,7 @@ salesforce:
             example: acme.my.salesforce.com
             prefix: https://
             optional: true
+            doc_section: '#step-1-finding-your-hostname'
 
 salesforce-jwt:
     display_name: Salesforce (JWT)
@@ -13596,21 +13703,21 @@ salesforce-jwt:
             title: Consumer Key
             example: 3MVG9dAEux2v1sLsg0e52***************CJpGsXgqg8E
             description: The Consumer Key from your Salesforce Connected App.
-            doc_section: '#step-4-get-consumer-key-and-consumer-secret'
+            doc_section: '#step-3-get-consumer-key-and-consumer-secret'
         clientSecret:
             type: string
             title: Consumer Secret
             example: 954F73F4C234***************9D069B8FCF83B5
             pattern: '^[A-F0-9]{64}$'
             description: The Consumer Secret from your Salesforce Connected App.
-            doc_section: '#step-4-get-consumer-key-and-consumer-secret'
+            doc_section: '#step-3-get-consumer-key-and-consumer-secret'
         username:
             type: string
             title: Username
             description: The Salesforce username of the user the JWT will act on behalf of.
             format: email
             example: john@acme.com
-            doc_section: '#step-7-finding-the-username'
+            doc_section: '#step-6-finding-the-username'
         privateKey:
             type: string
             title: Private Key
@@ -13623,7 +13730,7 @@ salesforce-jwt:
             description: Your Salesforce authorization server URL.
             format: hostname
             example: 'login.salesforce.com'
-            doc_section: '#step-6-finding-the-authorization-server-url'
+            doc_section: '#step-5-finding-the-authorization-server-url'
 
 salesforce-sandbox:
     display_name: Salesforce (Sandbox)
@@ -16464,6 +16571,64 @@ ukg-pro:
             prefix: https://
             doc_section: '#step-3-finding-your-hostname'
 
+ukg-pro-cc:
+    display_name: UKG Pro HCM (Client Credentials)
+    categories:
+        - hr
+    auth_mode: OAUTH2_CC
+    token_url: https://${connectionConfig.identityServer}/signin/oauth2/t/${connectionConfig.tenantId}/access_token
+    body_format: form
+    token_headers:
+        content-type: application/x-www-form-urlencoded
+        accept: application/json
+    token_params:
+        grant_type: client_credentials
+    proxy:
+        retry:
+            after:
+                - 'retry-after'
+        base_url: https://${connectionConfig.hostname}
+    docs: https://nango.dev/docs/api-integrations/ukg-pro-cc
+    docs_connect: https://nango.dev/docs/api-integrations/ukg-pro-cc/connect
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Unique identifier of the identity client provided by UKG customer support.
+            doc_section: '#step-1-getting-the-credentials-from-ukg-support'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Client secret associated with the client ID provided by UKG customer support.
+            secret: true
+            doc_section: '#step-1-getting-the-credentials-from-ukg-support'
+    connection_config:
+        identityServer:
+            type: string
+            title: Identity Server
+            description: Identity server for your tenant.
+            format: hostname
+            example: signin.ukg.net
+            order: 1
+            doc_section: '#step-1-getting-the-credentials-from-ukg-support'
+        tenantId:
+            type: string
+            title: Tenant
+            description: Tenant value from your UKG Pro Recruiting URL.
+            example: UO32145HGOGOG
+            pattern: '^[a-zA-Z0-9]+$'
+            order: 3
+            doc_section: '#step-2-identify-tenant-and-recruiting-application-domain'
+        hostname:
+            type: string
+            title: Recruiting Application Domain
+            description: Recruiting application domain from your UKG Pro Recruiting URL.
+            format: hostname
+            example: recruiting.example.ultipro.com
+            prefix: https://
+            order: 2
+            doc_section: '#step-2-identify-tenant-and-recruiting-application-domain'
+
 ukg-ready:
     display_name: UKG Ready
     categories: