Error creating an automation to copy a new Bug to another Instance

[julie_calboutin]

Hi, what should be a really simple thing that I can't get to work.

• Jira Instance 1
  • Create a new work item
  • Triggers an "Send web request" automation to send ID (purely for reference as this will be a new bug in Jira instance 2 with it's own ID), Summary, Description, and type to Jira Instance 2
• Jira Instance 2
  • Receives the "Incoming webhook" POST - this is where it's failing
  • Triggers automation to create a new work item (new ID) of the same type, Summary, and Description

Jira Instance 2 is receiving the call, but the package is empty so the create action fails. I can see the content being sent which includes all of the necessary info above from Jira Instance 1, but is not received.
I personally have access to both domains and Instances.

I saw there was a recent update to the automation but am unsure if this is a bug or I'm doing something wrong. It's like there is a mismatch between what is beings sent (1 single item) vs. what is expected to arrive (maybe an array?)

My layout is this (headers with Tokens and Secrets are all in place)

I am receiving the error

[Jayesh Raghuvanshi]

@julie_calboutin 

The payload is reaching Jira Instance 2, but it’s not being parsed into the automation context because the request isn’t arriving as a JSON object that the Incoming webhook trigger can read via the {{webhookData}} smart value, usually due to Content-Type or structure issues, or using the wrong smart value in the receiving rule. Ensure the sender sets Content-Type: application/json and sends a single JSON object (not an array), and in the receiver use {{webhookData.*}} to map fields when creating the issue

Below could be the reasons

The Incoming webhook trigger expects a JSON body with Content-Type: application/json; if omitted or mismatched, the body won’t be parsed into smart values, making {{webhookData}} appear empty in the rule

The correct smart value in the receiving rule is {{webhookData}} (root of the JSON), not {{webhookResponse.*}} which applies only to “Send web request” responses in the sender rule, so referencing the wrong variable yields blank

Top‑level arrays are not supported by the trigger; if the sender posts [] or a JSON array, Jira cannot deserialize and will not expose usable data to the rule, so always send an object

In “Send web request,” set headers: Content-Type: application/json and include the Incoming webhook secret using header X-Automation-Webhook-Token (or append /SECRET to the URL if headers aren’t possible)

Thanks
Jayesh R

[Gor Greyan]

Hi @julie_calboutin

Welcome to the Atlassian Community!

Let's do some fixes.

In the 2nd instance, which is reciever:

• Edit the rule trigger:

  • Trigger: Incoming webhook

• In the Create issue action, pull values from the webhook using {{webhookData}}:

  • Summary: {{webhookData.summary}}

  • Description: {{webhookData.description}}

  • Issue type: either set a fixed type, or branch by {{webhookData.issuetype}} (if you need to mirror the type).

  • If you prefer advanced JSON, use the “More options” → Additional fields:

    {
    "fields": {
    "project": { "key": "ABC" },
    "issuetype": { "name": "{{webhookData.issuetype}}" },
    "summary": "{{webhookData.summary}}",
    "description": "{{webhookData.description}}"
    }
    }

In the 1st instance, which is the sender:

• Method: POST

• Body: {
  "summary": "{{issue.summary}}",
  "description": "{{issue.description}}",
  "issuetype": "{{issue.issueType.name}}"
  }

[Bill Sheboy]

Hi @julie_calboutin -- Welcome to the Atlassian Community!

First thing, I recommend obscuring / removing your webhook URL in the images you posted.

Next, for fields such as Summary and Description, remember to add the JSON encoding function when including them in the custom data:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-text-fields/#Json-encoding

Kind regards,
Bill

[julie_calboutin]

Hi Bill,

Thanks for your response! Not my webhook URL, that's the help text in the automation, but thanks for looking out.

I'll check out the link.

Julie