@bijection/connectors/monday entrypoint to declare monday.com resources.
Availability
This page describes the pinned source package. Published availability is unestablished for this artifact. Source build and package availability.Resources and modes
Declare a resource in application code, then bind deployment-specific settings and credentials. See typed resources, connections and source inspection.
Board items
pull: Active items of one board
The following example matches configurationstandard.
Inferred record types
Inferred record types
Configuration: standard
Case:monday/items/pull/standard.
Connection and resource configuration are declared by this exact case.
Credential kind: monday. Keep credential material in the private credential inventory.
Complete configuration contract
Complete configuration contract
Complete native profile
Complete native profile
Commands, occurrences and artifacts
Commands, occurrences and artifacts
Hosted qualification: unestablished for this catalog configuration. Installed connections report their own identity, authority and current status.
Provider guidance
Compiled declaration examples and configuration details are published in the connector reference. Read-only board items over captured GraphQL (POST https://api.monday.com/v2).
Every request pins API-Version: 2026-07; without the header monday answers with
whatever version it currently calls Current.
Bind setup { board: "<board id>" } and monday.credential("MONDAY_TOKEN"). A
personal API token goes RAW in Authorization, with no Bearer; configure it as
a raw-authorization credential envelope. The host writes the header; nothing in
this package does. Identity is the token’s account (me.account.id).
items.pull reads boards(ids: [$board]) { items_page(limit: 500, cursor: $cursor) }
and follows items_page.cursor until it is null. The board is the first (only)
element of the boards list; the native contract indexes it as
data.boards.0.items_page, and an empty list (unknown or invisible board) refuses
the page. monday documents that a cursor expires 60 minutes after the first
request, so a walk interrupted for longer cannot resume and refuses.
Each record is id, name, state, created_at, updated_at and group.id.
items_page returns active items only. The reference types updated_at as a
nullable Date with no documented format, so it is published as a value, not as
a record version: no version and no coverage are claimed. Column values are not
selected: ColumnValue is an interface over more than 32 typed values and
ColumnType has more than 32 values, beyond the captured profile’s bound.
Nothing is withdrawn. An item archived or deleted leaves items_page and simply
stops being observed. A point read through the root items(ids:) query returning
state (archived, deleted) could withdraw on provider evidence; it is not
declared because the reference does not say which states items returns.
Rate-limit errors (COMPLEXITY_BUDGET_EXHAUSTED, minute, concurrency and IP
limits) answer HTTP 429 with Retry-After; 429 is a declared transient failure
and the connection backs off on Retry-After up to 300 s. The complexity budget
(points per minute per token, 5,000,000 points per query) and the daily call
limit are not declared as a connection budget: a query’s cost is known only from
monday’s complexity field, which is not selected.
No write is declared: monday’s change_column_value takes no precondition.
The schema is a reviewed projection transcribed from the published reference, not
retrieved by introspection. Regenerate with
BIJECTION_GRAPHQL_EXECUTABLE=/path/to/bijection-graphql node dev/graphql-codegen.mjs monday
(--check compares). Nothing here has run against monday.com or been qualified.
Provider references
Provider references and prerequisites are maintained in the connector guidance above. No separate provider-documentation review date is recorded.Source and evidence
Canonical connector source, native analysis and check receipts. Connector artifact:905888ea276a2a28e36981a79e8142b2547ea451c3e63162cb6915ad4a7d1305.
The resource declaration examples above are compiled and compared with exact catalog declarations. Recorded checks apply only to their source, declaration and runtime identities. Configure a connection and inspect its status to establish deployment-specific readiness.