🛠️

Integrations

7 articles Ruut CSM Mona Olamilekan By Ruut CSM, Mona, and Olamilekan

Find help with any sort of integrations you would like to attain with Ruut

How to Integrate the Ruut Flutter SDK

Ruut Flutter Chat SDK Documentation A simple and powerful Flutter SDK to integrate real-time chat into your Flutter app using Ruut. Connect with your visitors instantly and provide exceptional support. Overview The Ruut Flutter Chat SDK allows you to add a fully-featured chat interface to your Flutter app. It supports real-time messaging, file attachments, customizable themes, and offline message storage. Key Features - Real-time messaging with WebSocket support - File and image attachments - Customizable UI themes - Offline message persistence - Typing indicators - User avatars and names - Message status (sending, delivered, read) - Customer Satisfaction (CSAT) surveys Installation 1. Add Dependency Add the ruut_flutter package to your pubspec.yaml file. Check the latest version. dependencies: ruut_flutter: ^latest_version 2. Install Dependencies Run the following command in your terminal: flutter pub get Basic Setup 1. Create an API Channel Follow the steps here to create an API channel on the Ruut server and get your inboxIdentifier. 2. Implement RuutChat Widget Add the RuutChat widget to your app: import 'package:flutter/material.dart'; import 'package:ruut_flutter/ruut_chat.dart'; import 'package:ruut_flutter/data/local/entity/ruut_user.dart'; void main() { runApp(MyApp()); } class MyApp extends StatelessWidget { @override Widget build(BuildContext context) { return MaterialApp( title: 'Ruut Chat Demo', home: Scaffold( body: RuutChat( inboxIdentifier: 'your_inbox_identifier', user: RuutUser( identifier: 'user_123', name: 'John Doe', email: '[email protected]', ), ), ), ); } } Replace your_inbox_identifier with the inbox identifier from your Ruut API channel. Note: The SDK uses Hive for local storage. Configuration Required Parameters - inboxIdentifier: Your Ruut inbox identifier (String, required). Optional Parameters Parameter Type Default Description enablePersistence bool true Enables saving messages and conversations to disk for offline access. user RuutUser null Custom user details (e.g., name, email, avatar). theme RuutChatTheme Default Customizes the chat UI (colors, fonts, icons). callbacks RuutCallbacks null Handles real-time events (e.g., message received, typing started). Custom User Setup RuutChat( inboxIdentifier: 'your_inbox_identifier', user: RuutUser( identifier: 'unique_user_id', name: 'Jane Doe', email: '[email protected]', avatarUrl: 'https://example.com/avatar.jpg', customAttributes: { 'plan': 'premium', 'signup_date': '2024-01-01', }, ), ) Theme Customization RuutChat( inboxIdentifier: 'your_inbox_identifier', theme: RuutChatTheme( primaryColor: Colors.blue, backgroundColor: Colors.white, inputBackgroundColor: Colors.grey[100], userAvatarNameColors: [Colors.black, Colors.white], attachmentButtonIcon: Icon(Icons.image_outlined, color: Colors.grey), ), ) Callbacks Use RuutCallbacks to handle real-time events: RuutChat( inboxIdentifier: 'your_inbox_identifier', callbacks: RuutCallbacks( onMessageReceived: (ruutMessage) { print('New message: ${ruutMessage.content}'); }, onMessageSent: (ruutMessage, echoId) { print('Message sent: ${ruutMessage.content}'); }, onError: (error) { print('Error: ${error.cause}'); }, onConversationStartedTyping: () { print('Agent is typing...'); }, onConversationIsOnline: () { print('Agent is online'); }, ), ) Available Callbacks Callback Description onWelcome Connection established. onMessageReceived New message from agent. onMessageSent Message sent successfully. onMessageDelivered Message delivered to server. onConversationStartedTyping Agent started typing. onConversationStoppedTyping Agent stopped typing. onConversationIsOnline Agent is online. onConversationIsOffline Agent is offline. onError Error occurred. Troubleshooting Common Issues 1. Chat Not Connecting - Verify your inboxIdentifier and Ruut server URL. - Example: RuutClient.create( baseUrl: 'https://app.ruut.chat', inboxIdentifier: 'correct_identifier', ); 2. File Upload Fails - Check file size limits and network connection. - Handle errors: onError: (error) { if (error.type == RuutClientExceptionType.SEND_MESSAGE_FAILED) { print('Upload failed. Check connection and retry.'); } } 3. Messages Not Persisting - Ensure enablePersistence is set to true: RuutChat( inboxIdentifier: 'your_inbox_identifier', enablePersistence: true, ) 4. Theme Not Applied - Verify theme properties: RuutChat( theme: RuutChatTheme( primaryColor: Colors.blue, backgroundColor: Colors.white, ), ) Enable Debug Mode Add debug logging for troubleshooting: void initState() { super.initState(); debugPrint('Ruut Chat initialized'); } Error Handling RuutChat( callbacks: RuutCallbacks( onError: (error) { switch (error.type) { case RuutClientExceptionType.CREATE_CLIENT_FAILED: print('Failed to initialize chat'); break; case RuutClientExceptionType.SEND_MESSAGE_FAILED: print('Message failed to send'); break; default: print('Unknown error: ${error.cause}'); } }, ), ) If issues persist, contact us at [email protected]. Best Practices 1. Error Handling: Implement robust error handling for all callbacks. 2. User Feedback: Show loading states and error messages to users. 3. Performance: Use pagination for large message histories: RuutChat( onEndReachedThreshold: 0.75, onEndReached: () async { await ruutClient?.loadMessages(); }, ) 4. Security: Validate user inputs and handle sensitive data securely. 5. Testing: Test on various devices and network conditions. Updating the SDK 1. Check for Updates: flutter pub outdated 2. Update Dependencies: flutter pub upgrade 3. Review Changelog: Check for breaking changes and test after updates. Support - Check example implementations on GitHub. - For issues, contact [email protected].

Integrating Ruut to your Wordpress site. Here's how.

If you're using WordPress for your website, you can easily integrate live chat support for your visitors with Ruut. By adding the Ruut live chat widget to your WordPress site, you can connect with your customers in real-time, answering their questions and addressing their concerns without the hassle of manual back-and-forth communication. Here's how you can get started in 4 simple steps: Step 1. Download the Ruut Plugin. Download the Zip file of the latest Ruut WordPress plugin from here Step 2. Upload the plugin to your WordPress website Log in to your WordPress account. Navigate to the Admin Panel and click “Plugins” from the sidebar. You will be able to see the "Add New" button. You will see an option to upload the plugin, as shown in the screenshot below. Click “Browse” and select the Zip file downloaded in step 1. Step 3. Activate the plugin Once the plugin is uploaded, you will see a Success screen with the "Activate Plugin" option, as shown below. Click the "Activate Plugin” button. Congrats! The plugin is now installed, you would see a Ruut Plugin view as shown below. To complete the configuration, you must add your Ruut app credentials. Step 4. Configure the plugin Now, you will be able to see “Ruut Settings” under your "Settings" menu. Click on that to update the live-chat configuration. You will be presented with the Settings screen as shown below. Configure your Ruut plugin here to make it work. You need to create a Website inbox on your Ruut installation. Please refer to this guide to create a website channel inbox. Once you have your inbox channel created. copy the website token from the website channel setting and include it below in the field called Ruut Website Token. Once you complete the form, click the "Save changes" button. ** Step 5. Verify that the plugin is working correctly** Visit your website and see if the widget appears on the website!

Integration Ruut React Native Widget

Overview The Ruut React Native Widget allows you to integrate a Ruut chat widget into your React Native application. This documentation will guide you through the installation, usage, and customization of the widget. Installation You can install the Ruut React Native Widget library using either yarn or npm: yarn add @ruut/react-native-client or npm install --save @ruut/react-native-client Dependencies This library requires react-native-webview and async-storage. Please refer to their respective documentation for installation instructions. iOS Installation For React Native versions > 60.0, follow these steps to complete the installation: cd ios && pod install Usage To use the Ruut Widget, follow these steps: 1. Create a Website Channel: Set up a website channel in the Ruut server by following the steps described here. 2. Replace websiteToken Prop: Use the token obtained from the above step to replace the placeholder in the example code below. Example Code import React, { useState } from 'react'; import { StyleSheet, View, SafeAreaView, TouchableOpacity, Text } from 'react-native'; import RuutWidget from '@ruut/react-native-client'; const App = () => { const [showWidget, toggleWidget] = useState(false); const user = { identifier: '[email protected]', name: 'John Samuel', avatar_url: '', email: '[email protected]', identifier_hash: '', }; const customAttributes = { accountId: 1, pricingPlan: 'paid', status: 'active' }; const websiteToken = 'WEBSITE_TOKEN'; // Replace with your actual website token const locale = 'en'; const colorScheme = 'dark'; return ( <SafeAreaView style={styles.container}> <View> <TouchableOpacity style={styles.button} onPress={() => toggleWidget(true)}> <Text style={styles.buttonText}>Open Widget</Text> </TouchableOpacity> </View> { showWidget && <RuutWidget websiteToken={websiteToken} locale={locale} closeModal={() => toggleWidget(false)} isModalVisible={showWidget} user={user} customAttributes={customAttributes} colorScheme={colorScheme} /> } </SafeAreaView> ); }; const styles = StyleSheet.create({ container: { flex: 1, justifyContent: 'center', alignItems: 'center', }, button: { height: 48, marginTop: 32, paddingTop: 8, paddingBottom: 8, backgroundColor: '#1F93FF', borderRadius: 8, borderWidth: 1, borderColor: '#fff', justifyContent: 'center', }, buttonText: { color: '#fff', textAlign: 'center', paddingLeft: 10, fontWeight: '600', fontSize: 16, paddingRight: 10, }, }); export default App; Props Here is a list of props you can use with the RuutWidget component: - websiteToken - Type: String - Default: - - Description: Website channel token. - colorScheme - Type: String - Default: light - Description: Widget color scheme. Options are light, dark, or auto. - locale - Type: String - Default: en - Description: Locale setting for the widget. - isModalVisible - Type: Boolean - Default: false - Description: Determines if the widget is visible or not. - closeModal - Type: Function - Default: - - Description: Function to handle the widget close event. - user - Type: Object - Default: {} - Description: User information such as email, username, and avatar URL. - customAttributes - Type: Object - Default: {} - Description: Additional information about the customer. https://www.npmjs.com/package/@ruut/react-native-client For detailed support, contact our support team.

How to Integrate Ruut with Linear to Track Issues and Feature Requests

The Linear integration in Ruut allows you to seamlessly convert customer conversations into actionable tasks in your Linear workspace. With this integration, your support team can quickly escalate bugs, feature requests, or feedback to your product team—without ever leaving Ruut. What Can You Do with the Linear Integration? - Create new issues in Linear directly from a Ruut conversation - Link existing Linear issues to ongoing customer threads - Track issue progress from within Ruut - Keep your support and product teams aligned ✅ Prerequisites Before you begin, make sure: 1. You have a Ruut account with Admin privileges. 2. You have a Linear account with access to the workspace you want to connect. 3. Your Ruut workspace supports integrations (check with your Ruut plan if unsure). 🔧 How to Connect Linear with Ruut 1. Navigate to application in Ruut: - Go to your Ruut dashboard - Click on Settings > Application - Select Linear from the list 2. Authorize Access: - Click on Connect Linear - A dialog would appear to enter your API Key - Go to your linear dashboard and locate the settings - Look for Security and access > and generate a Personal API key - Copy the generated API key to Ruut 3. Complete Setup: - Save your settings - You’ll now see the Linear integration as “Enabled” - Go to your conversation next you should see the Linear icon as described in the image below 🛠 How to Use the Integration 🔹 Create a New Issue from a Ruut Conversation 1. Open any customer conversation in Ruut 2. Click the Linear logo 3. A modal pops up to either add a new issue or link an existing issue to a particular conversation: 4. Click Create 📝 The Linear issue will now be linked to the conversation. A note will be added so all team members can see the connection. 🔗 Link to an Existing Linear Issue 1. In a Ruut conversation, click on More actions > Link Linear Issue 2. Search for the existing issue by name or ID 3. Select and confirm This is useful for when multiple customers are reporting the same problem. 👀 Track Issue Status Once an issue is linked, you can: - View issue status and updates directly within Ruut - Click through to view the issue in Linear - Stay informed about when an issue is closed or updated 🙋 Common Use Cases - Escalate bugs reported by customers - Track feedback for product improvements - Keep customer support and product teams in sync - Avoid duplicate reports by linking to existing Linear issues 📌 Final Notes The Ruut + Linear integration helps you streamline internal workflows and deliver better experiences to customers. No more toggling between tools—everything happens in context. Need help? Contact support or reach out to your Ruut success manager.

How to Connect Your Meta Pixel With Ruut's Conversions API

Connect your Meta Pixel to Ruut's Conversions API to send conversation events server-side for better ad attribution and retargeting — no code required. What is Meta Conversions API? If you run Facebook or Instagram ads, Meta Pixel helps you understand what people do after interacting with your ads. However, browser privacy settings and ad blockers can prevent some events from being tracked. Meta Conversions API (CAPI) solves this by sending events directly from Ruut to Meta. Once connected, Ruut can automatically tell Meta when important actions happen, such as: - A customer starts a conversation - A customer sends a message - An agent replies - A conversation is resolved - A customer leaves a satisfaction rating This gives Meta more information to measure your ads and build better audiences. Tip: You don't need to remove your existing Meta Pixel. Pixel and Conversions API work together. Before You Start You'll need two things from Meta: 1. Your Meta Pixel ID Go to Meta Events Manager and select your Pixel. You'll find your Pixel ID near the top of the page. It usually looks like this: 123456789012345 2. Your Access Token In Meta Events Manager: 1. Select your Pixel 2. Open Settings 3. Find Conversions API 4. Click Generate Access Token 5. Copy the token Keep your Access Token private. Treat it like a password. Connect Meta to Ruut Step 1 — Open Integrations From your Ruut dashboard, go to: Settings → Integrations Step 2 — Select Meta Conversions API Find Meta Conversions API and click Configure. Step 3 — Connect Click Connect. Enter your: - Meta Pixel ID - Access Token Step 4 — Test your connection Click Test Configuration. Ruut will send a test event to Meta to make sure your credentials are working. Green confirmation: Everything is working. Error message: Double-check your Pixel ID and Access Token. Step 5 — Save Click Connect to finish. That's it. Once connected, you'll see a green indicator showing that Meta Conversions API is active. What Ruut Sends to Meta Once connected, Ruut automatically sends supported conversation events to Meta. | Event | What it means | | ------------------------------- | -------------------------------------- | | Conversation Started | A customer starts a new conversation | | Message Sent | A customer sends a message | | Agent Replied | An agent replies to the customer | | Conversation Resolved | The conversation is marked as resolved | | Customer Satisfaction Rated | A customer submits a CSAT rating | | File Uploaded | A customer uploads a file | You don't need to manually send these events. Ruut handles them automatically in the background. Where Can I See My Events? Open Meta Events Manager and select the Pixel connected to Ruut. New events should begin appearing within a few minutes. You can use these events to: - Measure conversions from your ads - Build Custom Audiences - Retarget customers - Understand which ads lead to conversations - Improve campaign attribution How Does It Work? When something happens in Ruut — for example, a customer starts a conversation — Ruut sends the event directly to Meta's Conversions API. This happens securely in the background and doesn't slow down your inbox. Where applicable, customer information such as email addresses and phone numbers is hashed before being sent to Meta. Frequently Asked Questions Will this replace my Meta Pixel? No. Conversions API works alongside your existing Meta Pixel. Your Pixel tracks browser activity while Ruut sends supported events directly from the server. Does it cost anything? Meta doesn't charge separately to use the Conversions API. Ruut's Meta Conversions API integration is available at no additional charge where included in your plan. Can I disconnect it? Yes. Go to: Settings → Integrations → Meta Conversions API Then click Disconnect Meta Conversions API. Ruut will stop sending new events. Will this slow down Ruut? No. Events are sent in the background, so they won't affect your team's conversations or response times. What data does Ruut send? Ruut sends information required to identify the event and improve attribution, such as: - Event type - Event timestamp - Relevant conversation information - Available customer identifiers used for matching Sensitive customer identifiers supported by Meta's matching requirements are hashed where required before transmission. Why can't I see my events in Meta? Check the following: 1. Make sure your Meta integration is connected in Ruut. 2. Confirm you're viewing the correct Pixel in Meta Events Manager. 3. Wait a few minutes for new events to appear. 4. Use Test Configuration in Ruut to confirm your credentials are valid. Troubleshooting | Problem | What to do | | ---------------------------------- | --------------------------------------------------------------- | | Test Configuration fails | Check your Pixel ID and Access Token | | Events aren't appearing | Wait a few minutes and confirm you're viewing the correct Pixel | | Integration shows disconnected | Reconnect your Meta account from Settings → Integrations | | Access Token was revoked | Generate a new token from Meta Events Manager and reconnect | Need Help? If you're having trouble connecting Meta Conversions API, contact the Ruut support team from your dashboard or email [email protected]. We'll help you get connected.

Receiving Real-Time Events With Ruut Webhooks

Get real-time notifications when events happen in Ruut - conversations created, messages sent, contacts updated and more - delivered straight to your endpoint What Are Webhooks? Instead of constantly asking Ruut "anything new?", a webhook lets Ruut tell you the moment something happens. When a customer sends a message, when a conversation is resolved, when a new contact is created — Ruut sends an HTTP POST to your URL with the event data. This means you can: - Sync data to your CRM, database, or analytics platform in real time - Trigger automations in Zapier, n8n, Make, or your own backend - Build custom workflows that react instantly to customer interactions What You'll Need Before setting up a webhook: - A URL that accepts HTTP POST requests — This is where Ruut will send event data. It must be publicly accessible and respond with a 2xx status code. - Administrator access — Only account admins can create and manage webhooks. Setting Up a Webhook ::::steps :::step{title="Open Integrations"} From your Ruut dashboard, go to Settings → Integrations and find Webhook. ::: :::step{title="Click Add Webhook"} Click the Add Webhook button to open the configuration form. ::: :::step{title="Enter Your Endpoint URL"} Paste the URL where you want to receive webhook payloads. This must be a valid http:// or https:// URL. :::callout{type="tip" title="Use HTTPS"} We recommend using HTTPS endpoints. Your endpoint must return a 2xx response within 5 seconds. ::: ::: :::step{title="Give It a Name (Optional)"} Add a descriptive name so you can identify this webhook later — for example, "CRM Sync" or "Analytics Pipeline". ::: :::step{title="Select Events"} Choose which events you want to receive. You can subscribe to multiple events on the same webhook: | Event | When It Fires | | ----------------------------- | ---------------------------------------------- | | conversation_created | A new conversation is created | | conversation_status_changed | A conversation is opened, resolved, or snoozed | | conversation_updated | Conversation attributes are updated | | message_created | A new message is sent in a conversation | | message_updated | An existing message is edited | | contact_created | A new contact is created | | contact_updated | A contact's details are updated | | webwidget_triggered | The chat widget is opened by a visitor | | inbox_created | A new inbox is created | | inbox_updated | An inbox's settings are changed | | conversation_typing_on | Someone starts typing in a conversation | | conversation_typing_off | Someone stops typing | ::: :::step{title="Save"} Click Create to activate your webhook. Ruut will immediately start sending events to your endpoint. ::: :::: Verifying Webhook Signatures :::callout{type="warning" title="Always verify signatures"} Without verification, anyone could send fake payloads to your endpoint. Always validate the signature before processing a webhook. ::: Every webhook payload is signed with an HMAC-SHA256 signature using a secret key that's auto-generated when you create the webhook. You can view and copy this secret from the webhook form in your dashboard. How Verification Works Each request includes three headers: | Header | Description | | ------------------ | ----------------------------------------------- | | X-Ruut-Signature | The HMAC-SHA256 signature of the payload | | X-Ruut-Timestamp | The Unix timestamp when the webhook was sent | | X-Ruut-Delivery | A unique ID for this delivery (for idempotency) | To verify a payload: 1. Read the X-Ruut-Timestamp header and the raw request body 2. Compute the HMAC: HMAC-SHA256(your_secret, "#{timestamp}.#{body}") 3. Compare your result with the X-Ruut-Signature header (ignoring the sha256= prefix) 4. If they match, the payload is authentic ::::tabs :::tab{title="Ruby"} def verify_ruut_signature(secret, timestamp, body, signature) expected = "sha256=" + OpenSSL::HMAC.hexdigest( 'SHA256', secret, "#{timestamp}.#{body}" ) ActiveSupport::SecurityUtils.secure_compare(expected, signature) end ::: :::tab{title="Python"} import hmac, hashlib def verify_ruut_signature(secret, timestamp, body, signature): expected = "sha256=" + hmac.new( secret.encode(), f"{timestamp}.{body}".encode(), hashlib.sha256 ).hexdigest() return hmac.compare_digest(expected, signature) ::: :::tab{title="Node.js"} const crypto = require('crypto'); function verifyRuutSignature(secret, timestamp, body, signature) { const expected = 'sha256=' + crypto .createHmac('sha256', secret) .update(`${timestamp}.${body}`) .digest('hex'); return crypto.timingSafeEqual(Buffer.from(expected), Buffer.from(signature)); } ::: :::: :::callout{type="tip" title="Replay protection"} To prevent replay attacks, check that the X-Ruut-Timestamp is within an acceptable window (e.g., 5 minutes) of the current time. ::: Payload Structure Every webhook sends a JSON payload with this structure: { "event": "message_created", "timestamp": "2026-09-04T12:00:00Z", "data": { "id": 12345, "conversation": { "id": 678, "display_id": 42, "status": "open" }, "contact": { "id": 910, "name": "Jane Doe", "email": "[email protected]" }, "message": { "id": 11213, "content": "Hi, I need help with my order", "message_type": "incoming", "created_at": "2026-09-04T12:00:00Z" } } } The data object varies depending on the event type, but always includes the relevant IDs and attributes. Handling Responses Your endpoint should: - Return a 2xx status code (e.g., 200 OK) to acknowledge receipt - Respond within 5 seconds — otherwise Ruut considers it a failure - Process the payload asynchronously if your logic takes longer :::callout{type="warning" title="Don't block on slow operations"} If your webhook handler needs to do heavy work (writing to a database, calling external APIs), accept the payload immediately, return 200, and process it in a background job. ::: Retries If your endpoint returns a non-2xx status or times out, Ruut will not retry the delivery. Ensure your endpoint is reliable and always returns a success response quickly. For critical workflows, consider: - Using a queue-based handler that acknowledges immediately and processes later - Monitoring your endpoint for failures - Logging all incoming webhook IDs (X-Ruut-Delivery) for debugging Frequently Asked Questions ::::accordion :::accordion-item{title="Can I have multiple webhooks?"} Yes. You can create multiple webhooks, each with its own URL, name, and event subscriptions. This is useful if you want different systems to receive different events. ::: :::accordion-item{title="Can I subscribe to the same event on multiple webhooks?"} Yes. The same event can be sent to as many webhooks as you configure. ::: :::accordion-item{title="What happens if my endpoint is down?"} The webhook delivery will fail. Ruut does not retry failed deliveries, so your endpoint should be highly available. Use a queue-based handler for critical workflows. ::: :::accordion-item{title="Is there a rate limit?"} Webhooks are delivered in real time as events occur. If you need to throttle or batch, implement that on your receiving end. ::: :::accordion-item{title="Can I see delivery history?"} Currently, webhook delivery logs are not exposed in the dashboard. Use your own endpoint logs and the X-Ruut-Deliveryheader to track individual deliveries. ::: :::accordion-item{title="How do I rotate my webhook secret?"} You can regenerate the secret from the webhook form in your dashboard. Update your verification logic with the new secret immediately — the old secret will stop working after regeneration. ::: :::: Troubleshooting | Problem | What to Try | | ------------------------------ | ------------------------------------------------------------------------------------ | | Not receiving events | Check that you've subscribed to the right events and your URL is publicly accessible | | Getting 502 or timeout errors | Your endpoint is too slow — respond within 5 seconds | | Signature verification failing | Make sure you're using the raw request body (not parsed JSON) and the correct secret | | Duplicate deliveries | Use the X-Ruut-Delivery header to deduplicate — the same ID won't be sent twice | | Webhook shows as disabled | Your endpoint returned errors repeatedly — check your logs and re-enable it | :::callout{type="info" title="Need help?"} If you're stuck, reach out to our support team from the dashboard or email us at [email protected]. :::

How to Connect Ruut Chat with LinkedIn

What it is Connecting LinkedIn brings your LinkedIn conversations into your Ruut Chat workspace, so your team can read and reply to LinkedIn messages from the same inbox as every other channel. The connection runs through Ruut Connect, a small browser extension that links your LinkedIn account to your workspace with your permission. You set it up once, and messages and replies then work automatically. Why it matters A lot of business conversations start on LinkedIn: prospects, partners, recruits. Without a connection, those messages live in one person's LinkedIn account, where they get missed, can't be shared with teammates, and leave no record in your workspace. Once connected, LinkedIn messages land in your Ruut inbox next to your other channels, so anyone on your team can pick them up, assign them, and reply. Before you start Have ready: - A computer with Chrome. Ruut Connect is a desktop browser extension, so it can't be set up from a phone. - Admin access to your Ruut Chat workspace, so you can add an inbox - Your LinkedIn login, for the exact account you want to connect - A folder you can keep for the extension files. The extension needs this folder to stay where you put it. How to set it up: step by step Step 1: Open Workspaces and click "Add Inbox" In Ruut Chat, open Settings → Workspaces. You'll see every channel already connected to your account. Click Add Inbox in the top right. Step 2: Choose LinkedIn The setup wizard has four stages: Choose Channel → Create Workspace → Add Agents → Voilà. On the first stage, select LinkedIn ("Connect your LinkedIn conversations"). Step 3: Download the Ruut Connect extension On the Connect LinkedIn screen, the Ruut Connect extension card shows Setup required. Click Download extension. A file named ruut-connect.tar.gz downloads to your computer. Step 4: Extract the downloaded file Extract ruut-connect.tar.gz into a folder you'll keep, for example a "ruut-connect" folder in Downloads or Documents. When it's done, the folder should contain a file called manifest.json. Don't delete or move this folder afterwards, because your browser reads the extension from it every time. Step 5: Open your browser's Extensions page In a new tab, paste chrome://extensions into the address bar and press Enter. (In Brave or Edge, the same page is reachable from the browser's extensions menu.) Step 6: Turn on Developer mode Switch on Developer mode in the top right. Three new buttons appear: Load unpacked, Pack extension, and Update. Step 7: Load the extension Click Load unpacked. A file window opens asking you to select the extension directory. Choose the extracted ruut-connect folder (the one containing manifest.json) and click Select. Ruut Connect now appears in your list of extensions, described as "Connect your LinkedIn and X accounts to a workspace in Ruut with your permission." Step 8: Return to Ruut and check for the extension Go back to the Connect LinkedIn screen in Ruut and click Check for extension. The card's status changes from Setup required to Installed. Step 9: Name your workspace In the Workspace Name field, enter a name that makes this inbox easy to recognize later, such as "Sales LinkedIn" or the name of the person whose account is connected. Step 10: Continue with Ruut Connect Click Continue with Ruut Connect. A new Ruut Connect page opens with three stages: Account access → Verify → Confirm in Ruut. You choose which LinkedIn account to connect, and you can disconnect at any time. Step 11: Sign in to LinkedIn and allow permission Click Open LinkedIn to sign in, then sign in to the LinkedIn account you want to connect. Your browser will ask whether to let Ruut Connect **read and change your data on **www.linkedin.com. This permission is what lets the extension pass your messages into Ruut. Click Allow. Step 12: Verify and confirm in Ruut Follow the on-screen prompts through Verify and Confirm in Ruut, reviewing the LinkedIn profile Ruut shows you to be sure it's the right account. Step 13: Your inbox is ready When the connection completes, Ruut shows "Your Inbox is ready!" with two options: More settings (to adjust the inbox) or Take me there (to open it and start working). Final checklist - You're on a computer using Chrome. - The Ruut Connect extension shows in your Extensions list and is switched on - The extracted folder is saved somewhere permanent and hasn't been moved or deleted - The Connect LinkedIn screen shows Installed - You signed in to the correct LinkedIn account - You allowed the permission prompt - "Your Inbox is ready!" appeared, and the new inbox is listed under Settings → Workspaces Common problems The Continue with Ruut Connect button is greyed out — Ruut hasn't detected the extension yet. Click Check for extension. If it still isn't detected, confirm the extension is listed and switched on in your browser's Extensions page. Load unpacked doesn't appear — Developer mode is off. Switch it on in the top right of the Extensions page. The browser rejects the folder — You've likely selected the wrong level. Choose the folder that directly contains manifest.json, not a parent folder or the downloaded .tar.gz file. The connection stops working later — The extension loads from the folder you selected, so moving or deleting that folder breaks it. Put the folder back, or load the extension again from its new location. You connected the wrong LinkedIn account — Disconnect it from the inbox settings and repeat the process while signed in to the right account. You can disconnect at any time. You clicked Deny on the permission prompt — The connection can't complete without it. Restart from Continue with Ruut Connect and choose Allow when asked. What's next Once LinkedIn is connected, add your teammates as agents so they can reply from the new inbox, and set up labels or automation to route LinkedIn conversations to the right people.