About Zapier Community
New to our Community? Get to know more about our space and how to make the most of your time here.

Code of Conduct Community FAQ's Zapier Common Questions What to Expect

Get Started With Zapier
New to Zapier? We have got you covered with our Zapier 101 Resources.

Zapier Essentials

Get Support
Have a question? Let's get you an answer!

How Do I...? Troubleshooting Code & Webhooks Developer Zone

Other Help Resources
Wait, there's more! Check out these Community sourced spaces for additional resources.

Zapier Help Center Hire an Expert

Zapier Products
Learn more about Zapier's new products.

Zapier Tables Zapier Interfaces

Zapier Reading
All of our best learning resources can be found here.

Featured Articles Show & Tell AI Hub Zapier Tools Hub

Learning Groups
Excited to meet other builders? Check out our interest areas full of doers, dreamers, and in-betweeners.

User Groups

Other Learning Resources
Some of our favorite additional ways to upskill your Zapier knowledge.

Zapier Learn Zapier Blog Zapier Webinars

Product Updates
Check out what is new and upcoming with Zapier with our regular product updates.

Product Updates

Early Access Program
Want to join Early Access? Learn more here.

Question

Zap from Salesforce to Confluence failing because of special characters

  • 28 July 2023
  • 1 reply
  • 101 views
MMonteyne

I am taking text from a Salesforce Task and sending it to Confluence as a new page. Working like a charm. However, in one of our notes, there is an "&" and it is causing this error.

com.atlassian.confluence.api.service.exceptions.BadRequestException: Error parsing xhtml: Unexpected character ' ' (code 32) (missing name?)

Yet I can take the same text and paste it directly into a confluence page without issue.  I am sure special characters are going to occur occasionally in our teams Salesforce notes.

Suggestions?

1 reply

GetUWired
Userlevel 7
Badge +12

Hey @MMonteyne, 

I actually ran into a similar issue recently where the “&” was causing some issues. 

For me, the fields with & were being used as query parameters in the API call.  Since & is a special character that separates query variables, I was getting a similar error.

I was able to fix it by changing the “&” characters into “%26” in the code.

 

For you, I would add a step where you would replace all instances of & with “%26” or just “and” to potentially fix this.

 

Hope this helps!

Reply


Terms & Conditions