Boardfeed

Import guide

Import Instagram posts into monday.com on a schedule

The people who plan content live in monday.com, and the numbers that tell them whether it worked live in Instagram. The join between the two is usually a screenshot, or somebody re-typing a like count into a board on Friday afternoon.

Boardfeed reads one Instagram account’s posts on a schedule and writes one item per post into a monday.com board: the caption, what kind of post it is, its permalink and its likes, comments and views. The account is not something you find by name — it is the Instagram account behind a Facebook Page you manage, and Boardfeed reads it through that Page.

Last checked : the eleven columns one row holds, the window, the page ceiling and the 10,000-media ceiling, read off the connector — whose endpoints are marked unverified in docs/connectors.md § Instagram posts until the Meta app exists, and this page repeats that position rather than claiming more

Doing it by hand, every time

  1. Open Instagram, and copy the numbers off each post.
  2. Paste them into the board and match them up with the rows from last week.
  3. Realise that a post whose engagement is still climbing has been frozen at the number you copied.
  4. Repeat weekly, for every account the team runs.

The scheduled route

  1. Connect the Meta account that manages the Page whose Instagram account you want. Boardfeed opens Meta’s own consent screen in a small window, asks for **read-only** access, and stores the connection encrypted (AES-256-GCM). Instagram is read through the Page, so this is the same connection a Facebook Page posts import would use — one account, several sources.
  2. Choose the Page. The list Boardfeed reads back names each Page and, beside it, the Instagram account behind it (`Instagram: 1784…`), so you can see which Pages have one before you choose. A Page without an Instagram account is refused **by name** when the run starts, rather than importing nothing quietly.
  3. Choose how many days back to read. Left empty it is the last 90 days, counted back from the moment the run starts. Instagram keeps the 10,000 most recently created posts of an account, so a long window is answered with those rather than refusing.
  4. Key the import on the post id and run it in **update matching items** mode: a fresh run updates the row it already wrote instead of adding a second copy. Likes, comments and views keep moving after a post is published, and an upsert is what keeps the board matching Instagram.
  5. Read the value check before you save. Every run reads the posts of the window, 100 a request, and stops rather than importing part of the account if the source answers more than 200 requests of them.

Field mapping notes for Instagram posts

This is the part that decides whether an import works on the first try. Everything below is handled in the mapping step, before the first run.

  • One row is one post, and it has eleven fields: `id`, `timestamp`, `media_type`, `media_product_type`, `caption`, `permalink`, `media_url`, `like_count`, `comments_count`, `view_count` and `username`.
  • `media_type` is one of `IMAGE`, `VIDEO` or `CAROUSEL_ALBUM` and `media_product_type` says where the post lives — `FEED`, `REELS`, `STORY` and the rest — so a board that wants to compare formats has both, and neither is renamed.
  • A video post carries a `view_count` and an image post does not, so the column is empty on the rows where Instagram has no such number. A caption is empty on a post that never had one. Neither is a zero invented for the board.
  • `media_url` is the address of the image or video file, and it is Instagram’s own address for it — one that expires after a while. It suits a Link column or a build step that copies the file; it is not a file Boardfeed keeps. `permalink` is the post’s permanent address and is the one to put on the board beside the numbers.
  • `timestamp` arrives in the form Instagram writes it (`2026-09-17T12:30:00+0000`) and maps to a date column as it comes, time zone included.
  • The account id is not a column: a board with `username` on it identifies the account from the post itself, which is what the run read.

Instagram posts import questions

Why do I choose a Facebook Page to import Instagram?

Because that is how Instagram’s business API is reached: an Instagram account reads through the Facebook Page behind it, and the permission Boardfeed is granted is a permission on that Page. It also means there is one account to connect rather than two, and nothing to keep in step.

Which Instagram accounts can I import?

The Instagram accounts behind the Pages the connected Meta account manages. Boardfeed reads the Pages back and names the Instagram account beside each one, so a Page without one is visible before you choose it — and a Page that has none is refused by name when a run starts.

How far back can a run read?

Instagram keeps the 10,000 most recently created posts of an account, and a run reads the window you set — 90 days by default — as far back as those cover. A window longer than the account’s history reads what there is.

Does Boardfeed need an Instagram login, or my password?

No. There is no Instagram password anywhere in this product and no Instagram login to perform: the connection is a Meta account, the consent screen is Meta’s own, and the permission is read-only.

Why do the like and view counts change after I imported them?

Because a post keeps being seen after the run that imported it. Boardfeed reads whatever Instagram reports at the moment the run starts; an import keyed on the post id, in update mode, is what keeps the board in step rather than frozen at the day it was first read.

Does Boardfeed read stories, comments or the people who engaged?

No. This connector reads the media of one Instagram account — its posts, reels and carousels — and nothing else: no story archive, no comment text, and no list of the accounts that liked or commented. Import what you need as its own board and relate the two there.

Other sources