> 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/hire-a-developer.md). # Hire a Mechanic Partner Find a Shopify automation developer to build or customize Mechanic tasks — browse Mechanic Partners or bring your own developer. Mechanic's automation tasks are written in Liquid, which is a template language used heavily in and around Shopify. This means that developers of all levels, with even a little Shopify development experience, can get started with Mechanic. ## When to hire a developer Many merchants work with a developer to get exactly what they need. Here are some common scenarios: * **Custom workflow** — you need an automation that isn't available in the [task library](https://tasks.mechanic.dev/) * **Modifying a library task** — you've found a task that's close to what you need, but it requires changes beyond what its built-in options support * **Third-party integration** — you want to connect Mechanic to an external service like an ERP, a custom app, or an API that isn't covered by the library * **Ongoing maintenance** — you have a set of tasks that need regular updates as your business evolves ## Finding a developer **To find a developer for hire, visit** [**partners.mechanic.dev**](https://partners.mechanic.dev/)**.** This is a growing list of established developers, both independent and agency, who can help you with your implementation. If you're not sure where to start, try the [matchmaking service at partners.mechanic.dev/matchmaking](https://partners.mechanic.dev/matchmaking) — tell us what you need and we'll connect you with a developer who can help. This is a super common path, and the Mechanic community is here to help. :) If you already have a developer on your team, or have an existing connection to a developer, send them [this article](/custom.md) and see if they can help you! --- # 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/hire-a-developer.md?ask=&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.