CoNote
BufferCoNote

Your Buffer post history, next to everything else that moved.

Buffer knows every post you’ve published — but it’s split across channels, where only the social team ever looks. CoNote logs each published post onto a shared timeline, beside the campaigns, deploys, and content changes from the same day.

Start your logbookSee how it works
Bufferpublished a change
Your timelineToday

Buffer post published to LinkedIn — “Our Q3 product update is live”

Buffer· 10:30

Newsletter “Summer drop” sent to 18,400 subscribers

Mailchimp· 11:00

Finding your history

Your Buffer post history: today, and from now on

The manual way · inside Buffer

Where to find it today

It’s all there — if you go channel by channel:

  1. 1

    Open Buffer and pick a channel

    Each connected channel — LinkedIn, X, Instagram, Facebook — keeps its own published history separately.

  2. 2

    Open the Sent / Published tab

    Switch from Queue to Sent to see what actually went out, with the text and the date for each post.

  3. 3

    Check Analytics for performance

    Open Analytics to see how a post did — but that’s engagement, not a record lined up with the rest of the company.

  4. 4

    Repeat for every channel and reconcile by hand

    More than one channel? Do it for each, then line the timestamps up yourself — nothing sits Buffer posts next to your campaigns or releases.

The CoNote way · one timeline

Where to find it from now on

Connect Buffer once. After that it’s seconds:

  1. 1

    Open your CoNote timeline

    Every published post is already there — across all channels, readable by anyone.

  2. 2

    Jump to the day it moved

    Scan the day engagement or traffic shifted; the post is stamped there with its channel.

  3. 3

    See it beside everything else

    The post sits next to that day’s email sends, ad changes, and deploys — the cause is obvious.

Start your logbook

Sound familiar?

Buffer’s history is perfect — for the social team.

#marketingThursday, 09:30
MR

Mara09:30

LinkedIn engagement doubled yesterday afternoon. Which post was it?
TB

Tom09:34

We schedule everything in Buffer, but there’s no shared record of what went out when.
MR

Mara09:37

So we’re scrolling Buffer trying to reverse-engineer the timing.

The post that drove it lives only in Buffer.

It answers “what did we post on this channel?” — never the question the rest of the company has: “what changed across every team around the day the number moved?”

  • One channel at a time — no single view across LinkedIn, X, Instagram, Facebook
  • Lives in Buffer, where the rest of the company never looks
  • Never lined up against the email send, ad change, or deploy from the same day
  • Built for scheduling and engagement, not a company-wide record of what shipped

With CoNote, the post is already on the timeline — “Buffer post published to LinkedIn” at 10:30 — sitting right beside the engagement spike, readable by anyone, on one page.

How it works

Connect once. Then it logs itself.

  1. 01

    Paste a Buffer API key

    Create a key in Buffer under Settings → API and paste it into CoNote — no webhook, no developer account.

  2. 02

    Every post logs itself

    CoNote checks Buffer every 30 minutes and logs each newly published post with a readable title and its channel.

  3. 03

    Read it in context

    The post sits beside that day’s email sends, ad changes, and deploys. When a metric moves, you scan one page instead of four tools.

What lands on your timeline

  • Every post Buffer publishes, across all your connected channels
  • The channel it went to and a preview of the text
  • A readable title like “Buffer post published to LinkedIn”

In your week

What teams actually use it for.

Side by side

Native history vs. your logbook.

See published posts

Buffer history

In Buffer

CoNote

On your timeline

One view across every channel

Buffer history

One channel at a time

CoNote

All channels in one place

Readable by the whole company

Buffer history

Needs a Buffer login

CoNote

Team-wide, plain language

Lined up against campaigns, deploys, config

Buffer history

Buffer only

CoNote

Side by side

Searchable with business context

Buffer history

Per-channel feeds

CoNote

Search and filter

Setup

Buffer history

Built in

CoNote

Paste a Buffer API key

On the timeline

The post in context.

A post on its own is a line in a feed. Next to the newsletter and the deploy from the same morning, it’s an explanation.

Thursday, June 11

  • Buffer post published to LinkedIn — “Our Q3 product update is live”

    Buffer· 10:30

  • Newsletter “Summer drop” sent to 18,400 subscribers

    Mailchimp· 11:00

  • Deployed storefront v2.4.0 (main → 3a7f2c1)

    GitHub· 09:41

Questions

Buffer post tracking, answered.

In Buffer, open a channel and switch from the Queue to the Sent (Published) tab to see what went out, with the text and date for each post. Analytics shows how each post performed. There’s one history per channel, so you check each one separately.

Buffer doesn’t send webhooks, so CoNote checks Buffer’s API every 30 minutes using a key you create in Buffer’s settings, and logs anything newly published.

No. You create an API key in Buffer under Settings → API and paste it into CoNote. There’s nothing to register or host.

Every channel connected to your Buffer organization — LinkedIn, X, Instagram, Facebook, and the rest. Each published post becomes a plain-language entry with the channel and a preview of the text.

No — only posts that actually publish. Drafts and still-scheduled posts stay off the timeline until they go out.

Buffer’s history lives in Buffer, one channel at a time, for the social team. CoNote puts every published post on a shared timeline next to campaigns, deploys, and config changes — so the whole team can line a post up against the day a metric moved.

Only your team. Every entry is scoped to your team, and connecting Buffer doesn’t expose your account to anyone outside it.

Keep digging

Track the rest of your stack.

Open the logbook.

Free plan, no card. The next time someone asks “what changed?”, the answer is one search away.

Start your logbook