After our Kommo node is verified, can n8n Cloud add our OAuth client ID and secret via Credential overwrites so Cloud users can connect without self-hosting? Docs: https://docs.n8n.io/embed/configuration/#credential-overwrites

Questions
1

Hi guys!. I have a quick question regarding the next steps for our upcoming node at Kommo. Can we, as a company that is planning to get the node verified, expect that after the publication and moderation of our package with the node, you will add our record with the client ID and client secret into Credential overwrites on your side? So that users who don’t have a self-hosted n8n instance (use the cloud version) will be able to connect to our public integration. Link to the article about Credential overwrites: https://docs.n8n.io/embed/configuration/#credential-overwrites Example of our record:

{
  "kommoOAuth2Api": {
    "clientId": "public_integration_client_id",
    "clientSecret": "public_integration_client_secret"
  }
}

Thanks in advance for clarifying.

2

Hey @Oscar07, we want to introduce a feature to enable this in a self-served way, so for now please proceed with the verification and stay tuned for when we release more information around the credentials.