Kord for Monday

Kord is version control for engineering document sets. It already knows which revision of a drawing is current, who still owes an approval, and which transmittal a document went out on. Monday knows what the project owes, to whom, and by when. Linking a board to a Kord project puts both halves on one row.

One owner per column

This is the rule the whole integration is built on, and it is why there is nothing here that can loop, echo, or overwrite someone mid-sentence. Every column you map flows one way only:

• Kord pushes what Kord computes. Status, current revision, a link to the file, a link to the review session, review progress ("2 of 3 approved"), the latest transmittal number and its date, and the archive of earlier transmittals. Nobody types these on either side, so Kord writes them and never reads them back.
• The board keeps what people type. Document number, assignee, due date, and any custom column of your own. Kord shows the value on its Documents dashboard and will not let anyone edit it there - that cell is typed on the board, and the dashboard says so.

You can flip any non-derived column the other way, so a team whose planning lives in Kord mirrors outwards instead. What you cannot do is make one bidirectional - which is the point. There is no merge rule to reason about, no "newer timestamp wins", and no conflict dialog, because two owners for one cell is the situation that produces all three.

Mapping the columns

Kord links a board you already have - it never creates one, and it never adds columns you did not ask for. The mapping screen is your board's columns on the left, Kord's fields on the right, and you draw a line between the two. The side you start the line on is the side that owns the value. A fresh connection starts with nothing mapped; map the three columns you care about and leave the rest out of the sync entirely.

While you are holding a column, the cards on the far side that cannot take it go dim - a status column will not land on a text field, and a derived field will not accept a line drawn towards Kord. There is a Match by name button if your titles already line up, but it only ever runs when you press it.

Connecting Monday

1. Install the Kord app into your Monday account from its share link. Unlike the Egnyte, Procore and Autodesk connections, there is no app registration for an administrator to create and no client credentials to paste - Kord runs the app.
2. Each member clicks Sign in with Monday and authenticates on Monday's own site. Kord never sees a Monday password, and the Monday account has to carry the same email address as the Kord account, so one person cannot quietly act as another.
3. Pick the board, pick the Kord project, and draw the column mappings. Kord imports the board once and the two sides are in step from then on.

How sync behaves

A change on either side reaches the other in seconds. A board edit arrives as a signed webhook; a Kord change - a published revision, a reviewer approving, a transmittal going out - schedules a reconcile immediately. A five-minute background pass is the backstop for a webhook Monday never delivered, so a missed event costs you five minutes rather than a support ticket. There is also a Sync now button when you want to watch it happen.

Sync is a reconcile rather than a stream: each run reads the board's own columns, then writes Kord's own. Because the two halves never touch the same cell, a run that dies halfway through resumes rather than replays, and Kord's own writes cannot come back as inbound changes.

Security

• OAuth 2.1 with PKCE, scoped to boards, updates, users and webhooks. Access tokens last about an hour and the refresh token rotates on every use, so a leaked token is stale almost immediately.
• Tokens encrypted at rest with AES-256-GCM. Any member can disconnect their own Monday sign-in; an admin can remove the integration for the whole organization, which unregisters the webhooks and drops the board links with it.
• Inbound webhooks are verified, not trusted. Kord checks the signature on every delivery and then re-fetches the item from Monday rather than believing the values in the payload.
• Every write is attributed. A change that came from the board is logged as such in Kord's audit trail, with the Monday user who made it - so an ISO 9001 record still answers "who changed this" across both systems.

Requirements

A Monday account and a Kord organization on the Team or Enterprise plan. The Documents dashboard itself is on every plan - it is wiring it into your planning tool that is the paid part.

Want to see it on one of your own boards? Email support@withkord.com or book a demo below - we'll map the first three columns with you.