Boardfeed

Import guide

Import a REST API into monday.com on a schedule

When the data you need lives behind an API, the usual answer is a developer and a cron job. That works until the developer leaves, the token rotates, or the endpoint starts paginating differently.

Boardfeed points at an HTTP endpoint, reads the JSON it returns, and writes the records into a monday.com board on a schedule — with the auth header, the JSON path and the pagination rule configured once in the UI.

Doing it by hand, every time

  1. Write a script that calls the endpoint and handles the API’s own pagination.
  2. Normalise the JSON into one row per record, flattening whatever nesting the payload uses.
  3. Post the rows to monday.com in batches, inside the account’s rate limits.
  4. Re-run it on a timer somewhere, and find out it broke when someone notices the board is stale.

The scheduled route

  1. Enter the endpoint URL and the authentication: none, basic, bearer token or an API-key header.
  2. Give the JSON path to the array of records (for example data.items) and pick the fields to map.
  3. Choose how the API pages — page number, offset, or a cursor returned in the response.
  4. Schedule the run. Boardfeed backs off and retries when the endpoint rate-limits or monday.com returns a complexity error.

Field mapping notes for REST API

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

  • Authentication: credentials are stored encrypted at rest (AES-256-GCM) and never written to logs. Header names and value prefixes are configurable, because every API spells "Bearer" differently.
  • Pagination: page-number and offset styles are configured with the parameter names the API expects; cursor pagination reads the cursor from a path in the previous response.
  • Nested objects: a record like { "customer": { "name": "…" } } is referenced by path (customer.name) rather than being flattened for you. Arrays of values map to a dropdown or a text column.
  • Types: ISO-8601 timestamps map to a date column; Unix timestamps in seconds or milliseconds are converted; amounts returned in minor units (cents) should be divided by 100 in the mapping.
  • Limits: Boardfeed only issues GET requests, and respects the source API’s rate limits with backoff between pages.

REST API import questions

Do I need to write code?
No. The endpoint, auth, JSON path, field mapping and schedule are configured in the app. The only thing you need from the API’s documentation is which URL returns the records and how it pages.
What happens when the API is down during a scheduled run?
The run is retried with backoff. If it still fails, the run is recorded as failed with the HTTP status and you get an email — you are not left guessing why the board stopped updating.
Can one API feed several boards?
Yes. The same source can be mapped to different boards on different schedules.

Other sources