> 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

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 %}

## Available entities

| Entity          | Description                                                   |
| --------------- | ------------------------------------------------------------- |
| Workspaces      | Top-level containers for all your Captain Data automations    |
| Workflows       | Automated sequences defining steps, integrations, and logic   |
| Jobs            | Individual executions of a workflow, with status and progress |
| Successful Jobs | Filtered view of jobs that completed without errors           |
| Job Results     | Final output data generated by completed jobs                 |


---

# 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 dynamically by asking a question.

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

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.