[Bug] Updating article with API removes table styling | Community
Skip to main content
Submitted

[Bug] Updating article with API removes table styling

Related products:Knowledge & Help CenterIntegrations, API & Custom Actions
  • March 24, 2026
  • 2 replies
  • 25 views

Summary

When an article is created or updated through the REST API / MCP then the `style` attribute on table <td> tags are removed, undoing styling that was applied in the web editor to customize colors or widths.

 

Steps to Reproduce

  1. Use the Knowledge web editor to create an article with a table, assign colors the to the column headers and adjust the column widths.
  2. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body contains the `style` attribute defining background-color and width on the <td> tags.
  3. Use the REST API / MCP to re-save the article as-is.
  4. In the web editor refresh the article and note that the table styling was removed.
  5. Use the REST API / MCP to retrieve the article HTML, note that the retrieved article’s body no longer contains the `style` attribute on the <td> tags.

 

Expected Result

The `style` attribute on the <td> tags defining the background-color and column width is preserved.

 

Actual Result

The `style` attribute on the <td> tags is removed.

 

Example Step 1

 

Example Step 2

<div class="intercom-interblocks-table-container">
<table role="presentation">
<tbody>
<tr>
<td style="background-color: #d7efdc; width: 320px;">
<p class="no-margin">Header 1</p>
</td>
<td>
<p class="no-margin">Header 2</p>
</td>
</tr>
<tr>
<td style="background-color: #e8e8e8; width: 320px;">
<p class="no-margin">Lorem ipsum dolor sit amet</p>
</td>
<td>
<p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p>
</td>
</tr>
<tr>
<td style="width: 320px;">
<p class="no-margin">Ut enim ad minima veniam</p>
</td>
<td>
<p class="no-margin">Consectetur adipiscing elit</p>
</td>
</tr>
</tbody>
</table>
</div>

 

Example Step 4

 

Example Step 5

<div class="intercom-interblocks-table-container">
<table role="presentation">
<tbody>
<tr>
<td>
<p class="no-margin">Header 1</p>
</td>
<td>
<p class="no-margin">Header 2</p>
</td>
</tr>
<tr>
<td>
<p class="no-margin">Lorem ipsum dolor sit amet</p>
</td>
<td>
<p class="no-margin">Sed ut perspiciatis unde omnis iste natus error</p>
</td>
</tr>
<tr>
<td>
<p class="no-margin">Ut enim ad minima veniam</p>
</td>
<td>
<p class="no-margin">Consectetur adipiscing elit</p>
</td>
</tr>
</tbody>
</table>
</div>

 

2 replies

  • New Participant
  • October 7, 2026

I used to use the API to do update multiple articles quickly (i.e mass search and replace).

However, I realized this removed the formatting of tables. I think it also removed the callout colouring too.

With the advent of AI, which can make mass updating really easy, why can’t I do via the API what we can do in the editor?

I have used to AI to read the information via the API and notify me on a number of small fixes I can make, but if there are over a 100 changes, why do I have to do it by hand? 

Furthermore, what if I want to make my own editor because I’m not satisfied with your editor. Again, I cannot, because the API will not let me alter the styling of tables. 

There are so many Quality of Life improvements I am willing to create myself for Articles, but I cannot, because the API does not allow me to do what the editor does. 


I am facing the same issue.

It would be very useful if the API supported preserving or setting column widths (for example via HTML attributes or CSS styles) so tables imported programmatically can maintain consistent layouts without manual rework.