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

# Integrations

Connect Mechanic to third-party services like Google Sheets, Airtable, Slack, and more.

Mechanic maintains several official integration points:

* [Airtable](/platform/integrations/airtable.md)
* [Appstle Subscriptions](/platform/integrations/appstle-subscriptions.md)
* [Google](/platform/integrations/google.md)
* [Google Drive and Sheets](/platform/integrations/google-drive-and-google-sheets.md)
* [Judge.me](/platform/integrations/judge.me.md)
* [Locksmith](/platform/integrations/locksmith.md)
* [Report Toaster](/platform/integrations/report-toaster.md)
* [Shopify Flow](/platform/integrations/shopify-flow.md)
* [Slack](/platform/integrations/slack.md)
* [Run links](/platform/integrations/run-links.md)

{% hint style="info" %}
**Need a service that's not on this list?**

Mechanic can connect to virtually any service that has an HTTP API or outbound webhooks. See [Connecting third-party apps](/platform/integrations/connecting-third-party-apps.md) for a complete guide to integrating external services.

The [Mechanic task library](https://tasks.mechanic.dev/) has a limited selection of tasks integrating with third-party services.

If you don't find a match in the task library, consider a custom task to achieve your integration. Start here: [I need something custom!](/custom.md)
{% endhint %}

### OAuth

Mechanic supports OAuth 2.0 for services like Airtable, Google Drive, and Slack — connect and authorize directly from the Mechanic app, no API keys needed.

Need a service not on the list? Put in a feature request [here](https://mechanic.canny.io/futures).


---

# 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://learn.mechanic.dev/platform/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.