> 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/faq.md).
# FAQ
What is the difference between Jobs and Successful Jobs?
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.
Why do my Job Results have different columns each time I sync?
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.
Can I connect multiple Captain Data workspaces to Coupler.io?
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.
Can I send Captain Data results to an AI tool for analysis?
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.
My workflow ran successfully in Captain Data but I see no results in Coupler.io — why?
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.
How do I find my Captain Data API key?
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.
{% hint style="info" %}
For details on what fields each entity returns, see the [Data Overview](/sources/category/other/captain-data/data-overview.md) article. If you're hitting connection or sync errors, check [Common Issues](/sources/category/other/captain-data/common-issues.md) 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 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/faq.md?ask=&goal=
```
`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.