Integray.Connector.CLI
1.0.26
See the version list below for details.
dotnet tool install --global Integray.Connector.CLI --version 1.0.26
dotnet new tool-manifest
dotnet tool install --local Integray.Connector.CLI --version 1.0.26
#tool dotnet:?package=Integray.Connector.CLI&version=1.0.26
nuke :add-package Integray.Connector.CLI --version 1.0.26
Integray Connector CLI
Create, package, and publish connectors with the Integray Connector CLI — a small command-line tool designed for the Integray integration platform (see Integray). The tool quickly generates a connector project from a template, builds it into a ZIP package, and can publish it to the Integray repository.
Install / Upgrade / Uninstall
Install globally:
dotnet tool install -g Integray.Connector.CLI
Upgrade to latest:
dotnet tool update -g Integray.Connector.CLI
Uninstall:
dotnet tool uninstall -g Integray.Connector.CLI
Requirements: .NET SDK 6.0 must be installed and available on your PATH. Network access is required only for publishing the connector.
Getting started
After installing the tool, the global command integray will be available.
Command structure: integray connector <command> [options]
Commands overview
integray connector new— scaffold a new connector project + tests from a template.integray connector pack— build and package an existing connector project into a distributable ZIP.integray connector publish— publish a packaged connector ZIP to the Integray repository.
Example workflow
A short example showing the typical steps to create, package and publish a connector for Integray.
- Create a new connector from a template:
integray connector new --template Calculator --name MyCalculator ./MyCalculator
- Build and package the connector:
integray connector pack -p ./MyCalculator/Integray.Connector.MyCalculator.csproj -o ./dist/MyCalculator.zip
- Publish the packaged ZIP to the Integray repository:
integray connector publish --source ./dist/MyCalculator.zip --channel <CHANNEL_ID> --token <TOKEN>
integray connector new
Scaffold a new connector project (connector itself + tests) from a selected template.
Usage:
integray connector new --template <Template> --name <Name> <OutputDirectory>
Or with short flags:
integray connector new -t <Template> -n <Name> <OutputDirectory>
Options:
--template,-tRequired. Template name (e.g.Calculator). See Available templates below.--name,-nRequired. Connector name without spaces (e.g.MyCalculatorConnector).<OutputDirectory>Required. Destination folder for generated projects.
Example:
integray connector new --template Calculator --name MyCalculator ./MyCalculator
Example (short flags):
integray connector new -t Calculator -n MyCalculator ./MyCalculator
Available templates
- Calculator — Demonstrates the use of input and output data, configurations and logging.
- Empty — Minimal connector template without any data or configurations.
- GitHub — Demonstrates how to call a public REST API, retrieve and parse output data.
integray connector pack
Build and package an existing connector project into a distributable ZIP.
Usage:
integray connector pack --project <PathToCsproj> --output <ZipPath>
Or with short flags:
integray connector pack -p <PathToCsproj> -o <ZipPath>
Options:
--project,-pRequired. Path to the connector.csproj.--output,-oRequired. Path to the resulting zip archive.
What it does:
- Runs
dotnet buildfornet6.0in Release configuration. - Zips build output as
plugin.zipand embeds it into the final archive. - Includes files from the project's
Metadata/directory at the root of the final archive.
Example:
integray connector pack --project ./MyCalculator/Integray.Connector.MyCalculator.csproj --output ./dist/MyCalculator.zip
Example (short flags):
integray connector pack -p ./MyCalculator/Integray.Connector.MyCalculator.csproj -o ./dist/MyCalculator.zip
integray connector publish
Publish a packaged connector ZIP to the Integray repository. Publishing requires a publisher account that allows you to create and manage channels, upload packages and control releases — to request access, contact support@integray.com.
Usage:
integray connector publish <package> --channel <ChannelId> --token <Token>
Or with short flags:
integray connector publish <package> -c <ChannelId> -t <Token>
Positional arguments:
package(pos. 0) Required. Path to the ZIP package produced byintegray connector pack(e.g../dist/MyCalculator.zip).
Options:
--channel,-cRequired. Identifier of the channel to publish to.--token,-tRequired. Bearer token used for authentication.
Example:
integray connector publish ./NewConnector.zip -c b5f1a1a6-0e6d-4b49-a7e4-746cfe7f6f7b -t 2d8c73df-f6d5-4d0d-936a-9c54b91a4d13
Short form example:
integray connector publish ./NewConnector.zip -c b5f1a1a6-0e6d-4b49-a7e4-746cfe7f6f7b -t 2d8c73df-f6d5-4d0d-936a-9c54b91a4d13
If you need a publishing channel or a publisher account to manage your channels, please contact support@integray.com. A publisher account is required to create channels and publish packages.
| Product | Versions Compatible and additional computed target framework versions. |
|---|---|
| .NET | net6.0 is compatible. net6.0-android was computed. net6.0-ios was computed. net6.0-maccatalyst was computed. net6.0-macos was computed. net6.0-tvos was computed. net6.0-windows was computed. net7.0 was computed. net7.0-android was computed. net7.0-ios was computed. net7.0-maccatalyst was computed. net7.0-macos was computed. net7.0-tvos was computed. net7.0-windows was computed. net8.0 was computed. net8.0-android was computed. net8.0-browser was computed. net8.0-ios was computed. net8.0-maccatalyst was computed. net8.0-macos was computed. net8.0-tvos was computed. net8.0-windows was computed. net9.0 was computed. net9.0-android was computed. net9.0-browser was computed. net9.0-ios was computed. net9.0-maccatalyst was computed. net9.0-macos was computed. net9.0-tvos was computed. net9.0-windows was computed. net10.0 was computed. net10.0-android was computed. net10.0-browser was computed. net10.0-ios was computed. net10.0-maccatalyst was computed. net10.0-macos was computed. net10.0-tvos was computed. net10.0-windows was computed. |
This package has no dependencies.
| Version | Downloads | Last Updated |
|---|---|---|
| 2.0.3 | 125 | 3/12/2026 |
| 1.0.34 | 111 | 1/14/2026 |
| 1.0.33 | 95 | 1/14/2026 |
| 1.0.32 | 97 | 1/14/2026 |
| 1.0.31 | 103 | 1/14/2026 |
| 1.0.30 | 231 | 12/19/2025 |
| 1.0.29 | 222 | 12/19/2025 |
| 1.0.28 | 288 | 12/17/2025 |
| 1.0.27 | 180 | 12/5/2025 |
| 1.0.26 | 364 | 11/21/2025 |
| 1.0.25 | 398 | 11/20/2025 |
| 1.0.24 | 405 | 11/20/2025 |
| 1.0.23 | 405 | 11/19/2025 |
| 1.0.22 | 394 | 11/19/2025 |
| 1.0.21 | 397 | 11/19/2025 |
| 1.0.20 | 405 | 11/19/2025 |
| 1.0.19 | 403 | 11/18/2025 |