# Webhook for JIRA syntax

**URL:** <https://community.glideapps.com/t/webhook-for-jira-syntax/58617>\
**Category:** Ask for Help\
**Tags:** actions\
**Created:** [March 1, 2023, 8:26am UTC](https://community.glideapps.com/t/webhook-for-jira-syntax/58617 "2023-03-01T08:26:09Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexandr\_Noskov](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/alexandr_noskov/32/55082_2.png) [@Alexandr\_Noskov](https://community.glideapps.com/u/Alexandr_Noskov)\
**Post date:** [March 1, 2023, 8:26am UTC](https://community.glideapps.com/t/webhook-for-jira-syntax/58617/1 "2023-03-01T08:26:09Z")

</div>

How to: Modify JIRA Task status thru JIRA webhook. Do not wanna use [Make.com](http://Make.com).

Stumbled upon a problem.  
JIRA wants a task name to be between ‘[’ and ‘]’, but Glide webhook sends it in ‘{}’

> **[monosnap.com](https://monosnap.com/direct/iOY6pL0mnKrUQD9C5IAP78zksKiW1c)**
>
> Monosnap screenshot tool for Mac and PC with own cloud storage. Take screenshots, record videos and upload files directly to the cloud. Just in one click.

![image](https://us1.discourse-cdn.com/flex002/uploads/glideapps/original/3X/f/2/f23d452edb37817efed6deea7ed0520eab6b5c97.png)

Can I somehow make Gide to transfer task info in appropriate format? Maybe combine a string?

It appears I cannot make a direct link of “Webhoook\_URL?TASK-123” as JIRA requires POST, not GET. Or Glide can POST urls somehow?

---

<div class="post-metadata">

**Author:** ![ricaxa](https://avatars.discourse-cdn.com/v4/letter/r/3da27b/32.png) [@ricaxa](https://community.glideapps.com/u/ricaxa)\
**Post date:** [July 28, 2025, 2:10pm UTC](https://community.glideapps.com/t/webhook-for-jira-syntax/58617/2 "2025-07-28T14:10:31Z")

</div>

Hello

You’re right Glide’s webhook sends data in JSON format using curly braces `{}`, whereas JIRA expects issue keys like `CIT-842` to be wrapped in square brackets `[]` in certain contexts, especially when parsing task names or statuses via webhooks or automation rules. One workaround within Glide is to create a template column that formats the task string with square brackets for example; `[CIT-842]`.

Then; when you configure your webhook payload, reference this template column instead of the raw issue key. This ensures the value sent in the webhook is already properly formatted for JIRA’s expectations.

As for dynamically passing the issue in the webhook URL (like `...?TASK=CIT-842`), that’s not ideal because JIRA requires a `POST` request, not a `GET`. Fortunately, Glide webhooks do support POST requests, so you can include the formatted task ID inside the request body instead of in the URL.

If you’re looking into deeper integration topics, I recently came across something called what is jira and found it fascinating how much can be automated through its API. For reference, here’s the [official JIRA webhook guide](https://developer.atlassian.com/server/jira/platform/webhooks/) to explore further.

Thank you !! 🙂