> 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/6.12/development/flow-studio/connectors/utility/custom-.net.md).

# Custom .NET

Flow has support for using third party .net assemblies. All public static methods with primitive types as arguments can be executed from a [machine step](https://home.novacuraflow.com/Help/latest/?designer_applications_workflow_machine_task) in any type of workflows.

Follow these steps to setup a custom connector:

1. Run **NovaCura.Flow\.Connector.Wrapper.exe** from your command line console.
   * It is located in Flow Designer program folder.
   * **First argument** is output connector dll name, example: CustomConnector.dll
   * **Second argument** is input assembly path.
   * If input assembly has dependencies to other assemblies those can be entered as arguments. For example: NovaCura.Flow\.Connector.Wrapper.exe CustomConnector.dll CustomAssembly.dll CustomUtil.dll
2. Copy output dll to the current studio version (*%appdata%\\{{version}}) and to* bin/CustomConnectors\* folder located in Server installation folder.
3. Add a *connector* element to CustomConnectors.xml located in *bin/CustomConnectors* folder in Server installation folder.

   ```
   <!-- Change 'species' to a unique technical name --> 
    <!-- Change 'displayName' to a suitable display name --> 
    <!-- Change 'assemblyname' to the name of the output dll exluding .dll, in the example below the file is named CustomConnector.dll --> 
   <connector 
    species="custom_connector_name"
    displayName="DotNet API Custom Connector" 
    assemblyname="CustomConnector"
    type="NovaCura.Flow.Connector.Wrapper.ConnectorWrapper" 
    uitype="NovaCura.Flow.ApiConnector.UI.ApiConnectorUI" 
    uiassemblyname="NovaCura.Flow.ApiConnector.UI" /> 
   ```
4. Start Flow Designer and verify that a new connector type with the previous specified display name exists in Connectors page under Environments when adding a new connector.
5. Add the new connector and enter a suitable name.
6. The new connector should now exist in all [machine step](https://home.novacuraflow.com/Help/latest/?designer_applications_workflow_machine_task) configurations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://help.novacuraflow.com/6.12/development/flow-studio/connectors/utility/custom-.net.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.