# Job Depot

The Job Depot stores all possible Sync jobs. Currently, in Impulse Jobs need to be defined before they can be used.\
A Job example would be providing a number of Sources and a Number of Destinations. The Job can be Manual or Automatic as described under the terms. In addition to this, each Source/Destination has its own detail (JSON) which the Taxis will use to figure out what to get.\
The detail can and must likely be different for each Content Repo as it is specific to interact with the Content Repo’s APIs.\
This is how Impulse deals with Folders being different or queries and content being different between systems.&#x20;

**Responsibility 1:** The job detail is responsible for storing the Job and populating to pass along any requested Job through the Sync Process.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://motivlabs.gitbook.io/impulse-dev-manual/services/job-depot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
