Setup guide

How to use Boardfeed

Boardfeed takes a file, a published sheet or an API endpoint and writes it into a monday.com board on a schedule. This page is the whole setup, from installing the app to reading the first run's errors.

Boardfeed runs as a view inside the board you are importing into: everything below happens in that view, without leaving monday.com.

Before you install

  • A monday.com account where you can install apps. Installing, authorising and uninstalling Boardfeed is an account-admin action; a board owner who is not an account admin can use the board view afterwards, but cannot install the app.
  • The scopes you approve at install: read and write the boards you point the import at (boards:read, boards:write), and read the account's own identity (me:read, account:read). Nothing else is requested, and you can revoke the app from your monday.com account settings at any time.
  • A source. A CSV or Excel file you can upload, a published Google Sheet, a CSV or Excel file kept in SharePoint or OneDrive, a JSON/REST endpoint, or a key — or a connected account — from the app the data lives in. An uploaded file runs manually: a schedule needs a source Boardfeed can fetch on its own, which is why a file in a drive is a source of its own rather than an upload (see Your first schedule).
  • A board with the columns you want filled. The mapping step offers the board's existing columns; a column Boardfeed cannot write to is left unmapped rather than guessed at.

Install Boardfeed

  1. In monday.com, open the marketplace (the Apps icon in the left panel, then Marketplace) and search for Boardfeed: Scheduled Import. If an account admin was given a share link — the auth.monday.com link from the app's Share tab — that link installs the same app.
  2. Press Install, choose the account and the board permission you want to grant, and approve the consent screen. It lists exactly the scopes in the section above.
  3. Open the board you want to import into. Boardfeed: Scheduled Import appears under Add view in the board's view tabs; open it as Import.
  4. That is the install done. If the view does not appear, reload the board and check that the app was installed on this account rather than on another one you are signed in to.

Your first import

The import view is a five-step wizard. Each step below is the heading you will see on screen; nothing is written to the board until you press the run button in step 5.

1. Choose a source

Upload a CSV or an Excel file (one sheet, up to the file-size limit shown next to the picker), or paste the URL of a published Google Sheet or a JSON/REST endpoint. Boardfeed reads the source, detects the delimiter and the encoding, and shows the first rows back. Nothing is stored beyond the preview until you save the import; an uploaded file is deleted seven days after it was stored.

2. Choose the fields

Check that the source was read the way you expect: the header row, the number of columns and the preview rows. If a column is in the wrong place or the header was not detected, fix the source or set the header row, and go back to step 1 — it is cheaper now than after an import.

3. Map the columns

Match each source column to a monday column. Boardfeed detects the type of every field (text, long text, numbers, date, status, dropdown, email, link, phone, checkbox or people) and offers the board's columns of that type; you confirm or change each one. A source column you do not want to import is left unmapped. The same 20-row preview is shown underneath, so you can see what will be written before you write it.

Screenshot to add: apps/site/public/screenshots/mapping-with-detected-types.png

The mapping step: source columns on the left, monday columns on the right, the detected type of each column, and the 20-row preview underneath

Map once — the type of every column is detected for you.

4. Check the values

Boardfeed checks every row against the board's own column settings before anything is written: a status value that is not on the board's list, a date it cannot read, a number that is not a number in any format, a missing or duplicated key when you are matching rows by a key. Each problem is listed with its source row number, the column and the reason, and the rows that are fine stay importable — a broken row never blocks the others.

Screenshot to add: apps/site/public/screenshots/row-errors-before-the-run.png

The error list above the run button: three rows to fix, each with its source row number, the mapped column and the reason

Every broken row is listed before the import runs.

5. Save the import and run it now

Choose how rows land — create only, upsert by a key column, or update only — give the import a name, and press Run now for the first run. The run is written up as a run record: how many rows were created, updated, skipped and left out, and how long it took. Saving the import is what makes it appear in the run history on this board.

Your first schedule

A schedule needs a source Boardfeed can fetch on its own: a URL, a published Google Sheet, or a connected app. Uploaded files run manually — the file is deleted seven days after it was stored, so a schedule on it would stop working on its own.

  • Manual is the default: nothing runs until you press Run now.
  • Hourly, daily, weekly, or a cron expression — a daily import at 07:00 means the board is up to date before the standup starts, not after someone re-uploads a file.
  • Pick a time and a timezone and check the next-run time the schedule panel shows under the control. Daylight-saving changes follow the timezone, not the clock time you typed.
  • Overlap protection is on. An import never has two runs in flight: if a run is still going when the next occurrence is due, that occurrence is skipped rather than started, so the same source is never read twice at once, and the occurrence after it runs on the schedule as normal. Saving a schedule change recomputes the next run time from that moment; a run already in flight is left alone and finishes.

Rows that disappear from the source

A scheduled import keeps a board in step with a file or an API, and the day a row stops being in the source it is usually because somebody deleted it there. Boardfeed will not archive or delete the item for you — that is your call, and it is not reversible. What it can do, if you ask it to, is say so on the board: an upsert import can carry a label such as Gone from source in a status column you pick, and the item wears that label until its row comes back.

  • Off by default. You switch it on per import, in the advanced settings, and choose the status column and the label. The column you mark with cannot also be a column this import writes rows into — the next row would overwrite the label.
  • Only after a clean run. The label is written only when a run imported everything: no failed rows, no rows it never reached, and not the first run of an import (nothing has been imported yet, so the whole board would look "missing"). The source also has to come back with at least 80 % of the previous run's rows, so a truncated export or a changed filter is treated as a short read rather than as hundreds of rows disappearing.
  • It undoes itself. When the row is back in the source, the next run removes the label and restores what the column held before — Boardfeed remembers the previous value when it marks. Nothing is archived and nothing is deleted.
  • You can see it before it happens. With the marking switched on, the row check in step 4 says how many items the run would label, or which rule would stop it. Nothing is written while you look.

Where the errors show up

  • Before a run, in step 4 of the wizard: the rows to fix, with the reason, and the good rows still importable.
  • In the run history, on the same board view: one line per run with its counts (created, updated, skipped, failed) and its duration. Open a run to see the rows that failed, one line per row with the same reason the wizard showed; a run that left rows out also mails them to the report address as a CSV attachment. A run that failed rows also offers Re-import failed rows: it runs the same import again and writes only the rows that failed in that run, once you have fixed them in your source. The rows it writes are the only ones it counts against your monthly allowance. It is offered for a source Boardfeed can find those rows in again — a file, or a source with a match column. A file has to be the same file, because the rows are found by their row numbers.
  • By e-mail, to the person who installed the app: when a run finishes with rows left out, the first few failed rows are in the message and the complete list is attached as a CSV. Repeated failures of the same import are folded into one summary rather than one e-mail per run. Nothing is written for a row that was left out, so the board stays consistent — the data is simply not all there yet.

Run history retention depends on the plan: 7 days on Free, 90 days on Solo and Team.

Support

Anything on this page that does not match what you see, or any error whose message does not tell you what to change: email support@boardfeed.co. If this keeps happening, email support@boardfeed.co — a real person reads it and we usually reply within a few hours. The scope of that support, and what to include in a report, is on the support page of this site.

Please do not send us API keys, tokens or passwords. If you need to show us a sample of your data, redact the rows you send.