<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="https://community.appian.com/cfs-file/__key/system/syndication/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Send Document as Base64 - SOAP Integration</title><link>https://community.appian.com/discussions/f/integrations/40410/send-document-as-base64---soap-integration</link><description>Hello everyone, 
 I hope you are doing well. 
 I am currently facing an issue while sending a SOAP request through an Appian Integration. The request body contains a document that must be sent as Base64 inside the XML body. 
 
 I have been researching</description><dc:language>en-US</dc:language><generator>Telligent Community 12</generator><item><title>RE: Send Document as Base64 - SOAP Integration</title><link>https://community.appian.com/thread/154589?ContentTypeID=1</link><pubDate>Tue, 12 May 2026 16:20:43 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:9ef784a0-c729-48f7-a8b2-49ab5ac5dd64</guid><dc:creator>erickjavidb860617</dc:creator><description>&lt;p&gt;Thank you for your response and for sharing your experience.&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;I&amp;rsquo;m going to try the database plugin approach first and evaluate how stable it is in our case. As you mentioned, I&amp;rsquo;ll make sure to clean up the temporary table after each execution.&lt;/span&gt;&lt;/p&gt;
&lt;p class="isSelectedEnd"&gt;&lt;span&gt;If that approach becomes difficult to maintain or introduces performance issues, I&amp;rsquo;ll probably consider either a custom plugin or an intermediate service to handle the XML/Base64 transformation outside of Appian.&lt;/span&gt;&lt;/p&gt;
&lt;p&gt;&lt;span&gt;Thanks again for the suggestions.&lt;/span&gt;&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item><item><title>RE: Send Document as Base64 - SOAP Integration</title><link>https://community.appian.com/thread/154569?ContentTypeID=1</link><pubDate>Sat, 09 May 2026 09:22:21 GMT</pubDate><guid isPermaLink="false">d3a83456-d57b-489c-a84c-4e8267bb592a:d51d6c7c-1aff-481e-b058-7b9f7dbca30b</guid><dc:creator>Stefan Helzle</dc:creator><description>&lt;p&gt;This is a very well known issue. The limited support of separate Base64 conversion is the memory consumption and potential risk of system stability.&lt;/p&gt;
&lt;p&gt;All my past experiences with SOAP and Appian have been painful. Mostly caused by the pure chaos of SOAP.&lt;/p&gt;
&lt;p&gt;I think that the most direct approach ist that database plugin trick. Just make sure to clean that table after the call.&lt;/p&gt;
&lt;p&gt;If this does not work, I suggest a custom plugin. A middleware or API gateway doing translation from/to JSON &amp;amp; XML might also be an alternative.&lt;/p&gt;&lt;div style="clear:both;"&gt;&lt;/div&gt;</description></item></channel></rss>