Support

Support

Boardfeed is supported by email, by the people who build it. Email support@boardfeed.co — the only address we publish, and the only channel there is: no phone line, no chat widget, no ticket portal to log into.

How quickly we answer

If this keeps happening, email support@boardfeed.co — a real person reads it and we usually reply within a few hours.

Every message gets a human reply, not only an autoresponder. Anything that blocks an import — the app down for your account, a scheduled import that has stopped running, a suspected data or security incident — is looked at first, before anything else in the queue. If the answer will take more than a day, the acknowledgement says what happens next and when.

What we support

  • Installing, uninstalling and re-authorising the app, and understanding the scopes it asks for.
  • Setting up a source, mapping columns, choosing an import mode.
  • Schedules, timezones, run-now, overlap protection and missed runs.
  • Reading the run history and the error CSV.
  • Questions about plans, trials and the limits of the free plan.
  • Reporting a suspected bug — and being told what we found.

What is not ours to support

  • Building your monday board, its columns or its automations, and cleaning up a source file.
  • Anything inside monday.com itself — account and plan billing, board permissions, seats. We will point you at the right monday.com support channel instead.
  • Sub-item imports, two-way sync, exports, and advertising sources behind their own OAuth review: these are not part of the current version. We log the request, and we do not promise a date.

What to include in a report

A report that carries these seven things is usually answered in one reply, without a round trip:

  1. Your monday.com account slug (the part before .monday.com in your URL) and the app version, shown at the bottom of the import view.
  2. The board name or id the import targets, and whether it is a scheduled run or a run-now.
  3. The date and time of the run, with your timezone — or “it has never run”.
  4. The source type (CSV or Excel upload, Google Sheet, JSON/REST endpoint, or the connected app) and the auth type.
  5. The exact error text, or a screenshot of the error panel. If the run produced an error CSV, attaching it is the fastest way for us to find the cause.
  6. What you expected to happen and what happened instead.
  7. Whether the same import works when you press “Run now”.

Please do not send API keys, tokens, passwords or full source files. If we need a sample, we will ask for the specific rows, or for a redacted copy. Security reports go to the same address and are handled under the same urgency rules.

Elsewhere on this site

This site describes a pre-launch product: anything labelled “planned” is on the roadmap and not available yet, and the monday.com marketplace listing opens at launch.