Answer

Hub can accept any JSON payload and can transform it via scripts to conform to the user defined models. In general, if your tool can send it, Hub can receive it (though it is recommended that you work with customer care to confirm if the use case is appropriate for a Gateway integration).

Tools send information about the event to the Hub Sync Gateway add-on using a simple REST call. These tools typically use web hooks or call a script that packs the necessary information into a JSON payload and sends the information to Hub. No further coding is required; based on configuration using our graphical user interface and the underlying artifact models, Hub will either create or modify an artifact in one of the connected lifecycle tools. Hub can be configured to handle even the most complex of software development and delivery workflows and artifact relationships.

The important things to note are:

1) The use case has to be "fire and forget" - meaning you can send information in one direction from your Gateway tool to your other repository. You will not be able to flow updates from the other repository back into your Gateway tool. Gateway is one-direction.

2) The Gateway tool must have APIs to be able to get at the artifacts

This can only be determined with certainty by working directly with customer care. If you are utilizing a Gateway integration, you may need to do some coding to enable the tool to send the information to Hub as a JSON Payload (or work with our Professional Services team to do so).