Integrations - Recent Threads

Facing issue with default setting of timer trigger setting time in seconds

akshantr0678 — Mon, 25 May 2026 16:56:55 GMT

we are receiving data via web api in Appian. as the volume is very high, we save the events to database to process them later via a second process model which keeps polling the db for pending events.
The issue is that processing should be in ALMOST real time without overwhelming the Appian environment. to do that, we tried to schedule the polling process every 30 seconds. but the minimum time it takes for repeat configuration is 5 minutes which is of no use to us.

how can we configure a process to run every 30 seconds ?

Send Document as Base64 - SOAP Integration

erickjavidb860617 — Fri, 08 May 2026 23:03:21 GMT

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 response in the Integration. However, the main issue is that Appian does not seem to provide a native way to convert a document to Base64 when building a custom SOAP/XML request manually.

Has anyone faced a similar scenario or found a better approach to send documents as Base64 in a custom SOAP/XML request?

Thank you in advance for your help.

Transition from Microsoft to Google

Jamal Case — Thu, 07 May 2026 16:46:33 GMT

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.

My integration object is calling the swagger endpoint multiple times when it is being failed

vijayp6380 — Thu, 23 Apr 2026 11:18:44 GMT

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

Docusign fail return of Oauth

Carmine Mele — Tue, 21 Apr 2026 06:10:50 GMT

We are using a DocuSign integration configured and tested successfully in the development environment with a DocuSign developer account.

However, we are encountering issues during the authorization phase when using the authorization link.

The authorization flow redirects correctly to DocuSign, and the login page is displayed, allowing the user to log in successfully. However, after the login, the system does not return the authorization token to the application as expected.

By checking the application logs, we can see the following error during the OAuth callback processing. This error appears multiple times; below is one example:

2026-04-21 05:57:39,619 [http-nio-8080-exec-794] ERROR com.appiancorp.connectedsystems.http.oauth.OAuthServlet - Error processing request to Appian OAuth callback URL. 
com.appiancorp.suiteapi.common.exceptions.AppianException: Failed to decrypt. Only values of type Encrypted Text can be decrypted. (APNX-1-4260-002)

It seems that the OAuth callback is reached, but the token exchange or decryption step is failing.

I'm trying to recreate connected system or new keys on docusing, but without success.

The AUTHORIZE button in the connected system, go, but we have multiple singers and we have to use authorization link in interface

Appian Actions using ChatGPT

kalaivanank0002 — Mon, 06 Apr 2026 08:10:35 GMT

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.

Need Help Previewing MS Office Documents (Word/Excel/PPT) in Browser via Appian Web API

uditachauhan — Wed, 18 Mar 2026 14:41:53 GMT

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?

Connect to on premise Dynamics CRM from Appian cloud

niharranjanh0001 — Thu, 19 Feb 2026 06:17:08 GMT

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.

Exposed WebAPI GET request size limit?

David Roberts — Tue, 17 Feb 2026 10:54:22 GMT

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?

webAPI taking more time for document download

Ramesh Palati — Thu, 12 Feb 2026 11:55:12 GMT

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.

tostore data from http resppponse to table

harithab835860 — Thu, 12 Feb 2026 08:03:22 GMT

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?

Getting error when creating data store

premr344453 — Fri, 06 Feb 2026 02:25:54 GMT

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)

403 error while uploading file in integration

amriteshg6866 — Fri, 30 Jan 2026 10:23:39 GMT

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.

Query Parameter Encoding Issue: Spaces encoded as + but API encodes it as %20 - Is there a workaround?

ansht119 — Thu, 29 Jan 2026 19:41:45 GMT

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
Standard Query Parameters section - Consistently encodes spaces as + signs
Building URL manually in Relative Path - Same encoding behavior

My Questions:

Is there any way in Appian to force query parameters to use %20 encoding for spaces instead of + encoding?
Is it even possible to pass literal spaces (unencoded) in query parameter values, or will Appian always encode them?
Are there any alternative approaches or workarounds to handle this scenario?

Additional Context:

Integration uses a Connected System with GET method
Cannot modify the external API to accept + encoding
API endpoint only accepts GET requests (POST with JSON body is not an option)
Cannot change the parameter values to avoid spaces (business requirement)

Has anyone encountered a similar issue or found a workaround for controlling the URL encoding format in Appian integrations?

Thank you in advance for any guidance!

Error opening SharePoint Integration Object – HTTP 500 / InvalidUserException

hamzas0003 — Fri, 16 Jan 2026 15:49:48 GMT

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 like to understand:

Whether this could be related to SharePoint user permissions or authentication
If this error can occur due to an expired or invalid SharePoint connection
Any known Appian issues related to InvalidUserException when opening integration objects

Any guidance or suggestions on where to look (logs, permissions, configuration) would be really helpful.

Thanks in advance!

Oracle connection with on prem install

alessandrop3176 — Thu, 15 Jan 2026 11:58:08 GMT

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.

Request/Header not created in oauth2 Integration

MikeMiracle — Tue, 13 Jan 2026 16:01:58 GMT

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

Does Appian Integration Convert Document to BASE64 String If the document field is under nested cdt?

Rahul Gundu — Thu, 08 Jan 2026 22:59:03 GMT

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

Integration error

Jishnu Magunta — Thu, 01 Jan 2026 14:18:43 GMT

Hi ,

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

Trigger access verification on user login using OIDC bearer token in Appian

ankitb703441 — Tue, 30 Dec 2025 07:22:17 GMT

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

Appian + DocuSign: Multi‑region setup using HTTP CS with dynamic accountId

devanshum749680 — Fri, 26 Dec 2025 12:07:58 GMT

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?

SharePoint Connected System

anushar639965 — Mon, 01 Dec 2025 07:02:35 GMT

Hi Everyone,

I am trying to create a SharePoint Connected System using Client Credentials-Entra ID authentication. We have created an Azure AD App and given the app read and write access to a specific SharePoint site.
While configuring the connected system, can I use the link to the specific SharePoint Site in place of the instance URL?

Appian API to let third party system download the document.

GauravSingh — Wed, 26 Nov 2025 12:11:39 GMT

Hi Team,

For one of our clients, we have a requirement to move Appian documents to GCP.

To meet this requirement, I have created an Appian Web API that exposes the document when the document ID is passed as a parameter. However, I am unable to test the API within Appian as it is giving 404 error while I'm testing it.

Here is the Web API code, which was generated using the available Appian API templates, along with the response I receive when testing it by passing the document ID of an Appian document.

Could you please assist?

Appian to SharePoint Integration with Client Credentials-Entra ID

anushar639965 — Wed, 26 Nov 2025 10:25:58 GMT

We are trying to integrate Appian and SharePoint using client credentials Entra Id. When I am trying to test the connection for the connected system, it is giving me the following error:

An unrecognized error was returned

The following status code was returned:403

Please ensure that your configuration is correct

Could someone help me on this.

Docusign embedded sign and code grant authorization

Carmine Mele — Sun, 23 Nov 2025 15:42:32 GMT

We are trying to integrate with docusign embedded component in appian.

I used a code grant authorization with a connected system, with a single user.

When the token is not valid i go to the connected system and click on authorize.

And like that i can even sign embedded in appian or with the url generated.

The problem is that we have a requirements to provide signing with docusign for two distincted users,

That user are not administrator or designer(like me) so cant click the authorize button everytime.

And i see that in the connected system are not a user reference to pass.

So how can i authorize two different user with codegrant?

I have to use two different connected system with a different secret keys?

Use an a!authorizationLink?