CloudSlang is an open-source workflow automation and orchestration project centered on a YAML-based language, an execution engine, a CLI, reusable content packs, and developer tooling. The organization brings together the core runtime, ready-made automations, Java actions, SDKs, editors, packaging utilities, documentation, and test assets needed to build and run orchestration at scale.

The integrations below are extracted from the CloudSlang content ecosystem and link directly to their respective sections in cs-content.

• Language, engine, and CLI for building and running CloudSlang flows
• Reusable content packs for cloud, infrastructure, ITSM, messaging, OCR, databases, and more
• Java actions and SDKs for extending integrations programmatically
• Docs, website, and editor integrations for onboarding and productivity
• Utilities, generators, packagers, and tests for contributor and release workflows

flowchart LR
	user([Developer or Operator]) --> cli[CloudSlang CLI]
	cli --> workflow[Workflow File\n.sl flow or operation]
	workflow --> score[Score Engine]
	score --> steps[Workflow Steps\nand Decisions]
	steps --> actions[Java Actions / Content Operations]
	actions --> targets[Cloud, ITSM, Database,\nMessaging, OCR Targets]
	targets --> output[Execution Results]
	output --> cli

Start with cloud-slang for the CLI and runtime, and cs-content for reusable workflows.

Get the latest CloudSlang CLI bundle from:

• Stable release
• All releases

From the extracted package, run:

cd cslang\bin
./cslang.bat

On Linux:

cd cslang/bin
bash cslang

Example: run the built-in print flow from the content pack.

run --f ../content/io/cloudslang/base/print/print_text.sl --i text=first_flow --cp ../content/

Example: use an integration-specific flow from the content repository after cloning cs-content.

run --f ../content/io/cloudslang/twilio/sms/send_sms.sl --i account_sid=<your_sid>,auth_token=<your_token>,from_number=<sender>,to_number=<recipient>,message=Hello --cp ../content/

In CloudSlang examples, these sections are command inputs that you replace with your own values:

--f   path to the flow file you want to run
--i   input values passed to the flow
--cp  classpath pointing at the content root

Example with placeholders shown explicitly:

run --f <path_to_flow.sl> --i input1=value1,input2=value2 --cp <content_root>

• Use cs-content to explore ready-made automations.
• Use cs-actions if you need Java-based integration logic.
• Use docs and cloudslang.io for platform documentation.

• cloud-slang: CloudSlang language, CLI, builder, compiler, runtime, and validation stack.
• score: The CloudSlang orchestration engine.
• cs-content: Ready-made CloudSlang flows and operations across many integrations.
• cs-actions: Java actions used by CloudSlang content packs.
• docs: Documentation source.
• CloudSlang.github.io: Website source.

We welcome external contributions, including first-time contributors.

• Start with Issues in the repository closest to your change.
• For orchestration content, start in cs-content.
• For Java-based integration logic, start in cs-actions.
• For core language, CLI, compiler, or runtime work, start in cloud-slang and score.
• For docs or onboarding improvements, use docs or CloudSlang.github.io.
• Please keep changes focused, include validation where possible, and follow each repository's CONTRIBUTING.md and DCO requirements.

• Website: cloudslang.io
• Documentation: CloudSlang docs
• Core platform: cloud-slang
• Engine: score
• Ready-made automations: cs-content
• Java actions: cs-actions
• Org repositories: CloudSlang repositories

Coffee, clean builds, reusable flows, and integration coverage tend to show up early and often.

You can do mighty things with the power of Markdown.