> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/integrations.md).

# Integrations

- [Overview](https://docs.kick.co/integrations/integrations.md): Connect your banks, payment tools, and financial apps to bring all your transactions into Kick automatically.
- [Google Sheets](https://docs.kick.co/integrations/google-sheets.md): Import your Kick financial reports directly into Google Sheets - no downloading, no copy-paste.
- [Use with AI](https://docs.kick.co/integrations/google-sheets/google-sheets-use-with-ai.md): Use Gemini, Claude, or ChatGPT on live Kick report data in Google Sheets. Summarize trends, build forecasts, and extend your own dashboards with AI.
- [Ramp](https://docs.kick.co/integrations/ramp.md): Sync your Ramp credit card transactions, reimbursements, and bills directly into Kick.
- [Mercury](https://docs.kick.co/integrations/mercury.md): Connect Mercury to sync your transactions and bank statements directly into Kick.
- [Gusto](https://docs.kick.co/integrations/gusto.md): Connect Gusto to sync your payroll runs into Kick automatically, broken out by expense type.
- [Stripe & PayPal](https://docs.kick.co/integrations/payment-processors.md): Connect Stripe or PayPal to sync your payments, fees, and payouts into Kick automatically.
- [BILL](https://docs.kick.co/integrations/bill.com.md): Sync your BILL bills, invoices, vendors, and payments directly into Kick.
- [Manage Integrations](https://docs.kick.co/integrations/manage-integrations.md): Fix disconnected accounts, reassign accounts to entities, and manage your integration settings.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/integrations.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.