airweaveContext retrieval layer for AI agents across users' applications. Search and retrieve context from Airweave collections. Airweave indexes and syncs data from user applications to enable optimal context retrieval by AI agents. Supports semantic, keyword, and agentic search. Use when users ask about their data in connected apps (Slack, GitHub, Notion, Jira, Confluence, Google Drive, Salesforce, Linear, SharePoint, Stripe, etc.), need to find documents or information from their workspace, want answers based on their company data, or need you to check app data for context to complete a task.
Install via ClawdBot CLI:
clawdbot install lennertjansen/airweaveRequires:
Grade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://api.airweave.aiAudited Apr 16, 2026 · audit v1.0
Generated Mar 21, 2026
A customer asks about a refund policy. The agent uses Airweave to search internal documents and past Slack conversations to provide an accurate, up-to-date answer based on company data, ensuring compliance and consistency.
A team member requests the latest updates on a product launch. The agent searches across Jira tickets, Notion pages, and recent Slack discussions to synthesize a comprehensive status report, highlighting key milestones and blockers.
A sales manager asks for recent customer feedback on pricing. The agent retrieves data from Salesforce records, Google Drive documents, and Stripe transaction notes to analyze trends and inform sales strategies.
An employee needs to find specific policy documents, such as onboarding procedures. The agent searches Confluence and SharePoint to locate and summarize relevant documents, ensuring quick access to critical information.
A developer reports a bug and asks for related issues. The agent searches GitHub repositories and Linear tickets to identify similar past incidents and provide context for faster debugging and resolution.
Offer Airweave as a cloud-based service with tiered pricing based on data volume, number of collections, and search frequency. Revenue comes from monthly or annual subscriptions, targeting small to large enterprises.
Provide on-premise or private cloud deployments with custom integrations and dedicated support. Revenue is generated through one-time license fees and ongoing maintenance contracts, ideal for organizations with strict data governance.
Charge based on the number of API calls, search queries, or data processed. This pay-as-you-go model attracts startups and developers, with revenue scaling directly with usage and offering flexibility for varying needs.
💬 Integration Tip
Ensure the AIRWEAVE_API_KEY and AIRWEAVE_COLLECTION_ID environment variables are securely configured before deployment, and test search scripts with varied queries to optimize retrieval accuracy.
Scored Apr 19, 2026
Google Workspace CLI for Gmail, Calendar, Drive, Contacts, Sheets, and Docs.
Registra contrato de locação via Google Forms.
Google Sheets integration. Manage analytics data, records, and workflows. Use when the user wants to interact with Google Sheets data.
Google Drive integration. Manage Drives, Users, Permissions. Use when the user wants to interact with Google Drive data.
Gmail, Calendar, Drive, Docs, Sheets — NO Google Cloud Console required. Just OAuth sign-in. Zero setup complexity vs traditional Google API integrations.
Google Slides API integration with managed OAuth. Create presentations, add slides, insert content, and manage slide formatting. Use this skill when users want to interact with Google Slides. For other third party apps, use the api-gateway skill (https://clawhub.ai/byungkyu/api-gateway). Calls run through the `maton` CLI with OAuth login, or over raw HTTP with a Maton API key where the CLI cannot be installed. Every call is authenticated as the user's connection and reaches only what that connection's authorization allows, which the provider enforces on every request; the endpoints documented here are the ones this skill uses, and any other endpoint of this app needs the user to ask for it by name. Default to read and list calls, and confirm every write or new connection with the user. This file also documents the three constructs that turn a Google Slides connection into automation, in the order they are used: the connection (the first step), a hosted function that runs a Google Slides action through the Maton SDK, and a trigger that calls that function on a schedule or on an event. Those sections are the platform's own reference text, shared with the api-gateway skill, with Google Slides examples; they add no Google Slides capability - Google Slides is not an event source, a trigger cannot read Google Slides data, and the files under `references/<source>/triggers.md` are the platform's event catalogues for the sources Maton offers (time, Calendly, GitHub, Gmail, HubSpot, Linear, Notion, Slack, Stripe).