Tag: Real-Time Search API

  • Slack dev tools pave the way for new AI agents

    Title: Revolutionizing Collaboration: Slack’s New AI Agents

    In a groundbreaking move, Slack has introduced a suite of developer tools that are set to transform the landscape of AI agents within the platform. These tools enable the creation and deployment of advanced agents that harness real-time conversation data, enhancing user interactions and boosting productivity. With features like the real-time search API and the model context protocol (MCP) server, third-party vendors and organizations can now effortlessly build custom AI agents tailored to their specific needs.

    The real-time search (RTS) API allows agents to access Slack channel data without the cumbersome process of downloading it in bulk, ensuring seamless integration while upholding stringent access permissions. For instance, applications like Notion and Dropbox Dash can now seamlessly retrieve information from Slack channels, empowering users with valuable insights within the familiar Slack environment.

    Moreover, the Slack MCP server, developed in collaboration with Anthropic, standardizes information access and task execution for agents, simplifying the development process and enhancing user experiences. By leveraging this framework, AI assistants like Perplexity can deliver more precise responses grounded in the context of ongoing Slack conversations, expanding the utility and reliability of such tools.

    Excitingly, these cutting-edge features are currently available in closed beta, with a slated general release in early 2026. Meanwhile, third-party agents can already be accessed through the Slack Marketplace, ushering in a new era of AI innovation within Slack. Pricing for these AI apps and agents will be determined by individual vendors, offering flexibility and scalability for businesses.

    Additionally, Slack’s announcement of Work Objects introduces a novel tool for developers to seamlessly integrate apps with Slack, enhancing data visualization and user engagement. By providing rich app previews and standardized data displays, Work Objects facilitate streamlined actions within Slack, promoting a seamless workflow and improved user experience.

    Furthermore, Slack has unveiled a range of agentic developer tools aimed at enhancing the development lifecycle with AI best practices and prebuilt resources. These tools, including the Block Kit Tables and CLI for Bolt interface, exemplify Slack’s commitment to empowering developers and driving innovation within the platform.

    Looking ahead, Slack’s Work Objects will soon be available to all developers in late October, while the new agentic developer tools are currently accessible. As the realm of AI agents continues to evolve, Slack’s pioneering efforts are set to redefine collaboration, productivity, and user experiences within the digital workspace.

  • Salesforce changes Slack API terms to block bulk data access for LLMs

    Salesforce Restricts Slack API Access for Large Language Models (LLMs)

    In a recent development, Salesforce’s Slack platform has implemented changes to its API terms of service, specifically targeting the usage of Large Language Models (LLMs) for data ingestion. This adjustment aims to enhance enterprise data discovery and search functionalities within the platform.

    The updated policy, detailed under the new section named “Data usage” in the latest terms of service released on May 29, prohibits the bulk export of Slack data through the API. It explicitly states that data obtained via Slack APIs can no longer be utilized for training LLMs. Instead, organizations are directed to leverage the Real-Time Search API provided by the company for search operations solely within Slack.

    The new terms also impose limitations on the distribution of applications developed using the API. Developers are required to either engage in a partner agreement with Slack or Salesforce or exclusively distribute their apps via the Slack Marketplace.

    These modifications could have significant implications on various fronts. Third-party developers of data discovery applications may lose access to a crucial data source, impacting tools like the Glean app, as reported by The Information. Moreover, organizations utilizing their own LLMs risk losing the capability to incorporate Slack data for broader internal discovery and search purposes.

    In a detailed blog post expounding on the rationale behind the change, Slack emphasized the shift as part of a broader initiative to redefine the intersection of AI and security. The company highlighted the Real-Time Search API as a secure means for approved partners and developers to retrieve necessary data from Slack in real-time, enabling safe AI-powered applications like federated search and deep research.

    An alternative perspective suggests that Salesforce aims to promote its proprietary or authorized AI tools available through the Slack Marketplace. Some industry observers speculate that this strategy could potentially lead to a broader crackdown intended to steer customers towards exclusive solutions.

    The evolving landscape of Software as a Service (SaaS) platforms, including Salesforce, Teams, Gmail, and others, presents a challenge of data fragmentation for organizations. Glean, founded by former Google employees, supports a multitude of these platforms, underscoring the complexity of data management. Enterprise search LLMs play a vital role in aggregating data from diverse platforms through public APIs, facilitating streamlined data querying across multiple SaaS interfaces.

    Notably, AI capabilities have become pivotal for platforms like Slack, prompting Salesforce to adjust its API access rules to safeguard this functionality. Salesforce reiterated that data security remains a primary focus of these changes, emphasizing real-time search access via the Real-Time Search API as a secure method that eliminates the need for extensive data exports while supporting key use cases like permission-based search.

    However, the restriction on integrating Slack data into external LLMs has sparked skepticism within the industry. Experts raise concerns about the potential impact on organizations striving to unify data sources and build advanced AI applications. The move has been perceived as a strategic maneuver by Salesforce to safeguard user data while potentially paving the way for monetization in the future.

    Industry voices, including Wyatt Mayham of Northwest AI Consulting and Bob Hutchins of Human Voice Media, caution about the broader implications of such platform restrictions. They highlight the risk of a fragmented AI app landscape, reduced choices for users, and slower decision-making processes if similar tactics are adopted by other vendors.

    In conclusion, the recent changes to Salesforce’s Slack API terms signify a pivotal shift in how organizations interact with AI tools and access data across platforms. While the emphasis on data security is paramount, the implications on innovation, user choice, and data accessibility warrant careful consideration in the evolving tech landscape.

  • Salesforce changes Slack API terms to block bulk data access for LLMs

    Salesforce’s Move to Restrict Slack API Access for LLMs

    Salesforce’s recent decision to update the API terms for its Slack platform has sent ripples through the tech community. The change specifically targets the use of Large Language Models (LLMs) for bulk data access, affecting how organizations interact with Slack’s data.

    This adjustment, while appearing technical on the surface, holds significant implications for the landscape of AI applications. Organizations relying on third-party AI tools to manage and analyze Slack data will now face limitations due to the prohibition on bulk data export via APIs for training LLMs.

    The shift towards utilizing Salesforce’s Real-Time Search API instead of traditional methods aims to enhance data security and streamline access within Slack itself. However, this move has sparked concerns among developers and AI enthusiasts who fear a potential restriction on innovation and data exploration.

    One key aspect of this change is the impact on data discovery and search capabilities within organizations. By limiting the ways in which data can be accessed and utilized, Salesforce risks hindering the development of comprehensive AI solutions that span across different platforms and services.

    The rationale behind this move, as explained by Slack, revolves around enhancing data security and promoting real-time search functionalities. While these objectives are commendable, the community remains divided on the long-term effects of such restrictions on the evolution of AI technologies and data-driven insights.

    The evolving landscape of SaaS platforms, including Salesforce, Teams, Gmail, and others, underscores the growing complexity of managing data across various services. The interplay between AI capabilities and data accessibility is crucial for organizations seeking to derive meaningful insights from their digital interactions.

    As industry experts and commentators weigh in on the implications of Salesforce’s decision, the broader conversation shifts towards the balance between data security, innovation, and user empowerment. The potential ramifications of restricting API access for LLMs extend beyond individual platforms, impacting the interconnected nature of modern data ecosystems.

    In conclusion, Salesforce’s updates to the Slack API terms reflect a broader trend in the tech industry towards tighter control over data access and usage. While the pursuit of enhanced security and proprietary solutions is understandable, it is essential to consider the wider implications for innovation, collaboration, and the future of AI-driven technologies in a data-centric world.