Skip to main content
Buffer is a social media management platform used to plan, schedule and publish posts on Instagram, Facebook, LinkedIn, X (Twitter), TikTok, YouTube, Threads, Pinterest, Bluesky and other networks, and to track how those posts perform. This connector reads your Buffer workspaces (organizations), their connected channels, every post (sent, scheduled, drafts, awaiting approval and failed) with its performance metrics, plus tags, ideas and content items.

Configuring Buffer as a Source

In the Sources tab, click on the “Add source” button located on the top right of your screen. Then, select the Buffer option from the list of connectors. Click Next and you’ll be prompted to add your access.

1. Add account access

The connector uses a personal API key of your Buffer account.
  1. Log in to Buffer with the account whose data you want to bring.
  2. Go to Settings > API (publish.buffer.com/settings/api) and create a new API key.
  3. Copy the key and paste it in Nekt.
The following configurations are available:
  • API Key: (Required) The personal API key you created. It reads every organization and channel of your Buffer account, including post metrics.
  • Start Date: (Optional) Only posts created or scheduled on or after this date are read. Leave it empty to read every post Buffer keeps.
  • Organization IDs: (Optional) IDs of the Buffer organizations to read. Leave it empty to read every organization the API key can access. If you enter an ID the key cannot access, the run fails and lists the organizations it can access.
Post metrics are only available with a personal API key. Keys and AI assistants connected to the same Buffer account share one request limit (see API Limits & Performance).
Once you’re done, click Next.

2. Select streams

Choose which data streams you want to sync. For faster extractions, select only the streams that are relevant to your analysis.
Tip: The stream can be found more easily by typing its name.
Select the streams and click Next.

3. Configure data streams

Customize how you want your data to appear in your catalog. Select the desired layer where the data will be placed, a folder to organize it inside the layer, a name for each table (which will effectively contain the fetched data) and the type of sync.
  • Layer: choose between the existing layers on your catalog. This is where you will find your new extracted tables as the extraction runs successfully.
  • Folder: a folder can be created inside the selected layer to group all tables being created from this new data source.
  • Table name: we suggest a name, but feel free to customize it. You have the option to add a prefix to all tables at once and make this process faster!
  • Sync Type: every Buffer stream is FULL_TABLE: each extraction reads the current state of the data, so post status changes, metric updates and deletions made in Buffer show up in your tables.
Once you are done configuring, click Next.

4. Configure data source

Describe your data source for easy identification within your organization, not exceeding 140 characters. To define your Trigger, consider how often you want data to be extracted from this source. Buffer refreshes post metrics once a day, so a daily extraction is usually enough. Optionally, you can configure Delta Log Retention and determine for how long we should store old states of this table as it gets updated. Read more about this resource here. Once you are ready, click Next to finalize the setup.

5. Check your new source

You can view your new source on the Sources page. If needed, manually trigger the source extraction by clicking on the arrow button. Once executed, your data will appear in your Catalog.
For you to be able to see it on your Catalog, you need at least one successful source run.

Streams and Fields

Available streams

The table below lists every stream, its slug (the exact identifier to pass when creating the source via API), a short description and the Buffer data it needs. Every table has an organization_id column. If the API key cannot read posts or ideas, the tables of that area are skipped (the run log says which ones) and the other tables keep syncing.

Fields by stream

One row per Buffer organization (workspace) the API key reads.
One row per connected channel. Join posts.channel_id to channels.id.
One row per post. Metric columns are filled for sent posts once Buffer has collected them from the network (up to about 24 hours after publishing, then refreshed daily). A metric the network does not report is empty, not 0. Every reported metric is also in the metrics JSON column.
One row per tag. Posts, ideas and content items list their tags in tag_ids.
One row per content item: either a channel-less draft, or the set of channel posts created from it (post_ids).
One row per idea.
One row per idea group (column of the ideas board). Primary key: organization_id + id.

Implementation Notes

Data Quality Considerations

  • Every table is rebuilt on each sync (FULL_TABLE), so status changes (scheduled to sent), metric refreshes and deletions in Buffer are reflected.
  • Buffer deletes sent and failed posts, with their media, two years after they go out. Those posts then leave the posts table too; keep your own copy (for example with History) if you need a longer history.
  • Buffer refreshes post metrics once a day; metrics_updated_at says when a post’s metrics were last refreshed.
  • Metrics are normalized across networks: metric_reactions holds Instagram and X likes, metric_reposts holds retweets, Mastodon reblogs and Threads reposts. On Facebook, metric_likes is the Like reaction only and metric_reactions is every reaction type.
  • metric_engagement_rate is a percentage (0 to 100).
  • When Start Date is set, posts created before it but scheduled after it are still read.
  • Posts are read in order of creation. Buffer does not report the total number of posts, so after the first run compare the number of posts per channel and status with the Buffer app; if they differ, contact Nekt support.

API Limits & Performance

  • Buffer limits API requests per account, shared by every API key and AI assistant connected to it, in three windows: 15 minutes, 24 hours and 30 days. The limits depend on your Buffer plan (Free: 150 per 15 minutes and 600 per day; Essentials: 450 and 1,800; Team: 1,500 and 6,000).
  • A sync uses about one request per 100 posts, tags, ideas and content items of each organization, plus two per organization for channels and idea groups.
  • When the 15-minute window is nearly used up, the sync pauses until it resets, leaving room for your other Buffer tools.
  • The sync never uses the last 10% of the daily or 30-day limit: when only that is left, or when what is left is not enough to read the next table whole, the run stops (tables not read keep their previous data) and the next run after the reset syncs normally. This keeps your other Buffer tools and AI assistants working.

Troubleshooting

Skills for agents

Download Buffer skills file

Buffer connector documentation as plain markdown, for use in AI agent contexts.