Skip to content


Folders and files

Last commit message
Last commit date

Latest commit


Repository files navigation

Control-M Automation API quickstart

This repository contains code samples and how-to for Control-M Automation API.

Online Documentation

You can find the latest Control-M Automation API documentation, including a programming guide, on the project web page.

Contribution guide

To contribute, please follow these guidelines.

Files, folders and naming conventions

  1. Every sample and its associated files must be contained in its own folder. Name this folder something that describes what your sample does. Usually this naming pattern looks like level-sample-purpose (e.g. 201-automate-corrective-flow). Numbering should start at 101. 100 is reserved for things that need to be at the top.
  2. For consistent ordering create all folders in lowercase.
  3. Include a file that explains the sample. A good description helps other community members to understand your sample. The uses Github Flavored Markdown for formatting text. If you want to add images to your file, store the images in the images folder. Reference the images in the with a relative path (e.g. ![alt text](images/sampleImage.png "Sample Image Text")). This ensures the link will reference the target repository if the source repository is forked.
  4. The samples are split into two major categories, Control-M and Helix Control-M. Make sure that you upload the sample under the correct category.