> For the complete documentation index, see [llms.txt](https://docs.coupler.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coupler.io/sources/category/other/captain-data.md).

# Captain Data

Connect Captain Data workflows to Coupler.io to pull extraction results into Google Sheets, BigQuery, and analytics tools for monitoring automation performance.

Captain Data is a no-code automation platform that lets you extract, enrich, and sync data from sources like LinkedIn, Google, and other web platforms. It organizes work into workflows and jobs, making it easy to run large-scale data extraction pipelines without writing code. Connecting Captain Data to Coupler.io lets you pull your automation results into analytics tools, spreadsheets, or AI assistants for deeper analysis.

## Why connect Captain Data to Coupler.io?

* **Monitor your automation runs** — track job statuses, success rates, and output volumes across all your workflows in one place
* **Analyze extracted data** — send job results to Google Sheets, BigQuery, or Looker Studio to build reports on your scraped or enriched data
* **Combine multiple entities** — use Append or Join transformations to merge job results with workflow metadata for a complete picture
* **AI-powered insights** — route your Captain Data output to ChatGPT, Claude, or Gemini to summarize findings or generate follow-up actions

## Prerequisites

* An active Captain Data account with at least one workspace set up
* Your Captain Data API key (available in your account settings)
* At least one workflow with completed jobs to pull meaningful data

## Quick start

{% hint style="success" %}
Start with the **Job Results** entity if you want to analyze the actual data your workflows have extracted. Pair it with the **Successful Jobs** entity using a Join transformation to filter out failed runs automatically.
{% endhint %}

## How to connect

{% stepper %}
{% step %}
**Create a new data flow in Coupler.io.** Log in to Coupler.io and click **Add data flow**. Search for **Captain Data** and select it as your source.
{% endstep %}

{% step %}
**Enter your API key.** In Captain Data, go to your account settings and copy your API key. Paste it into the API key field in Coupler.io.
{% endstep %}

{% step %}
**Select an entity.** Choose what data you want to import — Workspaces, Workflows, Jobs, Successful Jobs, or Job Results.
{% endstep %}

{% step %}
**Choose a destination.** Select where you want your data to land — Google Sheets, Excel, BigQuery, Looker Studio, or an AI destination like Claude or ChatGPT.
{% endstep %}

{% step %}
**Run your data flow.** Click **Run** to execute a manual sync. Once it completes successfully, your data will appear in the destination you chose.
{% endstep %}
{% endstepper %}

## Captain Data 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

## Captain Data common issues

### Connection issues

<details>

<summary>My API key is rejected when connecting</summary>

Double-check that you copied the full API key from Captain Data with no trailing spaces. Keys are found in your Captain Data account settings under API access. If the key was recently regenerated, make sure you're using the latest version — old keys are invalidated immediately.

</details>

<details>

<summary>Coupler.io says it can't reach Captain Data</summary>

This usually means Captain Data's API is temporarily unavailable. Wait a few minutes and try running the data flow again. If the issue persists, check Captain Data's status page for any active incidents.

</details>

### Missing data

<details>

<summary>Job Results are empty even though my jobs completed</summary>

Job Results only appear after a job has fully finished processing. If you ran the data flow while a job was still in progress, the results may not have been written yet. Try running again after confirming the job status shows as completed in Captain Data.

</details>

<details>

<summary>I can see jobs but no data in the Job Results entity</summary>

Some workflows are configured to process data without storing explicit result records — for example, workflows that push data directly to an external destination. Check your workflow configuration in Captain Data to confirm it is set to store results.

</details>

<details>

<summary>Only some workflows or jobs appear in the sync</summary>

Coupler.io pulls data scoped to the API key you provided. If your key is tied to a specific workspace, only jobs and workflows within that workspace will be returned. Check whether you need a workspace-level or organization-level API key.

</details>

### Permission errors

<details>

<summary>I get a 403 Forbidden error when syncing</summary>

Your API key may not have sufficient permissions. Captain Data API keys can be scoped — make sure the key has read access to the entities you're trying to pull (workflows, jobs, results). Generate a new key with broader permissions if needed.

</details>

### Data discrepancies

<details>

<summary>The record count in Job Results doesn't match what Captain Data shows in the UI</summary>

Captain Data's UI may display aggregate counts that include records from retried or partial job runs. Coupler.io pulls the raw result records as stored by the API, which may differ slightly. Use the Job ID field to cross-reference specific runs if precision is critical.

</details>

### Rate limits

<details>

<summary>My sync fails with a rate limit error</summary>

Captain Data enforces API rate limits that vary by plan. If you're pulling large volumes of job results, try scheduling syncs during off-peak hours or reducing the frequency of runs. If you hit limits consistently, contact Captain Data support about your plan's API quota.

</details>

## Captain Data FAQ

<details>

<summary>What is the difference between Jobs and Successful Jobs?</summary>

The Jobs entity returns all job executions regardless of outcome — running, failed, completed. Successful Jobs is a filtered subset that only includes jobs that finished without errors. Use Successful Jobs when you want clean data for reporting, and Jobs when you need to audit failures or monitor active runs.

</details>

<details>

<summary>Why do my Job Results have different columns each time I sync?</summary>

Job Results fields are determined by what each workflow is configured to extract. A LinkedIn profile scraper will return different fields than a Google Maps extractor, for example. If you're syncing results from multiple workflow types, the columns will vary. Keep result syncs separated by workflow type to maintain consistent column structure.

</details>

<details>

<summary>Can I connect multiple Captain Data workspaces to Coupler.io?</summary>

Yes. Add each workspace as a separate source within your data flow, using the API key for each workspace. You can then use the Append transformation to combine data from multiple workspaces into a single destination, which is useful for agency reporting or multi-team setups.

</details>

<details>

<summary>Can I send Captain Data results to an AI tool for analysis?</summary>

Absolutely. Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Perplexity, Cursor, and OpenClaw. This is useful for summarizing large batches of extracted profiles, generating outreach copy from job results, or identifying patterns across workflow outputs.

</details>

<details>

<summary>My workflow ran successfully in Captain Data but I see no results in Coupler.io — why?</summary>

The most common reason is that the job was still processing when you ran the data flow. Job Results are only written after a job fully completes. Wait for the job status to show as completed in Captain Data, then trigger a new manual run in Coupler.io. Also verify your workflow is configured to store results rather than push them directly to an external system.

</details>

<details>

<summary>How do I find my Captain Data API key?</summary>

Log in to Captain Data and go to your account settings. Look for an API or Integrations section — your API key will be listed there. If you don't see one, you may need to generate a new key. Copy the full key and paste it into the API key field when setting up your Coupler.io data flow.

</details>

{% hint style="info" %}
For details on what fields each entity returns, see the [Data Overview](#captain-data-data-overview) article. If you're hitting connection or sync errors, check [Common Issues](#captain-data-common-issues) for troubleshooting steps.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.coupler.io/sources/category/other/captain-data.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
