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 to explore further.