# Rapidbott CRM Mini App Integration The Rapidbott CRM Mini App Integration is the native integration built for Rapidbott workspaces. It helps users move chatbot contacts, pipeline records, tasks, and follow-up work into Rapidbott CRM without needing to manage separate systems manually. This page is written for users who want to install and use the Rapidbott CRM Mini App from inside the Rapidbott platform. **Image Placeholder** Add a screenshot of the Rapidbott CRM Mini App card in the Mini App Store here. *** ### Overview The Rapidbott CRM Mini App Integration helps users manage chatbot contacts, pipelines, tasks, and follow-ups inside a CRM experience built for Rapidbott workspaces. This integration includes: * workspace eligibility validation * secure workspace access with OTP and embed token support * contact sync from chatbot subscribers * manual contact creation and CSV contact import * multi-pipeline CRM boards with Kanban, list, and flow views * pipeline record assignment, movement, and activity logs * analytics dashboard, AI-style insights, and follow-up task generation The goal of this integration is simple: help teams turn chatbot activity into structured CRM work. *** ### What This Integration Is For If users want to move contacts from the chatbot into CRM, they should use the Rapidbott CRM Mini App Integration built for this purpose. This integration is useful when users want to: * bring chatbot contacts into the CRM * search for an existing CRM record using a user identifier * create a new CRM record in a selected pipeline * add another record for the same contact into a selected stage * move an existing record to a different stage * continue team follow-up in a full CRM workspace This is the recommended user path for chatbot-to-CRM workflows inside Rapidbott. *** ### Where To Install Install the Rapidbott CRM Mini App from the Dashboard Mini App Store. Once installed, the Mini App can be used from the Rapidbott workspace where it was connected. **Image Placeholder** Add a screenshot showing where the Mini App is installed from the Dashboard Mini App Store. *** ### What Users Must Provide During Installation During installation, users must enter the Workspace ID for the workspace where they want to install and use the CRM Mini App. This is important because the Mini App must know exactly which Rapidbott workspace should be connected to the CRM. #### Where to find Workspace ID Users can find the Workspace ID in their Workspace Settings. If the wrong Workspace ID is entered, the CRM Mini App may not open the correct workspace or may fail eligibility checks. *** ### Eligibility Requirements This is one of the most important parts of the integration. A workspace is eligible for CRM access only if: * the workspace exists * the workspace is active and not paused * the workspace has an active paid plan such as Pro Plan or higher, or an active trial If a workspace is on a free plan without an active trial, CRM access is not available. #### In simple user-facing wording Users can access the Rapidbott CRM Mini App only when their Rapidbott workspace is valid and eligible for CRM usage. If access is denied, the most common reasons are: * the workspace ID is incorrect * the workspace is paused * the workspace is on a free plan without an active trial * the workspace is no longer active *** ### Additional OTP Requirement If the workspace uses OTP login, the workspace must have a valid workspace owner email available. This email is used to send the verification code needed to complete login. If the workspace owner email is missing or unavailable, OTP verification cannot be completed. #### OTP guidance for users If users are unable to receive the OTP code, they should first check: * whether the workspace owner email is set correctly * whether they are using the correct workspace * whether the workspace is eligible for CRM access *** ### How Access Works The integration supports secure workspace access methods designed for the Rapidbott product flow. Depending on the usage scenario, access may happen through: * OTP verification * embed token flow * secure workspace launch From the user perspective, the important outcome is that the Mini App opens the CRM in the correct workspace context securely. Users do not need to know the backend details behind these access flows. *** ### What Users Can Do Inside the Mini App The Rapidbott CRM Mini App can expose actions that help users work with CRM data from within their Rapidbott flow. Based on the current integration, the action set includes: * Add Record to Same Pipeline Stage * Create a Record in Pipeline * Find CRM Records * Move a Record Using Record ID **Image Placeholder** Add the action selection screenshot here. #### 1. Add Record to Same Pipeline Stage This action adds another record for the same contact or user into a selected stage in the same pipeline. Use this when: * the same contact needs another separate record * the user is already part of that workflow * you want a new item created without replacing the earlier one Typical use cases: * repeated follow-up requests * multiple cases for the same user * additional sales or service events in the same process #### 2. Create a Record in Pipeline This action creates a new record in the selected pipeline and stage. Use this when: * the customer should be entered into a CRM workflow for the first time * a chatbot journey should create a new lead or support item * a new opportunity or service case needs to start in the CRM Typical use cases: * create a new lead from chatbot interaction * create a new support ticket * create a new follow-up record in the correct pipeline #### 3. Find CRM Records This action searches and retrieves CRM records using a user identifier such as phone, email, or user NS. Use this when: * you want to check whether the contact already exists in CRM * you need to retrieve earlier deal or ticket context * you want to avoid creating a duplicate record unnecessarily This action is especially useful before creating a new record. #### 4. Move a Record Using Record ID This action moves an existing record to a selected stage using the record ID. Use this when: * a record needs to progress to the next stage * chatbot logic confirms a new status * the workflow should reflect updated customer progress Typical use cases: * move a sales record after qualification * move a support record after review * move a customer into the next operational stage automatically *** ### What Happens After Installation After the Mini App is installed and linked to a valid workspace, users can continue work inside the CRM using the full product experience. This can include: * syncing contacts from chatbot subscribers * managing contacts manually * importing contacts through CSV * creating and managing multiple pipelines * switching between Kanban, list, and flow views * assigning records * moving records between stages * reviewing activity logs * using dashboard analytics * reviewing AI-style insights * generating follow-up tasks This is where the Mini App becomes more than a connector. It becomes the bridge between chatbot activity and structured CRM execution. *** ### Recommended User Flow For most users, the best flow is: 1. install the CRM Mini App from the Dashboard Mini App Store 2. enter the correct Workspace ID 3. confirm the workspace is eligible 4. complete OTP or secure access if required 5. use Find CRM Records first when checking an existing user 6. create or add a record only when needed 7. move records as the workflow progresses 8. continue management inside the full CRM workspace *** ### Common Troubleshooting #### The Mini App does not open the CRM Check: * the Workspace ID is correct * the workspace exists * the workspace is active * the workspace is not paused * the workspace has an active paid plan or active trial #### The user cannot receive the OTP code Check: * the workspace owner email is available * the workspace owner email is valid * the correct workspace is being used #### CRM access is denied The most common causes are: * invalid workspace ID * paused workspace * free plan without active trial * expired or inactive workspace state #### A user is not sure whether to create or find a record Recommended guidance: * use Find CRM Records first if the user may already exist * use Create a Record in Pipeline for a new CRM entry * use Add Record to Same Pipeline Stage when another separate record is needed for the same contact * use Move a Record Using Record ID when the record already exists and only the stage should change *** ### Best Practices * always confirm the Workspace ID before installation * use Find CRM Records before creating duplicates * keep pipelines aligned with real business processes * move records only when the status truly changes * use the Mini App for chatbot-to-CRM handoff, then continue deeper work in the full CRM ***