# FAQ

<details>

<summary>Can I pull data from multiple Blogger blogs in one data flow?</summary>

Each Blogger source connection is tied to a single Blog ID, so you'll need to add multiple sources within the same data flow — one per blog. Then use the **Append** transformation to merge all the data into a single output. This works well for combining posts or comments across several blogs into one reporting table.

</details>

<details>

<summary>Where do I find my Blog ID?</summary>

Your Blog ID is a long numeric string. You can find it in two places:

* In your **Blogger dashboard**, go to Settings > Basic — it's listed under "Blog ID"
* In the URL when you're in the Blogger admin panel: look for the number that appears after `blogID=` or as part of the path like `/blog/posts/XXXXXXXXXX`

Don't use your blog's public URL or Blogspot address — those won't work.

</details>

<details>

<summary>Why can't I see my draft or scheduled posts?</summary>

The Blogger API v3 only returns published posts when using an API key. Draft, scheduled, and private posts require OAuth-level access, which is not supported in the current Blogger source configuration. Only live, public posts will appear in your data flow.

</details>

<details>

<summary>How often can I refresh Blogger data?</summary>

You can schedule refreshes as frequently as your Coupler.io plan allows. However, the Blogger API has a default quota of 10,000 requests per day per Google Cloud project. If you're running frequent refreshes across multiple entities and multiple blogs, monitor your quota in the Google Cloud Console to avoid hitting the limit.

</details>

<details>

<summary>Can I use Blogger data with AI tools like ChatGPT or Claude?</summary>

Yes — Coupler.io supports AI destinations including ChatGPT, Claude, Gemini, Cursor, Perplexity, and OpenClaw. You can route your Blogger post content directly to these tools for tasks like summarization, content classification, SEO metadata generation, or drafting follow-up content. Keep in mind that post content arrives as raw HTML, so prompt your AI tool accordingly.

</details>

<details>

<summary>Can I join Posts with Comments in Coupler.io?</summary>

Yes. Add both Posts and Comments as separate sources in the same data flow, then use the **Join** transformation to connect them on the `post.id` field (from Comments) and `id` field (from Posts). This gives you a combined view of each post alongside its comments — useful for engagement analysis or moderation workflows.

</details>

<details>

<summary>The comment count in my Posts export doesn't match what I see in the Comments entity — why?</summary>

The `replies.totalItems` field in the Posts entity is a cached count from post metadata and includes all comment statuses (live, spam, pending). The Comments entity returns individual records and may differ slightly depending on which statuses the API exposes. For accurate, filterable comment data, rely on the Comments entity rather than the count field in Posts.

</details>

{% hint style="info" %}
For a full breakdown of available fields per entity, see the [Data Overview](https://docs.coupler.io/sources/category/social-media/blogger/data-overview) page. For connection errors or missing data, check [Common Issues](https://docs.coupler.io/sources/category/social-media/blogger/common-issues).
{% endhint %}