# Data Overview

Captain Data exposes five entities through Coupler.io, covering everything from your workspace setup down to the raw results produced by individual automation runs. This gives you full visibility into how your workflows are performing and what data they're generating.

## Entities

| Entity          | What it contains                                                |
| --------------- | --------------------------------------------------------------- |
| Workspaces      | Workspace name, ID, configuration, and membership details       |
| Workflows       | Workflow definitions, steps, integrations, and automation logic |
| Jobs            | Job executions tied to workflows — status, timestamps, progress |
| Successful Jobs | Subset of jobs that completed without errors                    |
| Job Results     | Actual output records produced by a completed job               |

## Available fields

#### Workspaces

| Field        | Description                              |
| ------------ | ---------------------------------------- |
| Workspace ID | Unique identifier for the workspace      |
| Name         | Display name of the workspace            |
| Created at   | Timestamp when the workspace was created |
| Members      | Users associated with the workspace      |

#### Workflows

| Field       | Description                                         |
| ----------- | --------------------------------------------------- |
| Workflow ID | Unique identifier for the workflow                  |
| Name        | Human-readable workflow name                        |
| Status      | Whether the workflow is active, paused, or archived |
| Steps       | Sequence of actions configured in the workflow      |
| Created at  | When the workflow was created                       |
| Updated at  | Last modification timestamp                         |

#### Jobs

| Field             | Description                                     |
| ----------------- | ----------------------------------------------- |
| Job ID            | Unique identifier for the job execution         |
| Workflow ID       | Which workflow triggered this job               |
| Status            | Current state: running, completed, failed, etc. |
| Started at        | Timestamp when the job began                    |
| Finished at       | Timestamp when the job ended                    |
| Records processed | Number of records handled by this job           |
| Error message     | Details if the job failed                       |

#### Successful Jobs

| Field             | Description                              |
| ----------------- | ---------------------------------------- |
| Job ID            | Unique identifier for the successful job |
| Workflow ID       | Workflow that produced this job          |
| Finished at       | When the job completed successfully      |
| Records processed | Output volume for this run               |

#### Job Results

| Field       | Description                                                |
| ----------- | ---------------------------------------------------------- |
| Result ID   | Unique identifier for the result record                    |
| Job ID      | Job that generated this result                             |
| Data fields | The actual extracted or enriched data (varies by workflow) |
| Created at  | When the result record was written                         |

## Common field combinations

* **Jobs + Job Results** (Join on Job ID) — link execution metadata to actual output data
* **Workflows + Jobs** (Join on Workflow ID) — see how each workflow performs across multiple runs
* **Successful Jobs across multiple workspaces** (Append) — consolidate results from different teams or clients into one report

## Use cases by role

{% tabs %}
{% tab title="Growth & Sales" %}

* Track how many leads or profiles were extracted per workflow run
* Monitor which LinkedIn or Google scraping workflows are producing the most results
* Send Job Results directly to ChatGPT or Claude to auto-generate outreach summaries
  {% endtab %}

{% tab title="Operations" %}

* Build a dashboard showing job success rates and failure trends over time
* Use the Jobs entity to spot workflows that are frequently failing or taking too long
* Append job data across workspaces to get a global view of automation health
  {% endtab %}

{% tab title="Agencies & Consultants" %}

* Pull Job Results per client workspace and push to separate Google Sheets tabs
* Use the Workspaces entity to automate client reporting across multiple accounts
* Aggregate record volumes by workflow to report on deliverables to clients
  {% endtab %}
  {% endtabs %}

## Platform-specific notes

* Job Results fields vary depending on what each workflow is configured to extract — there is no fixed schema across all workflows
* The Successful Jobs entity is a filtered view and does not include jobs that are still running or have failed
* Workspaces are the top-level scope — all workflows and jobs belong to a specific workspace
* Captain Data rate limits may apply when pulling large volumes of job results; see Common Issues for details