FAQ

Which CircleCI plan do I need to use this integration?

Coupler.io works with any CircleCI plan that provides API access, including the Free plan. However, some data — like advanced Insights metrics — may only be available on Performance or Scale plans depending on your CircleCI subscription.

Where do I find my Project ID?

Go to your CircleCI project settings. The Project ID appears in the URL: https://app.circleci.com/settings/project/circleci/ORG_SLUG/PROJECT_ID. Copy the UUID at the end and paste it into the Project ID parameter in Coupler.io.

Can I pull data from multiple CircleCI projects in one data flow?

Yes. Add multiple sources to a single data flow — one per project — and use the Append transformation to combine them into one unified table at the destination. This is useful for cross-project pipeline dashboards.

Do I need to set a workflow ID or job number?

For most entities, these are optional. If you don't provide a job number, Coupler.io will attempt to auto-fetch it from the Workflow jobs entity. Workflow IDs are only required if you want to scope data to specific workflows — otherwise, pipeline-level entities return data across all workflows.

Why does the Contexts entity return a permission error?

Context data in CircleCI is typically restricted to organization admins. If your API token belongs to a non-admin user, you'll see a 403 error. You'll need an org admin to generate the token or grant your account elevated permissions. See the Common Issues article for more detail.

Can I send CircleCI data to an AI tool like ChatGPT or Claude?

Yes. When setting up your data flow destination, select one of the available AI destinations — ChatGPT, Claude, Gemini, Perplexity, Cursor, or OpenClaw. This lets you feed pipeline metrics, failure trends, or insights data directly into an AI assistant for automated analysis or reporting.

How far back can I pull historical pipeline data?

This depends on your CircleCI plan's data retention policy. CircleCI limits how far back the API returns records, so very old pipelines may not be available regardless of the start date you configure. For best results, set a start date within your plan's retention window.

What's the difference between Jobs and Workflow jobs?

Workflow jobs returns all jobs associated with a specific workflow run. Jobs is a more targeted entity that fetches data for a specific job number. In most cases, start with Workflow jobs to get an overview, then use Jobs if you need detailed data for a particular job.

For details on what fields each entity returns, see the Data Overview article. For connection problems or empty results, check Common Issues.