Import a Deployment and Confirm Results
A 3-step recipe with Appian. We can help you get access.
Recipe · 3 steps
Import a Deployment and Confirm Results
with Appian
Start an import deployment, poll to completion, and branch on success vs errors.
- Create an import deployment. The Action-Type header is set to import and the multipart form carries the JSON configuration plus the package and optional settings and customization files.
- Poll the deployment results until the import leaves the IN_PROGRESS state, then branch on the terminal status.
- Retrieve the plain-text deployment log when the import did not complete cleanly so the failure detail is available for troubleshooting.
What you'll need to have ready
- apiKey: API key linked to a service account, sent in the appian-api-key header.
- name: Name of the deployment, displayed in Appian Designer's Deploy view.
- description: Optional description of the deployment.
- packageFileName: The deployment package ZIP file content to import.
- adminConsoleSettingsFileName: Optional Admin Console settings ZIP file content to import alongside the package.
- customizationFileName: Optional import customization properties file content mapping source values to target values.
For your developer
Arazzo workflow appian:import-deployment, 3 operations: createDeployment → getDeploymentResults → getDeploymentLog. Specs on APIs.io.