In this article, you will learn how to create and configure an integration, as well as how to use the integration designer to test and troubleshoot problems.
Integrations are created in Application Designer.
Open the destination application for the new integration.
Click New, then choose Integration from the dropdown menu.
Fill out the Create Integration form.
Once you’ve named and described your integration, you can click Create & Edit to start editing the integration immediately, or click Create to just create the object.
If you want to change the description or folder later, select Properties in the integration designer gear menu.
The configuration pane of the integration designer allows you to define the HTTP request details for your integration.
For more information about the integration definition fields, see Integration Objects.
Select whether you want to use an existing connected system to share connection details across multiple integrations. If you created this integration directly from a connected system then this option will already be selected and the connected system will be pre-populated.
Fill out the Connection details. If you are using an existing connected system, select a Connected System using the picker. Otherwise, provide the Authentication details (if applicable) directly, as shown below.
Add Parameters and Headers.
If the selected Method supports it, define the request Body and Content-Type.
Once you've configured the integration definition, it's a good idea to set automatic parsing on the response body.
Automatic parsing only applies to JSON responses.
Instead of having to write a wrapper rule, automatic parsing will convert the results into an Appian value. This will allow you to use dot notation and
index() in another expression simply by passing in an integration rule.
Once you've finished configuring the integration definition, you'll want to test the integration. There are several features to test your integration, and view details about the request and response.
The Result tab displays the Time taken for each phase of the integration and the resulting Value.
If an error occurs, the Result tab also displays the error details and recommended Next Steps.
The HTTP Request tab displays the raw request sent to the external system.
Any request or response body content over 10 KB in size will be truncated in the integration designer. The complete body is available when the integration is called from other objects in your application.
By default, an integration will return an error when it's unable to connect or when the external system responds with an HTTP error status code. Even when the HTTP call succeeds, you may still need to check for error messages or unexpected content before using the response in your application.
You can add custom error handling to an integration within the Error Handling section
a!integrationError()to construct a custom error message.
Instead of returning an unwanted success status, the integration will return an error, allowing you to more easily handle future error handling.
After the integration is tested, you can define inputs that will allow you to reuse this object throughout your application.
Expand the inputs pane on the right hand side of the integration designer.
Click the + button in the top right-hand corner.
Configure the input Name, Type, and whether or not it is an Array from the grid. You can also change the order of inputs using the up and down arrows.
If you have one or more inputs, you can enter values for each input in the test inputs pane. These values are used when testing the integration.