Create an app on developer.clomni.ai: step by step

Last updated: 11 November 2026 · 7 min read

Steps

1. 1

   Sign in and accept the terms

   Open developer.clomni.ai and press “Sign in with Clomni”. The Developer Terms open on your first sign-in (version 2026-11-09). You cannot create an app until you accept them. The main rules: selling workspace data or using it for advertising is forbidden, tokens are kept only on a server, and if there is a breach you tell Clomni within 72 hours at most.

2. 2

   Create an app

   The “New app” button opens a three-step form:

   1. Name (up to 60 characters) and a short description (up to 500 characters).
   2. Workspace: the list shows only the workspaces where you are an administrator. Then pick a preset or choose scopes.
   3. Final check.

   Choose the kind: an internal app for your own workspace, or “Public app” for an app other companies will connect. The kind cannot be changed later. One person can have at most 50 apps. If there is no workspace in the list, you are not an administrator of any workspace: ask an administrator for the role.

3. 3

   Pick a preset

   The preset selects the scopes for you, and you remove what you do not need later:

   • “Clomni in my own panel”: show conversations in your own system, write replies, assign.
   • “CRM sync”: keep contacts and conversations in sync with your CRM.
   • “BI and reporting”: pull report figures into a BI tool.
   • “Data export”: export data in bulk.
   • “AI management”: manage AI agents and the knowledge base with code.

   What each scope does is in the “Which scopes you need: scopes and endpoints by what you want to do” article.

4. 4

   Fill in the app's details

   Enter these in the app's settings. Review looks at them:

   • website, privacy policy link (with https://), terms of use link;
   • support email;
   • data deletion link: a page that explains how you delete data received from Clomni when the app is removed;
   • company name and tax ID (VOEN, 10 digits).

   For a public app you also fill in redirect URIs (at most 10) and the catalog listing.

5. 5

   Send the scopes for review

   A new scope has the “Draft” status. In the review form write, in at least 100 characters, why you want each scope, and send it. A Clomni team member looks at it, and the decision comes by email. The form's fields and rejection reasons: the “Review: checking scopes” article. While you wait for review, you can test on the test channel.

   The “Go live” checklist on the app's overview page shows what is left: privacy policy link, scope requested, review sent, scope approved, token created (first installation for a public app), first request. For a public app also: redirect URI, listing ready, and visible in the catalog.

6. 6

   Create a token

   Once at least one scope is approved, press “Create token” in the app's “Credentials” section: choose a name, scopes and a lifetime (30, 60, 90, 180 or 365 days). The token is shown only once: save it right away somewhere safe. For a server integration you can also create a client secret with “Create secret”. More: the “Tokens and authentication in the Developer API” article.

7. 7

   App statuses

   • Draft: no scope has been sent.
   • In review: a review is pending and no scope is approved yet.
   • Changes requested: the last review asked for changes.
   • Live: at least one scope is approved. When you add a new scope, the app stays Live.
   • Rejected: every scope was rejected.
   • Suspended: Clomni suspended the app and its tokens were revoked.
   • Archived: you deleted the app. All its tokens are revoked and its webhook is turned off. If it is a public app, it is removed from every workspace that connected it.

   Create the app from the company's permanent account: when the app owner is not an administrator in the workspace, the tokens do not work.