> For the complete documentation index, see [llms.txt](https://docs.meta-inf.hu/myra-master-your-ratings/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/automation-configuration.md).

# Automation configuration

Send every feedback submission to a Jira Automation rule, so the rule decides what counts as negative and creates the work item.

Open a Feedback Survey's settings and go to the **Automation** tab to connect it to a Jira Automation rule. This lets you automatically create a Jira Task whenever a customer leaves feedback that your rule considers negative - or trigger any other Automation action you like.

{% hint style="info" %}
Myra does not decide what counts as "negative". It sends every submission's raw data to your Jira Automation rule, and the rule itself makes the threshold decision and takes the action. This keeps the logic fully in your hands - change the threshold, the action, or the notification anytime, without touching Myra's settings.
{% endhint %}

### How it works <a href="#how-it-works" id="how-it-works"></a>

1. A customer submits feedback for a survey that has a webhook configured and enabled.
2. Myra sends the submission's score, comment, per-question answers, and related Jira context to your saved webhook URL shortly after. The customer's submission is never delayed by this - it completes instantly either way.
3. Your Jira Automation rule receives the data, checks whatever condition you've set (for example, "rating below 3"), and runs whatever action you've configured - typically creating a Jira Task.

### Which surveys support it <a href="#which-surveys-support-it" id="which-surveys-support-it"></a>

| Survey type                                        | Automation tab available? |
| -------------------------------------------------- | ------------------------- |
| Request survey (attached to a specific Jira issue) | Yes                       |
| Project survey                                     | Yes                       |
| Public / standalone survey                         | Yes                       |
| Native JSM request-CSAT survey                     | No                        |

{% hint style="info" %}
The **Automation** tab doesn't appear in Settings for native JSM request-CSAT surveys, since Jira Service Management already handles those responses natively. If you're using the built-in CSAT and want a similar "notify on bad rating" rule, see Atlassian's guide: [How to send a notification when bad customer satisfaction is received](https://support.atlassian.com/jira/kb/how-to-send-notification-when-bad-customer-satisfaction-received-in-automation/).
{% endhint %}

### Set it up <a href="#set-it-up" id="set-it-up"></a>

#### 1. Create the Automation rule in Jira <a href="#id-1-create-the-automation-rule-in-jira" id="id-1-create-the-automation-rule-in-jira"></a>

1. In Jira, create a new Automation rule and add an **Incoming webhook** trigger.
2. Copy the trigger's URL - it looks like `https://api.atlassian.com/automation/...`.

#### 2. Connect the survey in Myra <a href="#id-2-connect-the-survey-in-myra" id="id-2-connect-the-survey-in-myra"></a>

1. Open the survey's **Settings**, then the **Automation** tab.
2. Paste the Automation trigger URL into **Webhook URL**.
   * Myra only accepts URLs starting with `https://api.atlassian.com/automation/`, so feedback data can never be sent anywhere else.
3. Set a **Secret**. Myra sends it back on every delivery in the `X-Automation-Webhook-Token` header, so your rule can verify the request really came from Myra.
   * Leaving this field blank on a later edit keeps the secret you already saved - you don't have to re-enter it just to change the URL or toggle.
4. Turn on **Enabled**.
5. Click **Save**.

#### 3. Send a test payload <a href="#id-3-send-a-test-payload" id="id-3-send-a-test-payload"></a>

Once you've saved a URL and a secret, use **Send test payload** to fire a single test delivery and confirm your rule receives it. The button stays disabled until there are no unsaved changes, a secret has been saved, and the toggle is on - the tab tells you which of these is still missing.

#### 4. Build the rule's logic <a href="#id-4-build-the-rules-logic" id="id-4-build-the-rules-logic"></a>

Expand **See example payload** on the Automation tab to copy the exact JSON shape this survey will send, built from its real questions - use it as the reference while you design the rule. In your Automation rule, the incoming JSON is available under the `webhook.body` smart value:

1. Add a condition on `{{webhook.body.feedback.primaryScoreType}}` and `{{webhook.body.feedback.primaryScore}}` - for example, `"Rating"` and less than `3`.
2. Add a **Create issue** action, with **Project** set to `{{webhook.body.jiraContext.projectId}}`.
3. Build the **Summary** / **Description** from `{{webhook.body.survey.name}}`, `{{webhook.body.feedback.comment}}`, and `{{webhook.body.feedback.answers}}`.
4. For request-scoped surveys, `{{webhook.body.jiraContext.issueKey}}` is also available - branch on `{{#exists(webhook.body.jiraContext.issueKey)}}` to link back to the original issue.

### Payload reference <a href="#payload-reference" id="payload-reference"></a>

| Field                              | Description                                                                                                                               |
| ---------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------- |
| `survey.name`                      | Name of the survey the feedback was submitted to.                                                                                         |
| `feedback.primaryScore`            | The main question's score, as a number - `null` if the survey's main question isn't a rating or number question.                          |
| `feedback.primaryScoreType`        | `"Rating"` or `"Number Pick"`, matching `primaryScore`.                                                                                   |
| `feedback.primaryScoreQuestion`    | The main question's text, for use in tickets and notifications.                                                                           |
| `feedback.comment`                 | The customer's comment, or an empty string if none was given.                                                                             |
| `feedback.submitterId`             | The customer's Jira account ID (request-scoped surveys), or a stable anonymous ID (project/public surveys, which don't collect identity). |
| `feedback.answers`                 | Every question's answer, each with its own text and type - so a rule can list the full submission in a ticket description.                |
| `jiraContext.issueId` / `issueKey` | The Jira issue the feedback relates to (request-scoped surveys only).                                                                     |
| `jiraContext.projectId`            | The Jira project the feedback relates to (request and project-scoped surveys). Absent for public surveys, which aren't tied to a project. |

All fields above are read through `webhook.body.<path>` in your Automation rule, for example `{{webhook.body.feedback.comment}}`.

Example, for a request-scoped survey:

```json
{
  "event": "feedback.submitted",
  "timestamp": "2026-09-22T13:40:00.000Z",
  "survey": { "name": "Support CSAT" },
  "feedback": {
    "primaryScore": 2,
    "primaryScoreType": "Rating",
    "primaryScoreQuestion": "How would you rate your experience?",
    "comment": "The fix didn't work and the response was slow.",
    "submitterId": "5f8a2e1c-...",
    "answers": [
      { "question": "How would you rate your experience?", "type": "Rating", "value": 2 },
      { "question": "Leave a comment (optional)", "type": "Text", "value": "The fix didn't work and the response was slow." }
    ]
  },
  "jiraContext": {
    "issueId": "10042",
    "issueKey": "SUP-1042",
    "projectId": "10000"
  }
}
```

For project-scoped surveys, `jiraContext` only contains `projectId`. For public/standalone surveys, `jiraContext` is left out entirely.

### Good to know <a href="#good-to-know" id="good-to-know"></a>

* Myra sends **every** answer on every submission - it doesn't pre-filter for "negative" ones. Your rule's condition decides what to act on.
* If a delivery has to be retried after a temporary network issue, your rule may see the same submission twice. Design your rule to tolerate that if it matters for your use case.
* For request-scoped surveys, if the related Jira issue was deleted or moved before delivery, that delivery is skipped rather than retried.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.meta-inf.hu/myra-master-your-ratings/use-myra/automation-configuration.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
