In Review
36Under consideration
Website Chatbot Integration
Users want to introduce their AI chatbot to their customers. Supporting website integration would be beneficial for them to utilize AI better.
Negative Prompts
A set of instructions to tell the model what not to do. This could refine the chatbot responses.
Usage Dashboard
We are planning to introduce a Usage Dashboard to provide detailed insights into how Runbear is being used within your organization. This dashboard will show which app is used most within each channel, LLM token usage, and other important metrics.
Appfolio MCP Support
Appfolio is a powerful platform for your entire portfolio. AppFolio streamlines and automates real estate management, delivering insights and follow-through smithery.ai Has Appfolio MCP server - Appfolio Property Manager Reporting API Integration | Smithery It would be really appreciated if you would implement it in Runbear Thanks
Zendesk Chatbot Integration
Currently, Runbear Zendesk integration supports executing AI on every new inquiry. However, more customization options are needed to utilize AI better. For example, agents want to trigger AI manually by mentioning a chatbot. Requirements Support invoking AI by mentioning it. Support invoking AI that understands conversations on each ticket. Optional Support using Runbear on the sidebar instead of inside the chat panel.
Enable Runbear to link back to Slack threads
We use Runbear to create tickets in our task management software, and it would be ideal if we could have Runbear include links in the ticket back to the thread in Slack where the ticket was generated, as there is often useful context for the ticket in the preceding Slack conversation.
Improvements Slack <-> Linear integration
Would love to be able to manage tickets in Linear more effectively, for example being able to: • Get team members • Get users • Update issues: ◦ Mark issue as blocked by ◦ Mark issue as blocking ◦ Mark issue as related to ◦ Mark issue as sub-issue ◦ Mark issue as parent • Create project • Add issue to project
More then One google drive with access to Folders
I really need to have a way to allow multiple users to each set up their own Google Drive folder for sync. It would be a game changer for my use case
Issuebadge Integration
https://issuebadge.com - Bulk Certificate Generator API , Please integrate issuebadge
Private access to specific Slack users
Create the ability to grant private access to specific users for a publicly available assistant. This way only specific users can privately access an agent without having to be invited to a shared channel or DM.
In Progress
1Actively being built
Completed
22Recently shipped
Asana integration
Ability for bot to review Asana tasks and boards to provide updates on past due, comments when mentioned, etc.
Spreadsheet File Reading Capability
Many customers have requested the ability to read spreadsheet files such as CSV and XLS. This feature will enable you to upload spreadsheet-based files and have the bot answer questions based on the data within them. It can be used as a knowledge source for the bot, as well as for ad-hoc file uploads and chats on Slack.
To be able to pass Authorization headers to custom SSE MCP
Currently custom MCP servers only can be set with the /sse url, but for security purposes it would be always convenient to be able to add Authorization headers to protect the requests. Basically allow the equivalent of: curl -v -H "Authorization: Bearer token123" http://mcpserver.com/sse
Gemini Support
Currently, PlugBear supports OpenAI Assistants and Anthropic Claude as part of our proprietary LLM offerings. We are actively considering adding support for Gemini to expand our range of supported models.
SharePoint Knowledge Source
Many Microsoft Teams users seek to utilize files and folders stored in SharePoint as knowledge sources.
Website as a Knowledge base
Many customers have asked for the ability to use their public-facing documentation and FAQ pages as knowledge sources for their AI agents. In response to this demand, we are working on a feature that allows you to sync a website—including its subpages—so that your AI Agent can access and utilize the content as part of its knowledge base. This will make it easier for teams to keep their agents up to date with the latest product information, policies, and support content without needing to duplicate efforts in multiple systems.
Share entire Google Drive folder with Assistants > Automatically adds files to assistant's knowledge base
Enable the ability to share an entire folder with an assistant. 1. Folder is shared via google drive etc… 2. User selects folder within Runbear Drive integration UI > Folder and all content of folder is then automatically shared with Assistant (including any new files added in future) This enables easier maintenance of the knowledge base by businesses, as once a folder is designated, team members with appropriate permissions can then add new files to these folders that the assistant can access without having to request Runbear Admin to add new files to every assistant. Example: Business defines a google drive folder for ‘Standard Operating Procedures’ for the Training / SOP AI assistant. Any new SOPs that are created and added to the folder are automatically added to the Assistant’s knowledge ensuring the assistant is always up to date on the latest SOPs and reducing the Admin required to manage assistant’s knowledge base.
Notion Data Source Sync
Currently, PlugBear supports syncing documents in Google Drive and Confluence, keeping OpenAI Assistants up-to-date. Many of our customers have requested adding Notion as a data source, as it is one of the most popular knowledge bases today. We are looking into integrating Notion to ensure your OpenAI Assistants can access and stay updated with your Notion documents. Your feedback and suggestions are welcome as we work on this feature!
Add fetch Gitlab code tool to Gitlab connector.
Hi there Patrick Codrington says:Request to Runbear Support: GitLab Repository Files API Integration Issue: Ask_Sam is currently unable to retrieve file contents from GitLab repositories due to SAML SSO authentication blocking direct URL fetches. This prevents the agent from accessing authoritative production code, which is critical for accurate analytics responses. Current Limitation: • Direct URL fetches to https://gitlab.com/minted/analytics/* return SAML authentication pages • Example blocked URL: https://gitlab.com/minted/analytics/managed-airflow/-/raw/main/dags/bi/snowflake/workflows/update_orders_pipeline_daily/AN__bi_order_po/build.sql Required GitLab API Methods: Based on GitLab's Repository Files API documentation, we need the following endpoints: 1. Get File from Repository (Primary Need) • Endpoint: GET /projects/:id/repository/files/:file_path • Purpose: Retrieve file metadata and Base64-encoded content • Example: GET https://gitlab.com/api/v4/projects/47981211/repository/files/dags%2Fbi%2Fsnowflake%2Fworkflows%2Fupdate_orders_pipeline_daily%2FAN__bi_order_po%2Fbuild.sql?ref=main • Authentication: Requires PRIVATE-TOKEN header 2. Get Raw File from Repository (Alternative - Preferred) • Endpoint: GET /projects/:id/repository/files/:file_path/raw • Purpose: Retrieve raw file contents directly (not Base64-encoded) • Example: GET https://gitlab.com/api/v4/projects/47981211/repository/files/dags%2Fbi%2Fsnowflake%2Fworkflows%2Fupdate_orders_pipeline_daily%2FAN__bi_order_po%2Fbuild.sql/raw?ref=main • Authentication: Requires PRIVATE-TOKEN header Parameters Needed: • project_id (e.g., 47981211 for managed-airflow) • file_path (URL-encoded file path) • ref (branch name, default: main) Authentication Requirements: • GitLab Personal Access Token or Project Access Token • Token scopes needed: api or read_api • Token should be configured at the assistant/workspace level for persistent access Use Case: Analytics team members frequently request code lineage, table definitions, and ETL logic. Currently, Ask_Sam must rely on potentially outdated Confluence/Slack references. With GitLab API access, Ask_Sam can provide authoritative, production-accurate code directly from the source repository. Expected Behavior After Implementation: When a user provides a GitLab file URL or requests code from a specific file, Ask_Sam should: 1. Extract the project ID and file path 2. Call the GitLab API endpoint with proper authentication 3. Return the actual file contents to the user Priority: High - This is blocking accurate responses for code-related analytics questions, which are a primary use case for Ask_Sam.
Ability to Search Google Drive Files, Navigate and See folder names / path, Filter
Advanced users of assistants end up having a significant number of files and folders shared with their AI assistants. This becomes unwieldy to manage / maintain as assistants and usage matures. Providing the ability to navigate, search/filter, and see folder names / created / updates and file paths for shared files and folders within the google drive integration enables the ability to scale and manage the assistant’s knowledge base. Note that for AI advisory businesses managing client’s AI’s for them would also include the ability to see the Company/Folder path and filter to ensure they can easily manage multiple clients safely without accidentally sharing incorrect files or folders to other clients’ Assistants.