> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getquikly.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Integrations overview

> Connect Quikly with your tools through the REST API, webhooks, MCP server, n8n workflows, Telegram bot, web widget, and Discovery Copilot.

Quikly offers multiple ways to integrate with your existing stack. Whether you want to automate proposal creation from incoming leads, receive real-time notifications when a client responds, run a **live meeting copilot** ([Discovery Copilot](/guides/discovery-copilot-extension)), or let an AI assistant build proposals on your behalf, there's an integration path for you.

## Available integrations

<CardGroup cols={2}>
  <Card title="REST API" icon="code" href="/integrations/api-keys">
    Programmatic access to proposals, AI analysis, rate recommendations, and more. Authenticate with an API key and call endpoints from any language or platform.
  </Card>

  <Card title="Webhooks" icon="webhook" href="/integrations/webhooks">
    Receive HTTP POST notifications when proposals are created, shared, accepted, rejected, or when new leads arrive. Verify payloads with HMAC-SHA256 signatures.
  </Card>

  <Card title="MCP server" icon="robot" href="/mcp/overview">
    Use `quikly-mcp-server` with Cursor, Claude Desktop, or Claude Code to create and manage proposals directly from your AI coding assistant.
  </Card>

  <Card title="n8n workflows" icon="arrows-spin" href="/integrations/n8n">
    Automate your pre-sales pipeline with ready-made n8n workflow templates. Turn Telegram messages or form submissions into proposals without writing code.
  </Card>

  <Card title="Telegram bot" icon="paper-plane" href="/integrations/telegram-bot">
    Receive leads and manage proposal creation directly from Telegram. Connect your BotFather bot to Quikly and get notified when clients respond.
  </Card>

  <Card title="Web widget" icon="message-bot" href="/integrations/web-widget">
    Embed an AI-powered pre-sales agent on your website. It qualifies technical leads, runs discovery, and generates proposal drafts — 24/7.
  </Card>

  <Card title="Discovery Copilot" icon="monitor" href="/guides/discovery-copilot-extension">
    **Quikly Copilot** browser extension: live transcript and discovery coaching in Google Meet, Zoom Web, and Microsoft Teams Web. Uses your Quikly **API key** — create one under [API keys](/integrations/api-keys).
  </Card>
</CardGroup>

## Quick comparison

| Integration       | Auth method                         | Best for                                            |
| ----------------- | ----------------------------------- | --------------------------------------------------- |
| REST API          | API key (`X-API-Key` header)        | Custom integrations, scripts, CI/CD pipelines       |
| Webhooks          | HMAC-SHA256 signature verification  | Real-time event notifications to your server or CRM |
| MCP server        | API key via environment variable    | AI-assisted proposal creation from Cursor or Claude |
| n8n               | API key in HTTP Request node        | No-code automation workflows                        |
| Telegram bot      | Webhook URL from BotFather          | Lead intake and notifications on mobile             |
| Web widget        | Public key + domain allowlist       | Capturing leads from your website                   |
| Discovery Copilot | API key (same as REST — Quikly app) | Live meeting assistant in Meet, Zoom Web, Teams Web |

## Rate limits by plan

| Plan         | Monthly API calls | Rate limit |
| ------------ | ----------------- | ---------- |
| Starter      | 15                | 10/min     |
| Professional | 2,000             | 30/min     |
| Agency       | 2,000             | 60/min     |
| Lifetime     | 5,000             | 60/min     |

Check your current usage at any time with `GET /api/external/v1/usage`.

<Note>
  Self-serve API keys are meant for **your own integrations** (scripts, internal tools, workflows you build for yourself or your own clients as part of your service). If you're building a product that resells or proxies Quikly to third-party end-users, see [Self-serve vs Partner tier](/integrations/pricing-and-tiers).
</Note>

## Base URL

All API endpoints use the following base URL:

```
https://api.getquikly.com/api/external/v1
```

<Note>
  The REST API uses a separate authentication path from the web app. You need an **API key**, not your login credentials. See [API keys](/integrations/api-keys) to get started.
</Note>