JIRA Automation: publish a new page in Confluence fails on lookupIssues smart values

[Ryan Saul]

I am attempting to use this new Publish a new page in Confluence automation. I have the connection setup and I have confirmed that I can create simple pages if the smart values are simple, like a webhook value.

But I have a list of issues that I would like to publish with and that seems to be tripping up this automation rule.

We use the "Lookup work items" automation to get a list of relevant items for later automation steps. Importantly, we have other actions that work successfully using #lookupIssues and smart values.

I have tried several approaches to this and all are encountering the following error:

Could not parse page content. If you are using the {{agentResponse}} smart value, try changing the agents prompt.

Approach 1 - this is what we can use in our Teams messages currently:

{{#lookupIssues}}{{#if(equals(issueType.name, "Story"))}}
📗 [{{key}}]({{url}}) *{{Release Notes}}*

{{/}}{{/}}

Approach 2:

{{#lookupIssues}}

{{key}} - ({{url}})

{{/}}

Approach 3 - this uses code snippets as mentioned in the documentation:

```

{{#lookupIssues}}

{{key}} - ({{url}})

```

Approach 4 - this is taken directly from the example given on the documentation:

```

{{#lookupIssues}}

<a href="{{url}}">{{key}} - {{summary}}</a>

```

All of these approaches have the above error in the audit log.

Please help, it was already very difficult to get the original approach to work with Teams, but I can't figure out how to get this working on this new automation at all.

[Bill Sheboy]

Hi @Ryan Saul -- Welcome to the Atlassian Community!

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution

Until we see those...

Have you checked if any of the fields included in the content for the page contain characters which cannot be used in that action to create a page?  For example, special characters in the Summary or Release Notes fields you note.

Kind regards,
Bill

[Ryan Saul]

Hi Bill, I won’t be able to get those screens until tomorrow unfortunately. I believe Approach 3 rules out the special character issue no? 

I was hoping someone with experience with this new automation could provide an example that works for them on the lookupIssues API. I’m able to get a simple smart value to work, but lookupIssues throws this error consistently.