Integrations Overview
Greppilot allows you to connect to various external services, enabling the AI agent to interact with your data and systems by exposing their functionalities as "tools."
How Integrations Work
Each integration handles key aspects of its operation:
- Tool Discovery: Providing the agent with the set of capabilities available for that integration.
- Tool Execution: Processing requests to use those capabilities with provided parameters.
- Configuration Validation: Verifying connection details (e.g., API keys, connection strings) upon installation.
For Custom MCP (Model Context Protocol) servers, Greppilot dynamically fetches tool definitions directly from your configured server, enabling you to inject custom tools into the agent.
Available Integrations
Greppilot supports a diverse set of integrations, categorized as follows:
- SaaS APIs (full provider): Stripe, Linear, PostHog, Langfuse — full tool manifests with query, list, and management capabilities.
- SaaS APIs (connect & configure): Sentry, Notion, GitHub, Slack, Google Sheets, HubSpot — connect your account and configure credentials. Tool support is expanding.
- Databases: PostgreSQL, MySQL, Microsoft SQL Server, ClickHouse.
- Data Files: CSV Files.
- Custom: MCP Servers.
Configuration
When installing an integration, you provide configuration details specific to that service. These details are securely stored and used for establishing connections and authenticating requests.
Common authentication types include:
- API Key: A secret key or token provided by the external service.
- OAuth: A standardized protocol for granting secure access without sharing direct credentials.
- Connection String: A URL-like string containing credentials and parameters for database connections.
- None: No explicit authentication required.
Configuration Parameters
The exact fields required depend on the integration type. Common configuration fields include:
| Key | Type | Description |
|---|---|---|
apiKey | string | API key or token for services like Stripe, Sentry, Linear, PostHog, Langfuse, GitHub, HubSpot. |
connectionString | string | Full connection string for database integrations (PostgreSQL, MySQL, MSSQL, ClickHouse). |
url | string | Base URL for custom MCP servers. |
serverName | string | User-friendly name for a custom MCP server. |
authHeader | string | Optional authorization header for custom MCP servers (e.g., Bearer token). |
accessToken | string | OAuth access token. |
organization | string | Organization identifier for services like Sentry. |
projectId | string | Project identifier for services like PostHog. |
host | string | Custom host for services like PostHog or Langfuse. |
secretKey | string | Secret key for services like Langfuse. |
publicKey | string | Public key for services like Langfuse. |
Only provide sensitive credentials in fields explicitly designated as password types by the integration's configuration.
Security
Greppilot encrypts all sensitive configuration data at rest using industry-standard encryption. This protects API keys, connection strings, and OAuth tokens.
For database connection strings, Greppilot implements additional validation to ensure connections are only made to legitimate database endpoints.