Import guide
Import Facebook Page posts into monday.com on a schedule
A Page’s own reporting answers "how did last month go", not "which posts worked, and are they on the board the content team actually reads". Getting them there by hand means copying numbers out of Facebook’s insights screen into a tracker, which is a snapshot with no history.
Boardfeed reads one Page’s posts on a schedule and writes one item per post into a monday.com board: the message, the type of post, its permanent link, its picture and its like, comment and share counts. The credential is not a key you paste: you connect the Meta account that manages the Page, and Boardfeed reads through it.
Last checked : the nine columns one row holds, the window, the page ceiling and the 100-posts-a-request limit, read off the connector — whose endpoints are marked unverified in docs/connectors.md § Facebook Page posts until the Meta app exists, and this page repeats that position rather than claiming more
Doing it by hand, every time
- Open the Page’s posts, one at a time, and copy the numbers out.
- Paste them into the board and give every post a key by hand.
- Do it again next week, and work out which posts are new.
- Notice that the counts you copied last week have moved since.
The scheduled route
- Connect the Meta account that manages the Page. Boardfeed opens Meta’s own consent screen in a small window, asks for **read-only** access to the Pages you manage, and stores the connection encrypted (AES-256-GCM). No token reaches the board, the browser or a log, and you can revoke the account from the Support tab at any time.
- Choose the Page from the list Boardfeed reads back — the Pages that account manages — and choose how many days back to read. Left empty it is the last 90 days, counted back from the moment the run starts.
- Key the import on the post id and run it in **update matching items** mode: a fresh run then updates the row it already wrote rather than adding a second copy. The counts of a post move after it is published, and an upsert is what keeps the board matching the Page. In create mode, running the same window twice is two sets of items — that is the mode, not a bug.
- Read the value check before you save. On a remote source the check covers the rows it previewed, and the run checks the rest as it writes them — the screen says so rather than implying the whole window was read.
- Every run reads the posts of the window, 100 a request, and stops rather than importing part of the Page if the source answers more than 200 requests of them.
Field mapping notes for Facebook Page 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 nine fields: `id`, `created_time`, `message`, `status_type`, `permalink_url`, `full_picture`, `likes`, `comments` and `shares`. Nothing is renamed and nothing is computed.
- `likes` and `comments` are the totals Facebook reports for the post, and `shares` is how many times it was shared. A post nobody shared, or one Facebook answered without a total, arrives **empty** rather than as a zero — so an empty cell on the board means "Facebook did not say", not "none".
- `status_type` is Facebook’s own word for what the post is — `added_photos`, `published_story`, `status_update` and the rest — so map it to a text column, or to a status column and let the mapping create the labels it has not seen.
- `created_time` arrives in the form Facebook writes it (`2026-09-18T08:15:00+0000`) and maps to a date column as it comes, time zone included.
- `permalink_url` is the post’s permanent address, which is what a board wants beside the numbers — a Link column shows it as something people can click. `full_picture` is the URL of the post’s image, and it is Facebook’s own address for it rather than a copy Boardfeed keeps.
- A Page returns roughly 600 posts a year, so a 90-day window is a few dozen rows and a year is a few hundred: this is a source you can read whole rather than sample.
Facebook Page posts import questions
Do I need a Facebook app or a developer account for this?
No. You connect the Meta account that manages the Page, from the source dialog, and Meta asks that account whether Boardfeed may read its Pages — read-only, and nothing else. There is no key to create, paste or rotate.
Which Pages can I import?
The ones the connected account manages, which is what Boardfeed reads back and shows in the dialog. It is the Page that is read, not the personal profile behind the account, and a Page the account does not manage is refused by name before anything is written.
How far back does a run read, and how much is there?
The last 90 days by default, and whatever you set beyond that. Facebook reports roughly 600 posts a year on a Page, so a full year is a short import — but note that the window is counted back from the moment each run starts, so a scheduled import reads the same window again every time and it is the match column that keeps it from duplicating items.
Does Boardfeed write anything back to Facebook?
No. The permission it asks for is read-only, and the connector only reads: the posts of one Page, a page at a time, with no writes of any kind. It never posts, comments, likes or deletes, and it cannot see your Pages’ messages or their settings.
Why do a post’s numbers change after I imported them?
Because a post keeps being liked, commented on and shared after the run that imported it. Boardfeed reads whatever Facebook 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.
What happens if the connected account is revoked or expires?
The next run fails with a sentence naming the account, and it is recorded in the run history like any other source error — nothing is written to the board. Reconnect the account from the source dialog and run it again. Disconnecting an account in the Support tab names the imports that read it before it revokes anything.