> For the complete documentation index, see [llms.txt](https://help.novacuraflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.novacuraflow.com/development/integration-engine/get-started/create-an-integration.md).

# Create an integration

Go to the Flow Integrations page (by clicking Flow Integrations in the menu bar to the left).

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FS4zCYTKSE5k3fyblh92G%2Fimage.png?alt=media&amp;token=8f788086-2de8-4dfb-853c-a1bde43ba6db" alt=""><figcaption></figcaption></figure>

Click `+ Add` which brings you to the page for adding a Flow 6 Server integration.

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FvXVG5JHmBzKnW2WUgkLN%2Fimage.png?alt=media&amp;token=12ba9f5b-ff98-44e6-b9a4-3bce9cd99699" alt=""><figcaption></figcaption></figure>

Flow Server: in the drop down, select the Flow Server you have added a connection to.

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FeZAzNaYlGgA3UoPCBozM%2Fimage.png?alt=media&amp;token=23141007-f09c-4a06-838c-fe483cae92c8" alt=""><figcaption></figcaption></figure>

Under the Flow Server drop down, a list with all the machine workflows published on that specific Flow 6 Server appears.

Navigate in the folder structure to the machine workflow you want to create an integration for and select it.&#x20;

Fill in the following details of your integration:

**Name** (mandatory): a brief alpha-numerical name

**Description** (optional): A brief description of the integration

**Enabled** (On/Off): toggles whether the integration is active for execution or not.&#x20;

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FCRT6csNGTF4vg6rmHi6y%2Fimage.png?alt=media&amp;token=cee6efcf-be86-460a-a21d-c78a172634c8" alt=""><figcaption></figcaption></figure>

Now click the tab Trigger Type.

<figure><img src="https://529897662-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LtPTgZOYmpJka4jqs1v-3406065915%2Fuploads%2FQuWxOf3aCSBZO9xQSiSV%2Fimage.png?alt=media&amp;token=fa6b6673-7f4b-462b-a646-edf068e6bba4" alt=""><figcaption></figcaption></figure>

Click the drop down SelectTriggerType and select one of

* Schedule - Scheduled trigger
* Webhook - Webhook (http post/get) trigger

When you have are ready configuring the Trigger Type, click Save to create the integration and continue this Get Started guide.


---

# 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.novacuraflow.com/development/integration-engine/get-started/create-an-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.
