> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getcargo.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Captain Data

> Connect Captain Data to run automation workflows and scraping jobs in your pipelines.

## How to set up Captain Data

### Authentication

Captain Data requires API credentials:

1. Log in to your Captain Data account
2. Navigate to **Settings** → **API**
3. Obtain your credentials:
   * **API Key**
   * **Project UID**
4. Enter both in Cargo when connecting

## Captain Data actions

### Create job

Launch a Captain Data workflow with custom inputs.

**Required fields:**

* **Workflow**: Select the workflow to run

**Configuration:**

* **Inputs**: Map values to workflow input fields
* **Steps**: Configure accounts and parameters for each workflow step

**Use cases:**

* Trigger scraping jobs from Cargo workflows
* Run data extraction pipelines
* Execute multi-step automation workflows

### Cancel job

Stop a running Captain Data job.

**Required fields:**

* **UID**: The job UID to cancel

**Use case:** Cancel jobs that are no longer needed or taking too long.

### Retry job

Retry a failed Captain Data job.

**Required fields:**

* **UID**: The job UID to retry

**Use case:** Recover from transient failures without recreating the job.

### Find job

Get the status and results of a Captain Data job.

**Required fields:**

* **UID**: The job UID to retrieve

**Use case:** Check job completion status and retrieve results.

## Captain Data data models

### Fetch workflow results

Pull completed workflow results into Cargo.

**Required fields:**

* **Workflow**: Select the workflow to fetch results from
* **ID Column**: Define the unique identifier column

**Optional:**

* **Load jobs with warning**: Include results with warnings (default: no)

**Features:**

* Incremental sync
* 30-minute minimum sync interval
* Automatic retry on failures

## Best practices

* Use workflow presets for consistent configurations
* Monitor job status for large batch operations
* Configure appropriate accounts for each workflow step
* Use incremental fetch for workflow results
* Handle job failures with retry logic