> For the complete documentation index, see [llms.txt](https://help.orderdesk.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.orderdesk.com/integration-setup-guides/tools-and-productivity/make-integration.md).

# Make Integration

Order Desk can send your order details to [Make](http://www.make.com) allowing you to create powerful automated workflows across your fulfillment network.

### Setup

To enable the integration, click on **Manage Integrations** in the left sidebar. Under the **Productivity** tab, find and enable the Make integration.

![](https://251457507-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FAQOLMUJWMYtrpQ7Oxxca%2Fuploads%2FpSXezNcsXNOWUR6aBH6V%2Flegacy-6e9f3d891aed89a55482.gif?alt=media)

With this integration, you can take two separate actions: send order details to Make when an order is imported into Order Desk, or when an order moves between folders. Each of those actions would require its own separate webhooks in Make.If you’re unsure of how to create a webhook in Make, you can reference their guide at [this link](https://help.make.com/webhooks).

### Using Make with Order Desk

With Make connected to Order Desk, you’ll be able to send your order details to any of Make’s internal tools and thousands of connected apps by using the Order Desk Rule Builder.If you’re unfamiliar with how to use the Rule Builder, [here’s](/start-here/getting-started-series/quick-start-how-customizable-is-order-desk-really.md) an introduction.


---

# 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://help.orderdesk.com/integration-setup-guides/tools-and-productivity/make-integration.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.