@nangohq/providers 0.69.36 → 0.69.38

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +2 -2
  2. package/providers.yaml +212 -9
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@nangohq/providers",
3
- "version": "0.69.36",
3
+ "version": "0.69.38",
4
4
  "description": "Nango's providers.yaml and getters",
5
5
  "type": "module",
6
6
  "main": "./dist/index.js",
@@ -16,7 +16,7 @@
16
16
  "js-yaml": "4.1.1"
17
17
  },
18
18
  "devDependencies": {
19
- "@nangohq/types": "0.69.36",
19
+ "@nangohq/types": "0.69.38",
20
20
  "vitest": "3.2.4"
21
21
  },
22
22
  "files": [
package/providers.yaml CHANGED
@@ -1170,6 +1170,7 @@ asana-mcp:
1170
1170
  - ticketing
1171
1171
  - mcp
1172
1172
  auth_mode: MCP_OAUTH2
1173
+ client_registration: dynamic
1173
1174
  authorization_url: https://mcp.asana.com/authorize
1174
1175
  token_url: https://mcp.asana.com/token
1175
1176
  registration_url: https://mcp.asana.com/register
@@ -2581,8 +2582,8 @@ builder-io-private:
2581
2582
  type: string
2582
2583
  title: API Key
2583
2584
  description: The API key for your Builder.io account
2584
- pattern: '^[a-zA-Z0-9]+$'
2585
- example: bb209fb71eh2412dbe0114bdae18fd15
2585
+ pattern: '^bpk-[a-f0-9]+$'
2586
+ example: bpk-****************************
2586
2587
  doc_section: '#step-2-finding-your-api-key'
2587
2588
 
2588
2589
  builder-io-public:
@@ -7909,6 +7910,28 @@ hubspot:
7909
7910
  docs: https://nango.dev/docs/api-integrations/hubspot
7910
7911
  setup_guide_url: https://nango.dev/docs/api-integrations/hubspot/how-to-register-your-own-hubspot-api-oauth-app
7911
7912
 
7913
+ hubspot-mcp:
7914
+ display_name: HubSpot (MCP)
7915
+ categories:
7916
+ - marketing
7917
+ - support
7918
+ - crm
7919
+ - mcp
7920
+ auth_mode: MCP_OAUTH2
7921
+ client_registration: static
7922
+ authorization_url: https://mcp.hubspot.com/oauth/authorize/user
7923
+ token_url: https://mcp.hubspot.com/oauth/v3/token
7924
+ authorization_params:
7925
+ response_type: code
7926
+ token_params:
7927
+ grant_type: authorization_code
7928
+ refresh_params:
7929
+ grant_type: refresh_token
7930
+ proxy:
7931
+ base_url: https://mcp.hubspot.com
7932
+ docs: https://nango.dev/docs/api-integrations/hubspot-mcp
7933
+ setup_guide_url: https://nango.dev/docs/api-integrations/hubspot-mcp/how-to-register-your-own-hubspot-mcp-api-oauth-app
7934
+
7912
7935
  incident-io:
7913
7936
  display_name: Incident.io
7914
7937
  categories:
@@ -9140,6 +9163,7 @@ linear-mcp:
9140
9163
  - ticketing
9141
9164
  - mcp
9142
9165
  auth_mode: MCP_OAUTH2
9166
+ client_registration: dynamic
9143
9167
  authorization_url: https://mcp.linear.app/authorize
9144
9168
  token_url: https://mcp.linear.app/token
9145
9169
  registration_url: https://mcp.linear.app/register
@@ -9730,6 +9754,46 @@ microsoft-admin:
9730
9754
  doc_section: '#step-1-finding-your-tenant-id'
9731
9755
  order: 1
9732
9756
 
9757
+ microsoft-teams-bot:
9758
+ display_name: Microsoft Teams Bot
9759
+ auth_mode: OAUTH2
9760
+ categories:
9761
+ - communication
9762
+ authorization_url: https://login.microsoftonline.com/${connectionConfig.tenantId}/oauth2/v2.0/authorize
9763
+ token_url: https://login.microsoftonline.com/${connectionConfig.tenantId}/oauth2/v2.0/token
9764
+ disable_pkce: true
9765
+ default_scopes:
9766
+ - offline_access
9767
+ - .default
9768
+ authorization_params:
9769
+ response_type: code
9770
+ response_mode: query
9771
+ token_params:
9772
+ grant_type: authorization_code
9773
+ refresh_params:
9774
+ grant_type: refresh_token
9775
+ proxy:
9776
+ base_url: https://smba.trafficmanager.net/teams
9777
+ connection_config:
9778
+ botHostTenantId: ${connectionConfig.botHostTenantId}
9779
+ post_connection_script: microsoftTeamsBotPostConnection
9780
+ docs: https://nango.dev/docs/integrations/all/microsoft-teams-bot
9781
+ docs_connect: https://nango.dev/docs/integrations/all/microsoft-teams-bot/connect
9782
+ connection_config:
9783
+ tenantId:
9784
+ type: string
9785
+ title: Tenant ID
9786
+ description: The unique identifier for the Azure AD tenant
9787
+ format: uuid
9788
+ example: a1b2c3d4-e5f6-47a8-9b0c-d1234567890f
9789
+ doc_section: '#step-1-finding-your-tenant-id'
9790
+ order: 1
9791
+ botHostTenantId:
9792
+ type: string
9793
+ title: ''
9794
+ description: ''
9795
+ automated: true
9796
+
9733
9797
  microsoft-excel:
9734
9798
  display_name: Microsoft Excel
9735
9799
  categories:
@@ -10663,6 +10727,7 @@ notion-mcp:
10663
10727
  - productivity
10664
10728
  - mcp
10665
10729
  auth_mode: MCP_OAUTH2
10730
+ client_registration: dynamic
10666
10731
  authorization_url: https://mcp.notion.com/authorize
10667
10732
  token_url: https://mcp.notion.com/token
10668
10733
  registration_url: https://mcp.notion.com/register
@@ -10841,6 +10906,55 @@ okta:
10841
10906
  suffix: .okta.com
10842
10907
  prefix: https://
10843
10908
 
10909
+ okta-cc:
10910
+ display_name: Okta (Client Credentials)
10911
+ categories:
10912
+ - dev-tools
10913
+ auth_mode: OAUTH2_CC
10914
+ token_url: https://${connectionConfig.subdomain}.okta.com/oauth2/v1/token
10915
+ token_request_auth_method: private_key_jwt
10916
+ token_params:
10917
+ grant_type: client_credentials
10918
+ proxy:
10919
+ base_url: https://${connectionConfig.subdomain}.okta.com
10920
+ retry:
10921
+ at:
10922
+ - 'x-rate-limit-reset'
10923
+ paginate:
10924
+ type: 'link'
10925
+ limit_name_in_request: 'limit'
10926
+ link_rel_in_response_header: 'next'
10927
+ docs: https://nango.dev/docs/api-integrations/okta-cc
10928
+ docs_connect: https://nango.dev/docs/api-integrations/okta-cc/connect
10929
+ credentials:
10930
+ client_id:
10931
+ type: string
10932
+ title: Client ID
10933
+ description: The Client ID of your Okta API Services application
10934
+ doc_section: '#step-1-creating-your-okta-api-services-application'
10935
+ client_private_key:
10936
+ type: string
10937
+ title: Private Key (JWK)
10938
+ description: The private JWK JSON (including kid, kty, n, e, d, p, q, dp, dq, qi) whose public key is registered in your Okta API Services application
10939
+ secret: true
10940
+ doc_section: '#step-2-generating-and-registering-your-rsa-key-pair'
10941
+ connection_config:
10942
+ subdomain:
10943
+ type: string
10944
+ title: Okta Domain
10945
+ description: The subdomain of your Okta account
10946
+ pattern: '^[a-z0-9_-]+$'
10947
+ example: dev-12345678
10948
+ suffix: .okta.com
10949
+ prefix: https://
10950
+ doc_section: '#step-3-finding-your-okta-domain'
10951
+ oauth_scopes:
10952
+ type: string
10953
+ title: Scopes
10954
+ description: Space-separated list of Okta Management API scopes (e.g. okta.users.read okta.users.manage). Must be granted under Okta API Scopes on your application.
10955
+ example: okta.users.read okta.users.manage okta.groups.read
10956
+ doc_section: '#step-4-grant-api-scopes-to-your-application'
10957
+
10844
10958
  okta-preview:
10845
10959
  alias: okta
10846
10960
  display_name: Okta (Preview)
@@ -11744,8 +11858,8 @@ perplexity:
11744
11858
  type: string
11745
11859
  title: API Key
11746
11860
  description: The API key for your Perplexity account
11747
- pattern: '^pplx-[a-f0-9]+$'
11748
- example: pplx-xxxxxx
11861
+ pattern: '^pplx-[a-zA-Z0-9]+$'
11862
+ example: pplx-****************************
11749
11863
 
11750
11864
  perimeter81:
11751
11865
  display_name: Perimeter81
@@ -13600,6 +13714,59 @@ salesforce-cdp:
13600
13714
  secret: true
13601
13715
  doc_section: '#step-1-generating-your-encoded-jwt'
13602
13716
 
13717
+ salesmsg:
13718
+ display_name: Salesmsg (PAT)
13719
+ categories:
13720
+ - communication
13721
+ - marketing
13722
+ auth_mode: TWO_STEP
13723
+ body_format: json
13724
+ token_url: https://api.salesmessage.com/pub/v2.2/oauth/personal-token/refresh
13725
+ token_headers:
13726
+ authorization: Bearer ${credentials.apiKey}
13727
+ content-type: application/json
13728
+ refresh_token_headers:
13729
+ authorization: Bearer ${refresh_token}
13730
+ token_response:
13731
+ token: access_token
13732
+ token_expiration: expires_in
13733
+ token_expiration_strategy: expireIn
13734
+ refresh_token: access_token
13735
+ proxy:
13736
+ base_url: https://api.salesmessage.com/pub/
13737
+ headers:
13738
+ authorization: Bearer ${accessToken}
13739
+ docs: https://nango.dev/docs/api-integrations/salesmsg
13740
+ docs_connect: https://nango.dev/docs/api-integrations/salesmsg/connect
13741
+ credentials:
13742
+ apiKey:
13743
+ type: string
13744
+ title: Personal Access Token
13745
+ description: Your Salesmsg Personal Access Token (PAT).
13746
+ example: eyJhbGciOi***.eyJzdWIiOi***.xxxxxxxxxxxx
13747
+ pattern: '^[A-Za-z0-9-_]+\.[A-Za-z0-9-_]+\.[A-Za-z0-9-_]*$'
13748
+ doc_section: '#step-1-generating-your-personal-access-token'
13749
+
13750
+ salesmsg-oauth2:
13751
+ display_name: Salesmsg (OAuth2)
13752
+ categories:
13753
+ - communication
13754
+ - marketing
13755
+ auth_mode: OAUTH2
13756
+ authorization_url: https://app.salesmessage.com/auth/oauth
13757
+ token_url: https://api.salesmessage.com/pub/v2.2/oauth/token
13758
+ disable_pkce: true
13759
+ authorization_params:
13760
+ response_type: code
13761
+ token_params:
13762
+ grant_type: authorization_code
13763
+ refresh_params:
13764
+ grant_type: refresh_token
13765
+ proxy:
13766
+ base_url: https://api.salesmessage.com/pub/
13767
+ docs: https://nango.dev/docs/api-integrations/salesmsg-oauth2
13768
+ setup_guide_url: https://nango.dev/docs/api-integrations/salesmsg-oauth2/how-to-register-your-own-salesmsg-oauth-app
13769
+
13603
13770
  sap-fieldglass:
13604
13771
  display_name: SAP Fieldglass
13605
13772
  categories:
@@ -15356,6 +15523,30 @@ tailscale-api-key:
15356
15523
  pattern: '^tskey-api-[A-Za-z0-9]+CNTRL-[A-Za-z0-9]+$'
15357
15524
  doc_section: '#step-2-generating-an-api-access-token'
15358
15525
 
15526
+ tally:
15527
+ display_name: Tally
15528
+ categories:
15529
+ - productivity
15530
+ auth_mode: API_KEY
15531
+ proxy:
15532
+ base_url: https://api.tally.so
15533
+ headers:
15534
+ authorization: Bearer ${apiKey}
15535
+ verification:
15536
+ method: GET
15537
+ endpoints:
15538
+ - /forms?limit=1
15539
+ docs: https://nango.dev/docs/api-integrations/tally
15540
+ docs_connect: https://nango.dev/docs/api-integrations/tally/connect
15541
+ credentials:
15542
+ apiKey:
15543
+ type: string
15544
+ title: API Key
15545
+ description: Your Tally API key.
15546
+ pattern: '^tly-[A-Za-z0-9]{32}$'
15547
+ example: tly-84m**************************56Y
15548
+ doc_section: '#step-1-create-an-api-key'
15549
+
15359
15550
  tapclicks:
15360
15551
  display_name: TapClicks
15361
15552
  auth_mode: OAUTH2_CC
@@ -15836,12 +16027,13 @@ timify:
15836
16027
  - productivity
15837
16028
  auth_mode: TWO_STEP
15838
16029
  body_format: json
15839
- token_url: https://api.timify.com/v1/auth/token
16030
+ token_url: https://${connectionConfig.subdomain}.timify.com/v1/auth/token
16031
+ refresh_url: https://${connectionConfig.subdomain}.timify.com/v1/auth/refreshtoken
15840
16032
  token_params:
15841
16033
  appid: ${credentials.appId}
15842
16034
  appsecret: ${credentials.appSecret}
15843
16035
  refresh_token_params:
15844
- refreshToken: ${refresh_token}
16036
+ refreshtoken: ${refresh_token}
15845
16037
  token_headers:
15846
16038
  content-type: application/json
15847
16039
  accept: application/json
@@ -15851,23 +16043,34 @@ timify:
15851
16043
  token_expiration_strategy: expireIn
15852
16044
  refresh_token: refreshToken
15853
16045
  proxy:
15854
- base_url: https://api.timify.com
16046
+ base_url: https://${connectionConfig.subdomain}.timify.com
15855
16047
  headers:
15856
16048
  authorization: ${accessToken}
15857
16049
  docs: https://nango.dev/docs/api-integrations/timify
15858
16050
  docs_connect: https://nango.dev/docs/api-integrations/timify/connect
16051
+ connection_config:
16052
+ subdomain:
16053
+ type: string
16054
+ title: Timify Subdomain
16055
+ description: The subdomain of your Timify API.
16056
+ pattern: '^[a-z0-9_-]+$'
16057
+ example: api
16058
+ order: 1
16059
+ suffix: .timify.com
16060
+ prefix: https://
16061
+ doc_section: '#step-1-finding-your-subdomain'
15859
16062
  credentials:
15860
16063
  appId:
15861
16064
  type: string
15862
16065
  title: App ID
15863
16066
  description: Your Timify app ID
15864
- doc_section: '#step-2-getting-your-credentials'
16067
+ doc_section: '#step-3-getting-your-credentials'
15865
16068
  appSecret:
15866
16069
  type: string
15867
16070
  title: App Secret
15868
16071
  description: Your Timify app secret
15869
16072
  secret: true
15870
- doc_section: '#step-2-getting-your-credentials'
16073
+ doc_section: '#step-3-getting-your-credentials'
15871
16074
 
15872
16075
  todoist:
15873
16076
  display_name: Todoist