Documentation

Create webhooks to replace your integrations with Jira and Trello

To maintain your workflow automation, migrate your integrations with Jira and Trello to webhooks.
Read time 3 minutesLast updated 14 hours ago

Integrations with Jira and Trello are deprecated from August 15, 2026. To maintain your workflow automation, replace these integrations with webhooks to connect to Jira automation, or to Trello as a custom service:

Create a webhook with Jira automation

Before you create the webhook, you must first create an automation rule in Jira.

1. Create a Jira automation rule

To create a Jira automation rule that listens to the Unity webhook and creates issues, complete these steps:
  1. In your Jira project, go to Project Settings > Automation.
  2. Select Create rule.
  3. Choose this trigger:
    Incoming webhook
    .
    Jira creates a webhook URL.
  4. Copy the webhook URL and save it for later.
  5. Add this action:
    Create issue
    .
  6. Map the fields from the webhook payload:
    • Summary:
      {{webhookData.topic}}
      or a custom template.
    • Description:
      {{webhookData.data}}
      . Adjust the content based on the information that you need.
    • Issue type: bug, task, or any type that fits your workflow.
    • Project: your target project. If you want to keep the same settings as in your current integration with Jira, configure the same project and issue type as in your current integration with Jira.
  7. Save and enable the rule.

2. Create a Unity webhook

To create a Unity webhook, complete these steps:
  1. In the Unity dashboard, go to Projects, and then select your project.
  2. On the Settings tab, select New Integration and then Webhook.
  3. Paste the Jira automation webhook URL that you have copied from Jira.
  4. Select the events for which you want to be notified:
    • New crash
      : when a new crash group is detected
    • Crash reopened
      : when a previously resolved crash occurs again
    • Bug report received
      : when a new bug report is submitted
    • Build events
      : if applicable, when a build succeeds or fails
    These events must match the events of your integration with Jira.
  5. Save the integration.

3. Test your integration

To test your integration, complete these steps:
  1. Trigger a test event.
  2. Verify that a Jira issue is created with the expected fields.

Create a webhook to connect with Trello as a custom service

Contrary to Jira, Trello has no first-party automation rules. To replace the integration, you need a small service that receives the Unity webhook notification and that calls the Trello API to create a card. You keep full control over how Trello cards are formatted. You don't need an SDK or a third-party automation tier.

1. Create a service that receives webhook notifications and calls the Trello API

To create this service, complete these steps:
  1. Set up a public HTTPS endpoint:
    • Cloud Function
    • Lambda
    • Your own server
    • Anything that can handle the POST method
  2. In the handler service, parse the JSON payload and call the Trello
    POST /1/cards
    API with this information:
    • Your Trello API key and token.
    • The list ID (
      idList
      ) of your target Trello board. If you want to create cards on the same board as with your current integration with Trello, use the same list ID as in your current integration.
    • A card name and description that are built from the payload.

2. Create a Unity webhook

To create a Unity webhook, complete these steps:
  1. In the Unity dashboard, go to Projects, and then select your project.
  2. On the Settings tab, select New Integration, and then select Webhook.
  3. Create a webhook that points to your endpoint, and select the same events as in your current integration with Trello.

3. Test your integration

To test your integration, complete these steps:
  1. Trigger a test event.
  2. Verify that a Trello card is created with the expected format.

JSON payload from the webhook to your service

When a triggering event occurs, Unity Cloud sends a JSON payload to your webhook URL. The JSON payload has this structure:
{ "project": { "id": "<project-uuid>", "genesisId": "<project-genesis-id>", "name": "<project-name>", "organizationId": "<organization-id>", "organizationGenesisId": "<organization-genesis-id>" }, "data": { "<event-specific-field>": "<value>", "<event-specific-field>": "<value>" }}
The data object contains event-specific fields that vary depending on the webhook event.

Events and their content

Previous integration with Trello or Jira

Webhook event

Payload content

Action on new bug report
diagnostics.bugreporting.received
Title and description of the bug report, information on the reporter
Action on new crash
diagnostics.crash.problem.new
Information on crash group, exception type, stack trace summary
Action on reopened crash
diagnostics.crash.problem.reopened
Same as for a new crash
Action on build success
devops.build.success
Build platform, build number, download link
Action on build failure
devops.build.failure
Build details with information on errors

Unity Support

If you have questions or if you need assistance, contact Unity Support.