--- title: "Workleap Officevibe Integration for Rig: Query Workleap Officevibe Data in Plain English" description: "Connect Workleap Officevibe to Rig and query your Workleap Officevibe data in plain English, or ask it in Claude, ChatGPT and Cursor. Governed, validated answers from your warehouse." canonical: "https://rig.so/integrations/workleap-officevibe" format: markdown --- Browse integrations ![Workleap Officevibe logo](https://img.logo.dev/workleap.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=112&format=png&retina=true) People & operations Supported # Workleap Officevibe integration for Rig ## The easiest way to connect Workleap Officevibe to Claude and other AI tools Workleap Officevibe is an employee engagement tool that collects weekly survey answers, feedback conversations and peer recognition. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) ## What Rig syncs from Workleap Officevibe Once connected, Rig models these objects so questions resolve to the right tables and joins: - Weekly engagement scores - Scores per team - Engagement metrics - Feedback conversations - Feedback labels - Good Vibes - Users - Groups ## How Workleap Officevibe connects to Rig Rig Ingest syncs Officevibe into your warehouse on a schedule with an organisation API key. Free-text feedback, recognition messages, authors and phone numbers are off by default. [Read the step-by-step Workleap Officevibe setup guide](https://rig.so/guides/connect-workleap-officevibe) ## Track engagement over time An engagement score is the weekly measure Officevibe computes from survey answers. Rig stores one row per week for the organisation and per team, so trends are queries over history. Ask Rig - How has the engagement score moved over the last 12 months? - Which teams have the lowest participation rate? - What was our NPS each month this year? ## Compare teams on each engagement metric Engagement metrics are the themes Officevibe scores, such as recognition or manager relationship. Rig syncs the metric names beside per-team scores, so teams can be compared on the same metric. Ask Rig - Which team scores lowest on each metric? - Which metrics fell the most last quarter? - How does one team compare with the organisation? ## Read feedback volume and recognition Feedback conversations are tagged by metric, type and label, and Good Vibes are peer recognition cards. Rig syncs both, so volume and themes can be tracked without opening Officevibe. Ask Rig - How many feedback conversations are there per metric? - Which feedback labels are used most? - How many Good Vibes were sent each month? ## Join engagement to the people directory Users and groups come across with the engagement data. Joined to HR and finance tables in the warehouse, scores can be grouped by the same team structure the business already uses. Ask Rig - Which groups have grown while their scores fell? - How does engagement differ by department? - Which groups have the most users? ## Ask your Workleap Officevibe data in Claude, ChatGPT or Cursor Rig serves your Workleap Officevibe data to AI assistants over MCP. Once Workleap Officevibe is synced into your warehouse, you can ask questions in plain English from the tool you already use, and every answer is backed by validated, governed SQL. - [Claude](https://rig.so/integrations/claude) - [Claude Code](https://rig.so/integrations/claude-code) - [Cursor](https://rig.so/integrations/cursor) - [ChatGPT](https://rig.so/integrations/chatgpt) - [Codex](https://rig.so/integrations/codex) - [Gemini](https://rig.so/integrations/gemini) ## Frequently asked questions What does Rig sync from Officevibe? Users, groups, the metric taxonomy, weekly engagement scores for the organisation and per group, feedback conversations, feedback labels, Good Vibes and Good Vibes collections. Is feedback text included? Free-text feedback, recognition messages, feedback authors and phone numbers are off by default, and you can switch each on per field. Does an older Officevibe key work? No. Rig uses the current Workleap API, and a key from the older Officevibe API fails with a 401. How far back does history go? The first sync reads from the start date you set, which is pre-filled as 2016-01-01. Recent weeks are re-read on each sync because late answers move them. ## Related integrations [![CharlieHR logo](https://img.logo.dev/charliehr.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)CharlieHRPeople, teams and leave from CharlieHR, with salary data never synced.](https://rig.so/integrations/charliehr)[![Google Workspace Directory logo](https://img.logo.dev/workspace.google.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)Google Workspace DirectoryAccounts, managers, departments and org units from Google Workspace.](https://rig.so/integrations/google-workspace-directory)[![Greenhouse logo](https://img.logo.dev/greenhouse.io?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)GreenhouseCandidates, applications, interviews and offers from Greenhouse Harvest.](https://rig.so/integrations/greenhouse)[![Make logo](https://img.logo.dev/make.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)MakeSee which Make scenarios touch a field, and how they run.](https://rig.so/integrations/make)[![Rippling logo](https://img.logo.dev/rippling.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)RipplingWorkers, org structure, leave, time and recruiting data from Rippling.](https://rig.so/integrations/rippling)[![SCORM Cloud logo](https://img.logo.dev/scorm.com?token=pk_AdkTbLWDS1iunmvTK2qm1g&size=72&format=png&retina=true)SCORM CloudCourses and learner registrations from SCORM Cloud.](https://rig.so/integrations/scorm-cloud) ## Connect Workleap Officevibe data to AI tools like Claude Rig builds a governed context layer over your data so every team, and every AI tool, asks questions and gets answers they can trust. [Try Rig](https://app.rig.so/signup)[Book a demo](https://rig.so/book-demo) --- - [This page as HTML](https://rig.so/integrations/workleap-officevibe) - [Site map for language models](https://rig.so/llms.txt) - [API and agent documentation](https://rig.so/developers)