Projects

In Workato, projects are used to organize automation assets and control access. A project holds a set of related assets for your automations, including connections, recipes, and subfolders.

The Project APIs enable you to programmatically manage and deploy projects to the environments provisioned in your workspace.

---

Understanding project deployment

In Workato, there are two ways to deploy projects:

• Build and then deploy. This approach can be used if you want to commit the package to an external version control system. Steps for accomplishing this would be similar to the following:

  1

  Build the project: {{ $frontmatter.build_a_project.method }} {{ $frontmatter.build_a_project.endpoint }}

  2

  Verify the project built successfully: {{ $frontmatter.get_project_build.method }} {{ $frontmatter.get_project_build.endpoint }}

  3

  If committing to a version control system like GitHub, use the download_url from Step 2’s response to download the package.

  4

  Commit the package to your version control system.

  5

  Deploy the project build to an environment: {{ $frontmatter.deploy_project_build.method }} {{ $frontmatter.deploy_project_build.endpoint }}

  6

  Verify the project deployed successfully: {{ $frontmatter.get_a_deployment.method }} {{ $frontmatter.get_a_deployment.endpoint }}

• Build and deploy in one step. If you don’t need to commit the project to a version control system, you can use this approach:

  1

  Build and deploy the project to an environment: {{ $frontmatter.deploy_a_project.method }} {{ $frontmatter.deploy_a_project.endpoint }}

  2

  Verify the project deployed successfully: {{ $frontmatter.get_a_deployment.method }} {{ $frontmatter.get_a_deployment.endpoint }}

Quick reference