> For the complete documentation index, see [llms.txt](https://motivlabs.gitbook.io/impulse-dev-manual/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://motivlabs.gitbook.io/impulse-dev-manual/services/pipeliner.md).

# Pipeliner

The **Pipeliner** service primarily job y to allow the user to pipeline Jobs and run them either in parallel and/or after a previous set of jobs finished. 

This allows you to create many jobs to sync all your content types, and run all the jobs by starting a pipeline rather than running every single job. Effectively, "pipelines" are a collection of "steps" and "steps" are a collection of "jobs." 

**Responsibility 1:** Allows the user to create a "Pipeline" of jobs.

**Responsibility 2:** To execute a Pipeline, meaning, to execute each of the sync jobs configured within the Pipeline. A pipeline will run all the steps in order. When a step is run, all the jobs in a step will be run at one time.