Website integration

What this type is for

Choose Website integration when the primary interface and business logic live in an external service and a user needs to connect a Senler AI project to it. Examples include a CRM, payment service, analytics product, or an account area on the developer's website.

Connection starts on the external site. The user approves the requested permissions in Senler AI, after which the integration server receives OAuth tokens and calls the API on behalf of the connected project.

What the user receives

• an application card in the plugin catalog that opens the developer's website;
• a clear OAuth screen listing the requested permissions;
• a link to the application's documentation when the developer has published it.

This type does not add tools to agents or display an embedded page inside the cabinet. Use Tool for those capabilities. Use Ready-made solution when a complete set of resources must be installed into a project.

What the developer configures

1. Add the name, description, avatar, website, and public documentation in the common application settings.
2. Save allowed Redirect URIs, select the minimum required permissions, and store the Client Secret securely. See OAuth settings.
3. Exchange authorization_code for an access token on the server, renew it through refresh_token, and never send the Client Secret to the browser.
4. When needed, declare agent events, add webhooks, and publish service documentation.

Project access

Creating the application and knowing its Client ID or Client Secret does not grant access to project data. Access begins only after the user explicitly approves OAuth and is limited to the selected permissions. Removing the connection or revoking the token ends the external service's access.

Before publication

Check the developer website, a working HTTPS Redirect URI, Russian and English texts, the minimum permission set, the access revocation flow, and user documentation. Then submit the application for moderation from Catalog publication.