Creating the Mobile app (App SDK) channel and where its settings are

Last updated: 9 October 2026 · 13 min read

In Clomni, each mobile app is one “Mobile app (App SDK)” channel: its messages, keys and settings are in one place. An administrator creates it. One channel serves one app, its Android and iOS versions together.

Steps

  1. 1

    Open the catalog

    On Settings › Workspace settings › Inboxes, click “Add Inbox”. In the catalog, click “Connect” on the “Mobile app (App SDK)” card.

    If the card is missing, the channel is not on for your account. The Clomni team turns it on: write to Clomni AI, and it passes the request to the team.

  2. 2

    Step 1: App details

    • “Channel name”: the name agents see in the channel list, for example “Example app”.
    • “Platforms”: iOS, Android or both.
    • “Android package name”: applicationId in app/build.gradle(.kts), for example com.example.app.
    • “iOS Bundle ID”: the Bundle Identifier of the app target in Xcode (Signing & Capabilities). The iOS SDK sends the app's Bundle ID when it connects, and if it differs from the one here, the server refuses the key. Type the package name and the Bundle ID carefully: the dashboard has no place to change them once the channel exists, and the Clomni team fixes a mistake.
    • “Take the look from a website chat”: your website chat's colour, logo and texts become the starting values. Or “Don't, use the default look”.

    Click “Create”. The channel and its keys are created at once.

  3. 3

    Step 2: Installation

    The App ID, “Android API key” and “iOS API key” are shown with a “Copy” button, and there is ready code for each platform. Copy the keys now: they are shown in full only in this step. Later the dashboard shows only the beginning of a key. If a key is lost, make a new one with “New key” in the Installation section.

  4. 4

    Step 3: Identity verification

    The Identity Secret is shown once. Store it on your server (for example CLOMNI_IDENTITY_SECRET) and never put it in the app. Tick “I have stored the secret safely”. Leave “Mode” on “Recommended” for now.

  5. 5

    Steps 4 to 6: Push, Appearance, Flows

    • “Push notifications”: the Firebase service account JSON (Android) and the APNs .p8 key (iOS). If they are not ready, “Do it later”.
    • “Appearance”: main colour, logo, greeting, theme and floating button.
    • “Flows”: choose the “New conversation flow”. It is copied to this channel as a draft. The Messenger runs it only once it is published.

    A step skipped with “Do it later” stays as a warning on the channel's “Overview” until it is done. At the end, “Finish”.

  6. 6

    The channel page and its settings column

    Open the channel later from the Settings › Workspace settings › Inboxes list. The channel's settings are in their own column next to the dashboard's menu. The channel name is at the top of the column; the ← button on its right goes back to the list of inboxes. The sections are in three groups:

    • APP: “Overview”, “Installation”, “Security”, “Push”, “Guide”.
    • MESSENGER: “Appearance”, “Flows”, “News”, “CSAT”, and “Bot Configuration” when bots are on for the account.
    • INBOX: “Settings”, “Collaborators”, “Business Hours”, “Analytics”.

    The open section is highlighted in the column. On a narrow screen (under 900 px), the column becomes a dropdown at the top of the page. These articles write the path like this: Settings › Workspace settings › Inboxes › your channel › settings column › Installation.

  7. 7

    Overview

    The first place to look when something does not work. The status of each platform: “Not installed”, “Installed” (a session in the last 30 days), “Securely installed” (the mode is enforced and there was a verified login in the last 7 days), “Push keys added”, “Push active”. “Warnings” names the problem, for example logins refused for a wrong hash or an old SDK. “Fix” opens the right section.

  8. 8

    Installation

    • “API keys”: the App ID and the beginning of each platform's key, with “Copy”.
    • “New key” makes a new key for that platform and shows it in full once. The old key keeps working for 7 more days, after that app versions with the old key cannot connect.
    • “Revoke” stops a key at once. Use it for a leaked key.
    • “Code”: ready code with your App ID in it.
    • “Recent devices”: the devices that connected last, with model, OS, app and SDK version and last seen time. A device shows up here a few seconds after the app calls initialize and opens a session.
  9. 9

    Security

    • “Mode”: “Off”, “Recommended” or “Enforced”. The choice takes effect with “Save”.
    • “Identity Secret” › “Make a new secret”: the new secret is shown once, the old one keeps working for 7 more days.
    • “Test a hash”: enter the user_id and the user_hash your server made, then click “Check”. The dashboard says whether the hash was made with the current secret, with the old one, or does not match.
    • “The hash on your server”: ready code for Node.js, PHP, Python, .NET and Java.

    More in “Mobile SDK keys and identifying users (user_hash)”.

  10. 10

    Push

    • “Android · Firebase Cloud Messaging” and “iOS · Apple Push Notification service”: the keys are uploaded here, renewed with “Replace” and deleted with “Remove”.
    • “Last 7 days”: per platform, “Sent”, “Failed”, “Removed tokens” and “Skipped” (not sent because there was no key).
    • “Notification title”: what the first line of a notification says.
    • “Test push”: sends a test push to the device you choose.

    How to get the keys and what the answers mean: “Mobile SDK push keys: Firebase (FCM) and APNs”.

  11. 11

    Guide

    • “Download the guide (PDF)”: this guide in four languages: Azerbaijani, English, Turkish and Russian. The dashboard's language comes first.
    • “Online guide language”: the links below open the guide in this language.
    • “Platforms”: cards for Android, iOS, React Native, Flutter and Unity. Each card has the package's install line with “Copy” and an “Online guide” link to that platform's chapter.
    • “Other chapters”: “Overview”, “Panel settings”, “User identity”, “Push keys”, “Troubleshooting”.
  12. 12

    Collaborators and Analytics

    • “Collaborators”: the agents who see this channel's conversations. An agent who is not here does not see conversations from the app.
    • “Analytics”: active devices (last day, 7 and 30 days), conversations, first reply time, pushes sent and SDK versions.
  13. 13

    Full guide

Document