> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/buffer.md).

# Buffer

Read scheduled and published social posts, channel performance metrics, and content ideas from your Buffer account.

## What It Enables

| Tool               | Capability | Description                                                    |
| ------------------ | ---------- | -------------------------------------------------------------- |
| `get_account`      | `read`     | Get the Buffer account and its organizations                   |
| `list_channels`    | `read`     | List connected social channels with service and queue state    |
| `list_posts`       | `read`     | List drafts, scheduled, sent, or errored posts across channels |
| `get_post`         | `read`     | Get one post with full text and per-post performance metrics   |
| `get_post_metrics` | `read`     | Get aggregate post performance over a date range               |
| `list_ideas`       | `read`     | List saved content ideas from the Buffer idea board            |

All tools are read-only. This connector does not schedule or publish posts.

## Setup

**Required:** Buffer personal API key

**Where to find it:** [publish.buffer.com/settings/api](https://publish.buffer.com/settings/api)

1. In the Notara dashboard, go to **Tools**.
2. Click the **Buffer** tile.
3. In Buffer, go to **Settings → API** and generate a personal API key.
4. Paste the key into the credential field and click **Verify & Save**.

Your API key is encrypted at rest with AES-256-GCM.

## Example Prompts

> "What posts are scheduled for this week across all channels?"

> "How did our LinkedIn posts perform last month — impressions and reactions?"

> "Show me the content ideas saved in Buffer."


---

# 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://notara.gitbook.io/notara-docs/connectors/buffer.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.