Integrations

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 possible solutions, and according to the Appian documentation, automatic Base64 conversion only seems to work when using a Data Type (CDT) with automatic XML conversion enabled. However, in my case, the XML structure required by the service contains specific namespaces and a custom structure, so when I tried using a CDT, the generated XML did not match the expected format and the service returned a 500 status code. I also found some plugins that convert documents to Base64, but my requirement is only to convert the document temporarily and send it in the request body. I do not need to store the Base64 value in the database. Another alternative I considered was creating an Appian Web API that returns the Base64 content and then consuming that res

Our client has transitioned from Microsoft to Google Workspace and no longer provides Microsoft licenses, meaning end users can no longer open the .xlsx files generated by our current Excel Tools v2.10 implementation. We need to convert our data export functionality to a format native to Google so users can access their reports without needing Excel. What is the recommended workaround to replace the Excel tools plugin smart service? We are looking for an alternative that avoids physical Excel files entirely to ensure a seamless experience for our users.

Hi, When I call a web API from another web API within the same server, the external url parameter value of the final web API iin the httppost request doesn't seem to work but I have to give the localhost url -  like this :localhost:8080/.../webapiname. Why is that and will this work in all environments? I understand it is not ideal to call this way, but I a little confused as to why the direct url is not working. 

My integration object  is calling the swagger endpoint multiple times when it is being failed. We have a log system in our SQL DB. When I test the endpoint from swagger, I am getting only one log but when I am I clicking on Test Request in the integration I am getting multiple logs

Hi Experts, Third party app admin has provided me API to call along the bearer token to authorize. Kindly suggest if  Appian can use such bearer token Authorize the API calls or not if yes then can we use it in our connected system or not, for now I have used it directly in the integration object as header but its not working. While using below Request payload in Appian Integration object its not being read properly because of the [ ] brackets.{ "advanced_search": { "condition_rules_attributes": [ { "type": "ProfileTypeRule", "comparison_operator": "==", "value": "some vale" }, { "type": "ProfileStatusRule", "comparison_operator": "==", "value": "Active" }, { "type": "ProfileAttributeRule", "condition_object_id": "some value", "object_type": "NeAttribute", "comparison_operator": "==", "value": "some value" } ] } }

Good Day Expert, Is it possible to call Appian actions and related actions using OpenAI ChatGPT in Appian?If yes, could you please guide me on this? Thanks in advance. Cheers, Kalai.

Hello All, Below is the code snippet from Ruby. Digest::SHA256.base64digest('') I need to generate the same in Appian and pass it to the integration header parameter, please let me know if anyone has done this before. Thank You, Sneha.

Hi everyone, We’re working on enabling document preview functionality in our Appian application. We created a Web API that can successfully preview and download documents from the UI. However, we’re facing an issue specifically with Microsoft Office files (Word, Excel, PowerPoint). Instead of previewing in the browser, these files automatically download. Current behavior: PDF files preview correctly in the browser MS Office files (.docx, .xlsx, .pptx) always trigger a download, regardless of browser settings We are returning the document via a Web API using proper headers, but preview still doesn’t work What we need help with: Is it possible to preview MS Office documents directly in the browser using Appian? Does Appian support inline preview of these formats, or do we need an external viewer (Office Online Viewer, Google Docs Viewer, etc.)? Any recommended approach, best practices, or sample configurations to achieve inline preview?

Has anyone experience with Connecting on premise Dynamics CRM system with Appian Cloud instance ? Can it be readily done ? If not what are the pre-requisites to be completed . The On-prem system moreover is on local ADFS authentication.

I have found information regarding a 5MB limit when my Appian application uses an Integration Object to call another API hosted on an external system. However, if my Appian application is exposing a WebAPI, so that an external system can make a GET request to my Appian application, is there a size limit on the JSON payload that my Appian WebAPI can return to that external system?

I have a webAPI which will receive the document from external system in binary format, but for file size around 25 MB, the API is taking more than 25 seconds.Is there any way we can increase the API performance by reducing the time taken by it?Thanks in advance.

In http response I am getting IDs and codes. Each id will have multiple codes. now i need to store the code with respective Id in table. How to do it?

i am trying to create a data store , i have already created teh data type and i can see teh field from database , The data source schema does not match the type mappings: Schema-validation: missing table [`xxxx_LIST`] (APNX-x-xxx)

what is the maximum limit of data that an integration call can retrive/query/ get  in vice versa .., How much (what is the maximum limit) of data we can expose to the external systems (when using WEB API's), where we can configure/ set these data limits

Hello Appian Community, I'm experiencing a URL encoding challenge with query parameters in an integration and would like to know if there's a solution or workaround. The Problem: I need to pass query parameter values that contain spaces (e.g., "North America") to an external API via a GET request. When I use Appian's standard Query Parameters in my integration object, the spaces are encoded as + signs, resulting in ?searchText=North+America. However, the external API we're integrating with does not recognize + as a space character and requires spaces to be encoded as %20 (i.e., ?searchText=North%20America). What I've Tried: Pre-encoding the parameter with substitute() - Replacing spaces with %20 before passing to the integration causes double encoding, resulting in %2520 because Appian encodes the % character itself Using urlwithparameters() function - Still produces + encoding for spaces, which follows the application/x-www-form-urlencoded standard Stand

Hi Team, I’m encountering an issue while uploading a file as part of the integration. The upload works fine for PDF files, but when I try with a .rtf.gz file, I receive a 403 Forbidden error. Interestingly, when I upload the same file to the same URL using Postman, it works without any problem. Could someone please look into this integration issue and help me resolve it? Thanks in advance.

We are looking for connect our appian with on prem oracle via jdbc. We are trying to understand the error, but the suite/logs result in 403. There's another way for read it? We cannot have a troubleshooting without this kind of information.

Hi everyone, I’m facing an issue while trying to open an Integration Object related to SharePoint in Appian. Whenever I try to open the integration object, Appian shows the following error message: Il sistema ha rilevato un errore Codice HTTP: 500 APNX-1-4198-000 Errore durante la valutazione dell’espressione UI Errore di valutazione dell’espressione (evaluation ID = YGR65): com.appiancorp.connectedsystems.templateframework.functions.pipeline.proxyDecoratorPipeline.TemplateInvocationException com.appiancorp.suiteapi.common.exceptions.InvalidUserException Important details: This issue happens only with SharePoint Integration Objects Other integration objects open correctly The error occurs while opening the integration object, not during execution The connected system is already configured in other environments works just fine,only in test and dev environments give this error Has anyone encountered a similar issue with SharePoint integrations? I’d lik

Normal http get integration. Getting below error and clearly query url is not created  . It is working with bruno/postman. hardcoded the bearer authorisation token into the appian integration , getting the same  error as below HTTP REQUET Note: The HTTP request did not include the following headers because they contained empty values: Authorization Accept X-IBM-Client-Id Content-Type Headers with empty values will be included in the request. Test again to see the results. RESULT error-result-label Connection timed out error-result-guidance The integration execution time exceeded the configured timeout Next Steps Retry the request later Set the timeout to a higher value

Hi  I need to pass document as a base64 string to third party integration and the structure is as a nested cdt. I did configure everything correct in cdt and passed cdt as a integration body. But I'm getting a timeout error.  Could anyone faced similar issue? When I did check on request, Appian is converting into xml code, and it's adding <n> to the xml. For example <n1: OlUploadDocument></n1: OlUploadDocument> But it should convert as <OlUploadDocument></OlUploadDocument> and when I remove this <n> and sending it as a body in postman it's working. I was thinking is it because of extra <n> in the structure? May I know, how to overcome? Please let me know Thanks

Hi Everyone, I’m working on the Deployment API export action and am encountering an "Invalid API Key" response. When i make a Deployment API POST call to Environment-A from Postman and Environment-B(Self-managed cloud), both are returning the same error: Response: 403 - Invalid API Key Message: "Invalid API Key. Contact your Appian system administrator to obtain the proper credentials." Error Code: APNX-1-4552-001 Here’s what I’ve checked so far: Admin Console: I reviewed the web API authentication page (/suite/admin/page/web-api-authentication), and I noticed that the last used date and time are populated. Login Logs: I also checked the Login-audit.csv file, where I can see an entry showing a successful login for Web-API service account. Does anyone have any insights or suggestions on what might be causing this issue or how I can resolve it? Thanks in advance!

Hi , Getting the below error when testing my integration. Can one of you help me out if i am missing something ?

I am looking for advice on automating an access verification step in Appian. Each time a user logs in via OIDC, we need to call an external endpoint to verify their access. The endpoint requires the user bearer token issued at login, and we can only reliably perform the check while the user session is active. Because of this, we cannot defer the verification to a scheduled job. Is there a recommended Appian pattern to run logic immediately on login, so we can call the endpoint once and persist the user’s access in an Appian table. The goal is to avoid invoking the external API on every site page load. I tried using a service backed record, but it still requires a trigger such as a record view load. Similarly, a process model still needs a user action to start. Are there any platform supported options for a login hook, post authentication trigger, or another best practice approach to achieve this Any guidance would be appreciated. Thanks

Our Appian application serves multiple geo regions (NA, EU, APAC). Each region uses a separate DocuSign account—and DocuSign’s REST endpoints require the accountId in the path (e.g., …/accounts/{accountId}/envelopes). We also need to route to the correct base URI for each account/region. Goal: Make the integration scalable and configurable by: Using an HTTP Connected System so we can manage auth/base URL centrally and pass accountId as a rule input in each Integration. Dynamically selecting the correct base URI (per account/region) via DocuSign’s /oauth/userinfo (then cache it) or from the Apps & Keys page. \ Planning a future switch to JWT Grant so the integration runs with a service account (no interactive login), impersonating a user with consent.  Is it possible to implement the solution. If yes what are the limitation?

Hi , I am trying to setup new Azure connected system to upload document to Sharepoint , I have done all the setup as mentioned in the below appian link Integrating SharePoint with Appian's Connected System - Appian 24.4 now error I am getting admin approval required when I tried to authrize this connected system only access which I am not able to provide is this :-  Click Application Permissions. Select the following permissions: Sites.Read.All Sites.ReadWrite.All My origination is a bank and they don't grant above 2 permissions to any app, is there any work around in Appian to resolve this as I am blocked due to this only and getting below mentioned error in Appian.