nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Send Web Request

Birthe Schmidt

I have created an automation in Confluence, that collects some information from a Confluence page (stored in a variable) I want to update an issue in Jira with these variables.

My trigger is "Task status changed"

I have two variables:

1) {{CommittedValue}}

2) {{JiraTicketNo}}

Both variables are coming out correctly.

I am using "Send web request" to put the two variables into Jira:

I am the owner of the project in Jira. I have created the Jira ticket/issue. I have created the Token. And I have developed the Confluence Automation.

But I get this error message:

Can anyone see what I am doing wrong???

Accepted answers

Bill Sheboy

Hi @Birthe Schmidt

There could be several causes for what you see. Here are some diagnostic things to try...

#1) How do you know the variables are parsing correctly?

I recommend adding the {{#debug}} ... {{/}} function around the smart value expressions in the Create Variable actions, and then you may confirm the values in the log.

#2) Automation rule actions such as Send Web Request can have timing problems where smart value expressions are not processed fast enough before they are used...leading to strange errors.

The way to mitigate that for Send Web Request is:

Create a variable for the dynamic URL, forcing it to be fully evaluated before it is needed. Then use that variable as the URL in the action. This also allows adding the noted debug function for additional logging.
Create a variable for the entire, dynamic JSON expression, repeating the above steps to use the variable name as the JSON.

#3) What is the type for your customfield_23434?

The JSON expression may not be correct, based upon the field type. Please look here to confirm your expression matches what is expected: https://support.atlassian.com/cloud-automation/docs/advanced-field-editing-using-json/

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Birthe Schmidt

There could be several causes for what you see. Here are some diagnostic things to try...

#1) How do you know the variables are parsing correctly?

I recommend adding the {{#debug}} ... {{/}} function around the smart value expressions in the Create Variable actions, and then you may confirm the values in the log.

#2) Automation rule actions such as Send Web Request can have timing problems where smart value expressions are not processed fast enough before they are used...leading to strange errors.

The way to mitigate that for Send Web Request is:

Create a variable for the dynamic URL, forcing it to be fully evaluated before it is needed. Then use that variable as the URL in the action. This also allows adding the noted debug function for additional logging.
Create a variable for the entire, dynamic JSON expression, repeating the above steps to use the variable name as the JSON.

#3) What is the type for your customfield_23434?

Kind regards,
Bill

Birthe Schmidt

Hi Bill, thank you so much for your support. The {{#debug}} ... {{/}} function was really helpful for me, and I learned something new.

The root cause of the problem was the token/auth. - I used a Basic but the format should be Base. After converting it, it worked.

Gunjan Jeena

Of course, web requests are possible from Confluence, but everything depends on what exactly you want to achieve. In case of a basic integration, automation rules and add-ons from the Atlassian Marketplace would be the simplest way. If you require something more specific, then you should take advantage of the Confluence REST API in combination with some external service or webhook.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud