@nangohq/providers 0.71.10 → 0.71.12

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@nangohq/providers",
-    "version": "0.71.10",
+    "version": "0.71.12",
     "description": "Nango's providers.yaml and getters",
     "type": "module",
     "main": "./dist/index.js",
@@ -13,8 +13,8 @@
         "directory": "packages/providers"
     },
     "devDependencies": {
-        "@nangohq/types": "0.71.10",
-        "vitest": "4.1.9"
+        "@nangohq/types": "0.71.12",
+        "vitest": "4.1.11"
     },
     "files": [
         "dist/**/*",

package/providers.scopes.yaml

@@ -2772,6 +2772,11 @@ etsy: []
 # source: providers.yaml (no official scopes page or discovery endpoint found)
 eventbrite: []
 
+# source: https://free.eway-crm.com/31994/API/swagger.json (securityDefinitions.OAuth2.scopes)
+eway-crm:
+    - api
+    - offline_access
+
 # source: providers.yaml (no official scopes page or discovery endpoint found)
 exact-online: []
 
@@ -4770,6 +4775,25 @@ highlevel-white-label:
 # source: https://developerportal.thomsonreuters.com/authentication/documents/api-access-mechanism-using-oauth2 (no scopes parameter — API access is governed by the authenticated user's Collaborate permissions)
 highq: []
 
+# source: HitPay Passport scope definitions (parent scopes such as `payments` also grant their `:read`/`:create`/... children)
+hitpay:
+    - business:read
+    - commerce
+    - commerce:create
+    - commerce:delete
+    - commerce:read
+    - commerce:update
+    - customer
+    - customer:create
+    - customer:delete
+    - customer:read
+    - customer:update
+    - payments
+    - payments:cancel
+    - payments:create
+    - payments:read
+    - payments:refund
+
 # source: providers.yaml (no official scopes page or discovery endpoint found)
 hover: []
 

package/providers.yaml

@@ -767,6 +767,9 @@ affinity:
                 - 'x-ratelimit-limit-user'
                 - 'x-ratelimit-limit-org-reset'
     webhook_routing_script: affinityWebhookRouting
+    webhook_allowed_query_params:
+        - nangoConnectionId
+        - nangoWebhookSecret
     docs: https://nango.dev/docs/integrations/all/affinity
     docs_connect: https://nango.dev/docs/integrations/all/affinity/connect
     credentials:
@@ -1470,6 +1473,18 @@ a-leads:
             example: a3f8b2e1********************d9c4
             pattern: '^[a-f0-9]{32}$'
 
+anarlog-mcp:
+    display_name: Anarlog (MCP)
+    categories:
+        - mcp
+    auth_mode: MCP_OAUTH2_GENERIC
+    mcp_server_url: https://api.anarlog.so/mcp
+    proxy:
+        base_url: https://api.anarlog.so/mcp
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/anarlog-mcp
+
 anrok:
     display_name: Anrok
     categories:
@@ -2095,6 +2110,37 @@ aspire:
             example: 7hLp************************nHa5
             doc_section: '#step-2-generate-your-client-id-and-secret'
 
+astro-mcp:
+    display_name: Astro (MCP)
+    categories:
+        - dev-tools
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://api.astronomer.io/v1alpha1/astro/mcp/authorize
+    token_url: https://api.astronomer.io/v1alpha1/astro/mcp/token
+    registration_url: https://api.astronomer.io/v1alpha1/astro/mcp/register
+    default_scopes:
+        - offline_access
+    authorization_params:
+        response_type: code
+        resource: https://api.astronomer.io/v1alpha1/astro/mcp
+    registration_params:
+        response_types:
+            - code
+        grant_types:
+            - authorization_code
+            - refresh_token
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://api.astronomer.io
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/astro-mcp
+
 atlas-so:
     display_name: Atlas.so
     categories:
@@ -3466,6 +3512,72 @@ beehiiv:
             example: pub_a3d1b49e-2a5d-4f4b-97c8-8f32e1d2f7b9
             pattern: '^(pub_[0-9a-fA-F\-]+)$'
 
+beeline-vms:
+    display_name: Beeline VMS
+    categories:
+        - hr
+    auth_mode: OAUTH2_CC
+    body_format: json
+    token_url: https://integrations.${connectionConfig.authHost}.beeline.com/oauth/token
+    token_headers:
+        content-type: application/json
+        accept: application/json
+    token_params:
+        grant_type: client_credentials
+        audience: ${connectionConfig.audience}
+    proxy:
+        base_url: ${connectionConfig.audience}
+        headers:
+            accept: application/json
+        retry:
+            at:
+                - 'x-rate-limit-reset'
+            remaining: 'x-rate-limit-remaining'
+    docs: https://nango.dev/docs/api-integrations/beeline-vms
+    docs_connect: https://nango.dev/docs/api-integrations/beeline-vms/connect
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Client ID issued by your Beeline Customer Operations Manager (COM).
+            order: 1
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Client Secret issued alongside your Client ID.
+            secret: true
+            order: 2
+    connection_config:
+        authHost:
+            type: string
+            title: Authorization Server Region
+            description: The region your Beeline credentials were issued for.
+            enum:
+                - auth
+                - eu-auth
+            doc_section: '#step-2-choosing-your-region-and-audience'
+            order: 1
+        audience:
+            type: string
+            title: Audience
+            description: The audience Beeline granted your Client ID for.
+            enum:
+                - https://client.beeline.com/api
+                - https://client-eu.beeline.com/api
+                - https://edge.beeline.com/client-onboarding
+                - https://edge-eu.beeline.com/client-onboarding
+                - https://edge.beeline.com/worker
+                - https://edge-eu.beeline.com/worker
+                - https://edge-eu.beeline.com/reporting
+            doc_section: '#step-2-choosing-your-region-and-audience'
+            order: 2
+        clientSiteId:
+            type: string
+            title: Client Site ID
+            description: Issued alongside your Client credentials.
+            doc_section: '#step-1-getting-your-credentials-from-beeline'
+            order: 3
+
 bettercontact:
     display_name: BetterContact
     categories:
@@ -3606,6 +3718,50 @@ bill:
         base_url: https://gateway.prod.bill.com/connect
     docs: https://nango.dev/docs/integrations/all/bill
 
+billit:
+    display_name: Billit
+    categories:
+        - accounting
+        - invoicing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.apiHost}
+        headers:
+            apikey: ${apiKey}
+            partyid: ${connectionConfig.partyId}
+        verification:
+            method: GET
+            endpoints:
+                - /v1/einvoices/registrations
+    docs: https://nango.dev/docs/api-integrations/billit
+    docs_connect: https://nango.dev/docs/api-integrations/billit/connect
+    connection_config:
+        apiHost:
+            type: string
+            title: Environment
+            description: The Billit API environment to connect to.
+            enum:
+                - api.sandbox.billit.be
+                - api.billit.be
+            order: 1
+            doc_section: '#step-1-choose-your-environment'
+        partyId:
+            type: string
+            title: Master Account Party ID
+            description: The Registration ID of your Billit master account.
+            pattern: '^[0-9]+$'
+            example: '588999'
+            order: 2
+            doc_section: '#step-3-find-your-master-account-party-id'
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for a user with access to your Billit master account.
+            pattern: '^(?!.*\s).+$'
+            example: 'abcd1234********'
+            doc_section: '#step-2-get-your-api-key'
+
 bing-webmasters:
     display_name: Bing Webmasters
     categories:
@@ -5180,6 +5336,38 @@ clay:
             pattern: '^[a-f0-9]+$'
             doc_section: '#step-1-finding-your-api-key'
 
+clay-mcp:
+    display_name: Clay (MCP)
+    categories:
+        - crm
+        - marketing
+        - mcp
+    auth_mode: MCP_OAUTH2
+    client_registration: dynamic
+    authorization_url: https://app.clay.com/oauth/authorize
+    token_url: https://api.clay.com/oauth/token
+    registration_url: https://api.clay.com/oauth/register
+    default_scopes:
+        - mcp
+    authorization_params:
+        response_type: code
+        resource: https://api.clay.com/v3/mcp
+    registration_params:
+        response_types:
+            - code
+        grant_types:
+            - authorization_code
+            - refresh_token
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://api.clay.com
+        headers:
+            accept: application/json,text/event-stream
+    docs: https://nango.dev/docs/api-integrations/clay-mcp
+
 cleverreach:
     display_name: CleverReach
     categories:
@@ -6894,6 +7082,61 @@ digits-mcp:
         base_url: https://api.digits.com
     docs: https://nango.dev/docs/api-integrations/digits-mcp
 
+discogs:
+    display_name: Discogs
+    categories:
+        - e-commerce
+        - other
+    auth_mode: OAUTH1
+    request_url: https://api.discogs.com/oauth/request_token
+    authorization_url: https://www.discogs.com/oauth/authorize
+    token_url: https://api.discogs.com/oauth/access_token
+    signature_method: 'PLAINTEXT'
+    proxy:
+        base_url: https://api.discogs.com
+        headers:
+            user-agent: ${connectionConfig.userAgent} || NangoDiscogsIntegration/1.0 (+https://nango.dev; support@nango.dev)
+    docs: https://nango.dev/docs/api-integrations/discogs
+    setup_guide_url: https://nango.dev/docs/api-integrations/discogs/how-to-register-your-own-discogs-api-oauth-app
+    connection_config:
+        userAgent:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+
+discogs-token:
+    display_name: Discogs (Personal Access Token)
+    categories:
+        - e-commerce
+        - other
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.discogs.com
+        headers:
+            authorization: Discogs token=${apiKey}
+            user-agent: ${connectionConfig.userAgent} || NangoDiscogsIntegration/1.0 (+https://nango.dev; support@nango.dev)
+        verification:
+            method: GET
+            endpoints:
+                - /oauth/identity
+    docs: https://nango.dev/docs/api-integrations/discogs-token
+    docs_connect: https://nango.dev/docs/api-integrations/discogs-token/connect
+    connection_config:
+        userAgent:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+    credentials:
+        apiKey:
+            type: string
+            title: Personal Access Token
+            description: The personal access token for your Discogs account
+            example: hpJEgq**********UPY
+            pattern: '^[A-Za-z0-9]+$'
+            doc_section: '#step-1-generating-your-personal-access-token'
+
 discolike:
     display_name: DiscoLike
     categories:
@@ -6936,6 +7179,36 @@ discord:
     docs: https://nango.dev/docs/api-integrations/discord
     setup_guide_url: https://nango.dev/docs/api-integrations/discord/how-to-register-your-own-discord-api-oauth-app
 
+discord-bot:
+    display_name: Discord Bot
+    categories:
+        - gaming
+        - social
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://discord.com
+        retry:
+            after:
+                - 'retry-after'
+        headers:
+            authorization: Bot ${apiKey}
+        verification:
+            method: GET
+            headers:
+                accept: application/json
+            endpoints:
+                - /api/v10/applications/@me
+    docs: https://nango.dev/docs/api-integrations/discord-bot
+    docs_connect: https://nango.dev/docs/api-integrations/discord-bot/connect
+    credentials:
+        apiKey:
+            type: string
+            title: Bot Token
+            description: Your Discord bot token from the Discord Developer Portal.
+            example: MTIzNDU2Nzg5MDEyMzQ1Njc4.******.**********************************
+            pattern: '^[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$'
+            doc_section: '#step-1-creating-a-discord-application-and-bot'
+
 discourse:
     display_name: Discourse
     categories:
@@ -7923,6 +8196,93 @@ epc-gov-uk:
             example: 'a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2c3d4e5f6a1b2'
             doc_section: '#step-2-finding-your-api-key'
 
+eclinicalworks:
+    display_name: eClinicalWorks (FHIR)
+    categories:
+        - other
+    auth_mode: TWO_STEP
+    body_format: form
+    token_url: https://${connectionConfig.oauthServerUrl}/oauth/oauth2/token
+    token_params:
+        grant_type: client_credentials
+        client_assertion_type: urn:ietf:params:oauth:client-assertion-type:jwt-bearer
+        client_assertion: ${credentials.assertion}
+        scope: ${credentials.scope}
+    token_headers:
+        content-type: application/x-www-form-urlencoded
+        accept: application/json
+    assertion:
+        type: jwt
+        singleUse: true
+        key: ${credentials.privateKey}
+        lifetimeInSeconds: 300
+        header:
+            alg: RS384
+            kid: ${credentials.keyId}
+        payload:
+            iss: ${credentials.clientId}
+            sub: ${credentials.clientId}
+            aud: https://${connectionConfig.oauthServerUrl}/oauth/oauth2/token
+            jti: ${random}
+    token_response:
+        token: access_token
+        token_expiration: expires_in
+        token_expiration_strategy: expireIn
+    proxy:
+        base_url: https://${connectionConfig.fhirBaseUrl}
+        headers:
+            accept: application/fhir+json
+    docs: https://nango.dev/docs/api-integrations/eclinicalworks
+    setup_guide_url: https://nango.dev/docs/api-integrations/eclinicalworks/how-to-register-your-own-eclinicalworks-app
+    docs_connect: https://nango.dev/docs/api-integrations/eclinicalworks/connect
+    connection_config:
+        fhirBaseUrl:
+            type: string
+            prefix: https://
+            title: FHIR Base URL
+            description: This practice's eClinicalWorks FHIR R4 base URL.
+            example: fhir4.eclinicalworks.com/fhir/r4/SANDBOX
+            doc_section: '#step-1-finding-your-fhir-base-url'
+            order: 1
+        oauthServerUrl:
+            type: string
+            prefix: https://
+            title: OAuth Server URL
+            description: This practice's eClinicalWorks OAuth issuer URL.
+            example: oauthserver.eclinicalworks.com
+            doc_section: '#step-2-finding-your-oauth-server-url'
+            order: 2
+    integration_config:
+        clientId:
+            type: string
+            title: Client ID
+            description: Your registered application's Client ID from the eClinicalWorks Dev Portal.
+            order: 1
+        keyId:
+            type: string
+            title: Key ID
+            description: The kid of the RSA key registered in your hosted JWKS file.
+            order: 2
+        privateKey:
+            type: string
+            title: Private Key
+            description: The RSA private key (PEM) matching your published JWKS public key. Signed with RS384.
+            secret: true
+            order: 3
+        scope:
+            type: string
+            title: Scope
+            description: >-
+                The SMART Backend Services scope(s) granted to this Client ID (e.g. system/Patient.read).
+                Include system/Group.read only for bulk Group/$export requests, and omit it for single-patient backend access.
+            order: 4
+    credentials:
+        assertion:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+
 epic:
     display_name: Epic (FHIR)
     categories:
@@ -8141,6 +8501,35 @@ everflow:
             description: The API key for your Everflow account.
             doc_section: '#step-1-generate-your-api-key'
 
+eway-crm:
+    display_name: eWay-CRM
+    categories:
+        - crm
+    auth_mode: OAUTH2
+    authorization_url: https://${connectionConfig.serviceUrl}/auth/connect/authorize
+    token_url: https://${connectionConfig.serviceUrl}/auth/connect/token
+    disable_pkce: true
+    scope_separator: ' '
+    default_scopes:
+        - offline_access
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    proxy:
+        base_url: https://${connectionConfig.serviceUrl}/API.svc
+    docs: https://nango.dev/docs/api-integrations/eway-crm
+    docs_connect: https://nango.dev/docs/api-integrations/eway-crm/connect
+    setup_guide_url: https://nango.dev/docs/api-integrations/eway-crm/how-to-register-your-own-eway-crm-api-oauth-app
+    connection_config:
+        serviceUrl:
+            type: string
+            title: Service URL
+            description: Your eWay-CRM Web Service address.
+            prefix: https://
+            example: free.eway-crm.com/31994
+            doc_section: '#step-1-finding-your-web-service-address'
+
 etsy:
     display_name: Etsy
     categories:
@@ -8882,6 +9271,8 @@ fillout-api-key:
             endpoints:
                 - /v1/api/forms
     webhook_routing_script: filloutWebhookRouting
+    webhook_allowed_query_params:
+        - nangoWebhookSecret
     docs: https://nango.dev/docs/integrations/all/fillout-api-key
     docs_connect: https://nango.dev/docs/integrations/all/fillout-api-key/connect
     connection_config:
@@ -8914,6 +9305,8 @@ fillout:
     token_response_metadata:
         - base_url
     webhook_routing_script: filloutWebhookRouting
+    webhook_allowed_query_params:
+        - nangoWebhookSecret
     docs: https://nango.dev/docs/integrations/all/fillout
     connection_config:
         base_url:
@@ -11209,6 +11602,9 @@ halo-psa:
         - support
         - ticketing
     auth_mode: OAUTH2_CC
+    webhook_routing_script: haloPsaWebhookRouting
+    webhook_allowed_query_params:
+        - nangoConnectionId
     token_url: https://${connectionConfig.hostname}/auth/token
     token_request_auth_method: basic
     scope_separator: ' '
@@ -11581,6 +11977,36 @@ highq:
             example: acme.highq.com/main
             doc_section: '#step-1-find-your-hostname'
 
+hitpay:
+    display_name: HitPay App
+    categories:
+        - payment
+        - e-commerce
+    auth_mode: OAUTH2
+    authorization_url: https://dashboard.${connectionConfig.environment}/oauth/authorize
+    token_url: https://api.${connectionConfig.environment}/v1/open/oauth/token
+    authorization_params:
+        response_type: code
+    token_params:
+        grant_type: authorization_code
+    refresh_params:
+        grant_type: refresh_token
+    proxy:
+        base_url: https://api.${connectionConfig.environment}
+    docs: https://nango.dev/docs/api-integrations/hitpay
+    setup_guide_url: https://nango.dev/docs/api-integrations/hitpay/how-to-register-your-own-hitpay-oauth-app
+    docs_connect: https://nango.dev/docs/api-integrations/hitpay/connect
+    connection_config:
+        environment:
+            type: string
+            title: Environment
+            description: The HitPay environment to connect to. Use sandbox.hit-pay.com with sandbox app credentials.
+            doc_section: '#step-1-choose-your-environment'
+            enum:
+                - hit-pay.com
+                - sandbox.hit-pay.com
+                - staging.hit-pay.com
+
 holded:
     display_name: Holded
     categories:
@@ -12786,6 +13212,28 @@ jobber:
             description: ''
             automated: true
 
+jobnimbus:
+    display_name: JobNimbus
+    categories:
+        - crm
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://app.jobnimbus.com/
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /api1/contacts
+    docs: https://nango.dev/docs/api-integrations/jobnimbus
+    docs_connect: https://nango.dev/docs/api-integrations/jobnimbus/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your JobNimbus API Key.
+            doc_section: '#step-1-generate-your-api-key'
+
 jobvite:
     display_name: Jobvite
     categories:
@@ -14270,6 +14718,30 @@ mailchimp:
             example: us6
             automated: true
 
+mailerlite:
+    display_name: MailerLite
+    categories:
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://connect.mailerlite.com/api
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /groups?limit=1
+    docs: https://nango.dev/docs/api-integrations/mailerlite
+    docs_connect: https://nango.dev/docs/api-integrations/mailerlite/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Token
+            description: Your MailerLite API token.
+            example: eyJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.****************.**********
+            pattern: '^eyJ[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+\.[A-Za-z0-9_-]+$'
+            doc_section: '#step-1-generate-your-mailerlite-api-token'
+
 mailjet:
     display_name: Mailjet
     categories:
@@ -14301,6 +14773,38 @@ mailjet:
             example: 'f6e5d4c3b2a1f0e9d8c7b6a5f4e3d2c1'
             doc_section: '#step-1-getting-your-credentials'
 
+mailtrap:
+    display_name: Mailtrap
+    categories:
+        - communication
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://${connectionConfig.subdomain}.api.mailtrap.io
+        headers:
+            api-token: ${apiKey}
+    docs: https://nango.dev/docs/api-integrations/mailtrap
+    docs_connect: https://nango.dev/docs/api-integrations/mailtrap/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Token
+            description: Your Mailtrap API token.
+            example: a1b2c3d4********************e5f6
+            pattern: '^[a-f0-9]{32}$'
+            secret: true
+            doc_section: '#step-2-getting-your-api-token'
+    connection_config:
+        subdomain:
+            type: string
+            title: API Environment
+            description: The Mailtrap API environment to connect to. Use 'send' for live or 'sandbox' for sandbox.
+            order: 1
+            enum:
+                - send
+                - sandbox
+            doc_section: '#step-1-choose-your-environment'
+
 mandrill:
     display_name: Mandrill
     categories:
@@ -15711,17 +16215,95 @@ modmed:
             doc_section: '#step-1-request-access-to-modmed-sandbox'
         password:
             type: string
-            title: Password
-            description: Your API password
+            title: Password
+            description: Your API password
+            secret: true
+            doc_section: '#step-1-request-access-to-modmed-sandbox'
+        apiKey:
+            type: string
+            title: API Key
+            description: Your API key (x-api-key)
+            secret: true
+            example: a1b2c3d4-e5f6-47a8-9b0c-d1234567890f
+            doc_section: '#step-1-request-access-to-modmed-sandbox'
+
+modmed-fhir:
+    display_name: ModMed (FHIR)
+    categories:
+        - other
+    auth_mode: TWO_STEP
+    body_format: form
+    token_url: https://sso.ema.md/auth/realms/fhir/protocol/openid-connect/token
+    token_params:
+        grant_type: client_credentials
+        client_assertion_type: urn:ietf:params:oauth:client-assertion-type:jwt-bearer
+        client_assertion: ${credentials.assertion}
+        scope: ${credentials.scope}
+    token_headers:
+        content-type: application/x-www-form-urlencoded
+        accept: application/json
+    assertion:
+        type: jwt
+        singleUse: true
+        key: ${credentials.privateKey}
+        lifetimeInSeconds: 300
+        header:
+            alg: ES384
+            kid: ${credentials.keyId}
+        payload:
+            iss: ${credentials.clientId}
+            sub: ${credentials.clientId}
+            aud: https://sso.ema.md/auth/realms/fhir/protocol/openid-connect/token
+            jti: ${random}
+    token_response:
+        token: access_token
+        token_expiration: expires_in
+        token_expiration_strategy: expireIn
+    proxy:
+        base_url: https://${connectionConfig.fhirHost}
+        headers:
+            accept: application/fhir+json
+    docs: https://nango.dev/docs/api-integrations/modmed-fhir
+    setup_guide_url: https://nango.dev/docs/api-integrations/modmed-fhir/how-to-register-your-own-modmed-fhir-app
+    docs_connect: https://nango.dev/docs/api-integrations/modmed-fhir/connect
+    integration_config:
+        clientId:
+            type: string
+            title: Client ID
+            description: Your Bulk FHIR application's Client ID from the ModMed FHIR vendor dashboard.
+            order: 1
+        keyId:
+            type: string
+            title: Key ID
+            description: The kid of the EC (P-384) key registered in your hosted JWKS file.
+            order: 2
+        privateKey:
+            type: string
+            title: Private Key
+            description: The EC (P-384) private key (PEM) matching your published JWKS public key. Signed with ES384.
             secret: true
-            doc_section: '#step-1-request-access-to-modmed-sandbox'
-        apiKey:
+            order: 3
+        scope:
             type: string
-            title: API Key
-            description: Your API key (x-api-key)
-            secret: true
-            example: a1b2c3d4-e5f6-47a8-9b0c-d1234567890f
-            doc_section: '#step-1-request-access-to-modmed-sandbox'
+            title: Scope
+            description: The space-separated system/*.rs scopes granted to your Bulk FHIR application.
+            order: 4
+    credentials:
+        assertion:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+    connection_config:
+        fhirHost:
+            type: string
+            prefix: https://
+            title: FHIR Host
+            description: This practice's ModMed Certified FHIR host.
+            example: fhirmp.mmi.prod.fhir.ema-api.com
+            pattern: '^[a-zA-Z0-9-]+\.[a-zA-Z0-9-]+\.prod\.fhir\.ema-api\.com$'
+            doc_section: '#step-1-finding-your-fhir-host'
+            order: 1
 
 mural:
     display_name: Mural
@@ -17147,6 +17729,37 @@ orange-logic:
             order: 1
             doc_section: '#step-1-find-your-orange-logic-url'
 
+omnisend:
+    display_name: Omnisend
+    categories:
+        - marketing
+        - e-commerce
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.omnisend.com
+        headers:
+            authorization: Omnisend-API-Key ${apiKey}
+            omnisend-version: ${connectionConfig.apiVersion} || '2026-03-15'
+        retry:
+            after:
+                - 'retry-after'
+    docs: https://nango.dev/docs/api-integrations/omnisend
+    docs_connect: https://nango.dev/docs/api-integrations/omnisend/connect
+    connection_config:
+        apiVersion:
+            type: string
+            title: ''
+            description: ''
+            automated: true
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: Your Omnisend API key.
+            example: 6ab55b0af9*******f39f53-Tr7yFM*****************************Hs3v
+            pattern: '^[A-Za-z0-9_-]+$'
+            doc_section: '#step-2-create-an-omnisend-api-key'
+
 openai:
     display_name: OpenAI
     categories:
@@ -17231,6 +17844,32 @@ open-hands:
             example: 'aNVlyRBLGWJgnVp1vwXN7TkO1MCYxeIDz'
             doc_section: '#step-1-finding-your-api-key'
 
+openrouter:
+    display_name: OpenRouter
+    categories:
+        - dev-tools
+        - productivity
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://openrouter.ai
+        headers:
+            authorization: Bearer ${apiKey}
+            content-type: application/json
+        verification:
+            method: GET
+            endpoints:
+                - /api/v1/key
+    docs: https://nango.dev/docs/api-integrations/openrouter
+    docs_connect: https://nango.dev/docs/api-integrations/openrouter/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key for your OpenRouter account.
+            pattern: '^sk-or-v1-[a-f0-9]{64}$'
+            example: sk-or-v1-a3f9**************************************7c2d
+            doc_section: '#step-1-create-your-api-key'
+
 optum-real:
     display_name: Optum Real
     categories:
@@ -18838,7 +19477,7 @@ pleo-api-key:
             title: API Key
             description: Your Pleo Standalone API Key.
             example: pls_********************************_620d75
-            pattern: '^pls_[a-f0-9]+_[a-f0-9]+$'
+            pattern: '^pl[sp]_[a-f0-9]+_[a-f0-9]+$'
             doc_section: '#step-1-generating-your-api-key'
 
 podium:
@@ -18925,6 +19564,36 @@ posthog:
             example: phx_1PPf***************************k3D
             doc_section: '#step-2-finding-your-api-key'
 
+posthog-capture:
+    display_name: PostHog (Capture API)
+    categories:
+        - dev-tools
+    auth_mode: API_KEY
+    proxy:
+        body:
+            api_key: ${apiKey}
+        base_url: https://${connectionConfig.hostname}
+    docs: https://nango.dev/docs/api-integrations/posthog-capture
+    docs_connect: https://nango.dev/docs/api-integrations/posthog-capture/connect
+    connection_config:
+        hostname:
+            type: string
+            title: Hostname
+            description: The hostname your PostHog capture API requests are sent to.
+            format: hostname
+            prefix: https://
+            example: us.i.posthog.com
+            order: 1
+            doc_section: '#step-1-finding-your-hostname'
+    credentials:
+        apiKey:
+            type: string
+            title: Project Token
+            description: Your PostHog project token, used to send events via the capture API.
+            pattern: '^phc_[A-Za-z0-9]+$'
+            example: phc_1PPf***************************k3D
+            doc_section: '#step-2-finding-your-project-token'
+
 posthog-oauth:
     display_name: PostHog (OAuth)
     categories:
@@ -22584,6 +23253,8 @@ shipstation:
             endpoints:
                 - /users
     webhook_routing_script: shipstationWebhookRouting
+    webhook_allowed_query_params:
+        - nangoWebhookSecret
     docs: https://nango.dev/docs/integrations/all/shipstation
     docs_connect: https://nango.dev/docs/integrations/all/shipstation/connect
     credentials:
@@ -22621,6 +23292,8 @@ shipstation-v2:
             endpoints:
                 - /v2/users?page_size=1
     webhook_routing_script: shipstationWebhookRouting
+    webhook_allowed_query_params:
+        - nangoWebhookSecret
     docs: https://nango.dev/docs/integrations/all/shipstation-v2
     docs_connect: https://nango.dev/docs/integrations/all/shipstation-v2/connect
     credentials:
@@ -23013,6 +23686,49 @@ shortcut:
             title: API Key
             description: The API key for your Shortcut account
 
+simpplr:
+    display_name: Simpplr
+    categories:
+        - knowledge-base
+        - productivity
+    auth_mode: OAUTH2_CC
+    token_url: https://platform.${connectionConfig.region}.simpplr.com/v1/identity/oauth/token
+    body_format: json
+    token_params:
+        grant_type: client_credentials
+    proxy:
+        base_url: https://platform.${connectionConfig.region}.simpplr.com
+    docs: https://nango.dev/docs/api-integrations/simpplr
+    docs_connect: https://nango.dev/docs/api-integrations/simpplr/connect
+    connection_config:
+        region:
+            type: string
+            title: Region
+            description: The region your Simpplr tenant is hosted in. Choose app for the United States.
+            enum:
+                - app
+                - eu
+                - au
+                - ca
+            order: 1
+            doc_section: '#step-2-find-your-region'
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: The Client ID of your Simpplr client application.
+            pattern: '^\S+$'
+            example: 7f3a91c2****************************e85b
+            doc_section: '#step-1-create-a-client-application'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: The Client Secret of your Simpplr client application.
+            pattern: '^\S+$'
+            example: b41d7e60********************************************9af2
+            secret: true
+            doc_section: '#step-1-create-a-client-application'
+
 simpro:
     display_name: Simpro
     categories:
@@ -23074,6 +23790,42 @@ slack:
     docs: https://nango.dev/docs/api-integrations/slack
     setup_guide_url: https://nango.dev/docs/api-integrations/slack/how-to-register-your-own-slack-api-oauth-app
 
+slack-app-configuration:
+    display_name: Slack (Configuration Token)
+    categories:
+        - dev-tools
+    auth_mode: TWO_STEP
+    body_format: form
+    token_url: https://slack.com/api/tooling.tokens.rotate
+    token_params:
+        refresh_token: ${credentials.refresh_token}
+    refresh_token_params:
+        refresh_token: ${refresh_token}
+    token_headers:
+        content-type: application/x-www-form-urlencoded
+        accept: application/json
+    token_response:
+        token: token
+        refresh_token: refresh_token
+        token_expiration: exp
+        token_expiration_strategy: expireAt
+    proxy:
+        base_url: https://slack.com/api
+        retry:
+            after:
+                - 'retry-after'
+    docs: https://nango.dev/docs/api-integrations/slack-app-configuration
+    docs_connect: https://nango.dev/docs/api-integrations/slack-app-configuration/connect
+    credentials:
+        refresh_token:
+            type: string
+            title: App configuration refresh token
+            description: Slack app configuration refresh token.
+            secret: true
+            pattern: '^xoxe-1-[A-Za-z0-9_-]+$'
+            example: xoxe-1-A08************************
+            doc_section: '#step-1-generate-an-app-configuration-token'
+
 slack-mcp:
     display_name: Slack (MCP)
     categories:
@@ -23762,6 +24514,8 @@ streak:
                 content-type: application/json
                 accept: application/json
     webhook_routing_script: streakWebhookRouting
+    webhook_allowed_query_params:
+        - nangoConnectionId
     docs: https://nango.dev/docs/api-integrations/streak
     docs_connect: https://nango.dev/docs/api-integrations/streak/connect
     credentials:
@@ -24136,6 +24890,40 @@ swoogo:
             secret: true
             doc_section: '#step-1-generate-your-api-credentials'
 
+symplr-ctm:
+    display_name: symplr CTM (ClearConnect)
+    categories:
+        - hr
+        - ats
+    auth_mode: BASIC
+    proxy:
+        base_url: https://ctms.contingenttalentmanagement.com/${connectionConfig.siteName}/clearConnect
+        verification:
+            method: GET
+            endpoints:
+                - /2_0/index.cfm?action=getRegions&resultType=json
+    docs: https://nango.dev/docs/api-integrations/symplr-ctm
+    docs_connect: https://nango.dev/docs/api-integrations/symplr-ctm/connect
+    connection_config:
+        siteName:
+            type: string
+            title: Site Name
+            description: Your CTM customer site name.
+            order: 1
+            example: myCTM
+    credentials:
+        username:
+            type: string
+            title: Username
+            description: Your ClearConnect API username.
+            doc_section: '#step-1-locate-your-clearconnect-credentials'
+        password:
+            type: string
+            title: Password
+            description: Your ClearConnect API password.
+            secret: true
+            doc_section: '#step-1-locate-your-clearconnect-credentials'
+
 syncore:
     display_name: Syncore
     categories:
@@ -24716,6 +25504,32 @@ terraform:
             example: VbQo****************************
             pattern: '^[a-zA-Z0-9.]{50,}$'
 
+textus:
+    display_name: TextUs
+    categories:
+        - communication
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://next.textus.com
+        headers:
+            authorization: Bearer ${apiKey}
+            accept: application/vnd.textus+jsonld
+            content-type: application/vnd.textus+jsonld
+        verification:
+            method: GET
+            endpoints:
+                - /accounts
+    docs: https://nango.dev/docs/api-integrations/textus
+    docs_connect: https://nango.dev/docs/api-integrations/textus/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Token
+            description: Your TextUs API Token.
+            example: eyJhbGciOi***.eyJzdWIiOi***.***************************
+            doc_section: '#step-1-generate-an-api-token'
+
 ticktick:
     display_name: TickTick
     categories:
@@ -24924,6 +25738,48 @@ trakstar-hire:
             default_value: ''
             hidden: true
 
+tracify:
+    display_name: Tracify
+    categories:
+        - analytics
+        - marketing
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://tracify-api.tracify.ai
+        headers:
+            tracify-token: ${apiKey}
+        verification:
+            method: GET
+            headers:
+                accept: application/json
+            endpoints:
+                - /analytics/api/v1/kpis/overview/?csids=${connectionConfig.siteId}&preset_id=${connectionConfig.presetId}&start_date=1970-01-01&end_date=1970-01-01&granularity=none&requested_metrics=customer_revenue
+    docs: https://nango.dev/docs/api-integrations/tracify
+    docs_connect: https://nango.dev/docs/api-integrations/tracify/connect
+    connection_config:
+        siteId:
+            type: string
+            title: Site ID
+            description: Your Tracify site ID.
+            format: uuid
+            order: 1
+            doc_section: '#step-2-finding-your-site-id'
+        presetId:
+            type: string
+            title: Preset ID
+            description: Your Tracify attribution preset ID.
+            order: 2
+            doc_section: '#step-3-finding-your-preset-id'
+    credentials:
+        apiKey:
+            type: string
+            title: Analytics API Token
+            description: Your Tracify Analytics API token.
+            example: tracify_abc123****************
+            pattern: '^[A-Za-z0-9_-]+$'
+            order: 1
+            doc_section: '#step-1-generating-an-analytics-api-token'
+
 trafft:
     display_name: Trafft
     categories:
@@ -25970,6 +26826,56 @@ ukg-pro-wfm:
             example: wfm
             doc_section: '#step-1-finding-your-tenant-url-and-tenant-name'
 
+ukg-pro-wfm-cc:
+    display_name: UKG Pro (Workforce Management Client Credentials)
+    categories:
+        - hr
+    auth_mode: OAUTH2_CC
+    body_format: json
+    token_url: https://welcome-us.ukg.net/oauth/token
+    token_headers:
+        content-type: application/json
+    token_params:
+        grant_type: client_credentials
+        audience: https://wfm.ukg.net/api
+        organization: ${connectionConfig.organization}
+    proxy:
+        base_url: https://${connectionConfig.hostname}/api
+        retry:
+            after:
+                - 'retry-after'
+    docs: https://nango.dev/docs/api-integrations/ukg-pro-wfm-cc
+    docs_connect: https://nango.dev/docs/api-integrations/ukg-pro-wfm-cc/connect
+    credentials:
+        client_id:
+            type: string
+            title: Client ID
+            description: Client ID for a client configured for the client credentials flow.
+            doc_section: '#step-1-finding-your-client-id-and-client-secret'
+        client_secret:
+            type: string
+            title: Client Secret
+            description: Client Secret for that client.
+            secret: true
+            doc_section: '#step-1-finding-your-client-id-and-client-secret'
+    connection_config:
+        organization:
+            type: string
+            title: Organization
+            description: The organization ID specific to your tenant.
+            doc_section: '#step-2-finding-your-organization-id'
+            order: 2
+        hostname:
+            type: string
+            title: Tenant URL
+            description: The tenant URL of your UKG Pro instance.
+            format: hostname
+            example: wfm.us1.ukg.com
+            suffix: /api
+            prefix: https://
+            doc_section: '#step-3-finding-your-tenant-url'
+            order: 1
+
 ukg-pro-wfm-ropc:
     display_name: UKG Pro (Workforce Management ROPC)
     categories:
@@ -26878,7 +27784,8 @@ webflow:
         grant_type: authorization_code
     proxy:
         base_url: https://api.webflow.com
-    docs: https://nango.dev/docs/integrations/all/webflow
+    docs: https://nango.dev/docs/api-integrations/webflow
+    setup_guide_url: https://nango.dev/docs/api-integrations/webflow/how-to-register-your-own-webflow-api-oauth-app
 
 webex:
     display_name: Webex
@@ -26927,6 +27834,31 @@ webinarjam:
             format: uuid
             doc_section: '#step-1-getting-your-api-key'
 
+weflow:
+    display_name: Weflow
+    categories:
+        - communication
+        - crm
+        - video
+    auth_mode: API_KEY
+    proxy:
+        base_url: https://api.getweflow.app
+        headers:
+            authorization: Bearer ${apiKey}
+        verification:
+            method: GET
+            endpoints:
+                - /api/v1/summary-templates
+    docs: https://nango.dev/docs/api-integrations/weflow
+    docs_connect: https://nango.dev/docs/api-integrations/weflow/connect
+    credentials:
+        apiKey:
+            type: string
+            title: API Key
+            description: The API key from your Weflow workspace.
+            example: wfl_****************************
+            doc_section: '#step-1-create-your-api-key'
+
 wejam:
     display_name: WeJam AI
     categories: