Unity Integrations allow you to connect the following Unity Services in your development workflow to non-Unity tools:
To add an Integration, you must be an Owner or Manager on the Project. For information on assigning roles, see the Members & Groups section of Managing your Organization.
Unity Integrations supports the following non-Unity tools:
Unity Personal limits users to one Integration for all events, but multiple Unity services can use that Integration. Unity Teams, Plus, and Pro users can have up to 100 Integrations. If your Unity Teams, Pro, or Plus subscription expires, Unity keeps all of your current Integrations, but automatically disables them. If this happens, you can still sign into the Unity Services Dashboard and enable a single Integration.
To add an Integration to your workflow:
To configure a webhook Integration, supply the following information:
Parameter | Description |
---|---|
Display Name | A name to identify the Integration in the Integrations list. |
Webhook URL | The URL of the server endpoint that receives the webhook POST requests from the Unity service. |
Authentication Secret | The client secret of your receiving application. |
Content Type | The MIME type of the content. Select the content type of your data from the drop-down menu. |
Disable SSL/TLS Verification | Tick this checkbox to disable verification of SSL/TLS security certificates. Verifying SSL/TLS certificates helps ensure that your data is sent securely to the above Webhook URL. Turning this option on is not recommended, so only do this if you absolutely know what you’re doing. |
To configure Discord Integrations, Unity calls an app that uses the Discord API to register a webhook to a Discord channel. If you do not have a Discord server, see How do I create a server? in the Discord documentation.
Important: You must enable webhooks on the account with which you are integrating.
To complete the configuration:
To configure Slack Integrations, Unity calls an app that uses the Slack API to register a webhook to a Slack channel.
After creating a new Slack integration and configuring the events that you want to appear, you must authorize Unity to access your Slack server.
If you do not have a Slack server, see Create a Slack workspace in the Slack documentation.
To complete the configuration:
Email Integrations notify team members when specified events for your Project occur.
The Unity JIRA Integration allows you to interact with JIRA as follows:
To configure a JIRA Integration for Collaborate or Cloud Diagnostics, you must supply the following information:
Parameter | Description |
---|---|
Display Name | A name to identify the Integration in the Integrations list. |
JIRA Site URL | The URL of your JIRA instance. |
JIRA Username | The user ID of an account that can post updates to your JIRA instance. |
JIRA REST API Token | The API token to authenticate Integration requests to your JIRA server. For instructions on how to create a token, see Atlassian’s documentation. |
After you have entered the information for your JIRA instance, you must supply the following additional information for Cloud Diagnostics:
Parameter | Description |
---|---|
Create Issues In This Project | Select the project in which to create the issues. |
Mark Incoming Issues As | Select the type of issue to log the report as. |
When you make changes in Collaborate, update JIRA-associated issues by referencing the issue key in your commit message. For example, “I fixed the crashes caused by ISS–42” adds publish details to issue “ISS–42”.
To manage existing Integrations:
To edit or delete an existing Integration, click EDIT next to the Integration you want to modify. The types of edits you can make depend on the Integration:
To enable or disable an existing Integration, click the Status toggle to enable or disable the Integration.