Skip to main content

monday.com

Fancified

monday.com for fancy-flow — as four imported, versioned packages, one per runtime. Not vendored source: a copy cannot be upgraded, and third-party APIs change.

Runtime Package Install
Authoring surface (every host) @particle-academy/monday-ui npm install @particle-academy/monday-ui
Node @particle-academy/monday-js npm install @particle-academy/monday-js
PHP 8.4+ particle-academy/monday-php composer require particle-academy/monday-php
Python 3.11+ fancy-monday pip install fancy-monday

The ui package is the editor surface and is React on every host — a PHP or Python project installs it and its own runtime package, and never the js one.

What it costs you

One dependency: @particle-academy/fancy-connector-core (or particle-academy/fancy-connector-core on Composer), which the js and php packages pull in themselves. The Python package has zero runtime dependencies.

No monday.com SDK. Plain HTTP, deliberately: a vendor SDK is third-party code subject to the kit's full approval bar, and one per provider is hundreds of dependencies nobody is tracking.

Setting it up

Everything below is generated from provider/manifest.json, so it cannot disagree with what the packages do.

Credentials

A monday.com connection holds 1 value.

Every value here is account scope: one per connected account, not one per installation.

Field Scope Secret Where it comes from
API token per connected account secret From monday.com: your avatar -> Developers -> My Access Tokens. It carries YOUR permissions and every board you can see, so a personal token grants an automation everything you have.

The estate

monday.com has no test estate, and somebody checked. Everything this connector does is real. Use the faker to build against it.

monday has no test estate. A developer plan is a real account with real boards, so anything an action creates is created for real. The faker is the only safe way to develop against this connector, which is why every action ships with one.

What it can do

Actions

item_create — monday.com item

Create an item on a monday.com board.

POST /v2 · unsafe to replay — a retried durable run does it TWICE

Input Required What it is
boardId yes The numeric id in the board URL: monday.com/boards/1234567890.
itemName yes What the item is called on the board.
groupId no Which group on the board to create it in. Left empty, monday uses the board's default group.
columnValues no Column id to value, e.g. status -> Done. Which values a column accepts depends on its type.

Run it before you have credentials

Every operation ships a faker, whether or not monday.com has a sandbox. Set a node's mode to fake and it returns the shape monday.com actually publishes — the same field names, deterministically — so you can wire the downstream nodes before touching an account, a key, or a network.

This repository is generated

provider/ is the source. Everything under packages/ is emitted from it and must not be hand-edited — CI regenerates and diffs on every push, and the next protocol sync destroys anything it finds. See AGENTS.md.

Two namespaces, which do not match on purpose

The repo is github.com/Fancy-Friends/monday; the packages publish under particle-academy. Nothing derives one from the other — the names come from weaver's friends.json and nowhere else.

Licence

MIT.

Metadata

Release files for fancy-monday 0.4.1

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for fancy-monday 0.4.1
File Size Uploaded Provenance Actions
fancy_monday-0.4.1.tar.gz 23.0 kB Without provenance Details for fancy_monday-0.4.1.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for fancy-monday 0.4.1
File Interpreter ABI Platform Actions
fancy_monday-0.4.1-py3-none-any.whl Python 3 none any Details for fancy_monday-0.4.1-py3-none-any.whl

Total release size: 43.4 kB

Release files / fancy_monday-0.4.1.tar.gz

Download URL fancy_monday-0.4.1.tar.gz
Size 23.0 kB
Tags Source
SHA-256 checksum
How to use checksums
8e81e0c52f7ef191834c2de31950e66680a09b41b5a6c5475e3a171e559e988f
BLAKE2b-256 checksum
How to use checksums
5e12a726a5c486a8ec9f4c67710211a217624f5c5cf95727875233055e48a638
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Release files / fancy_monday-0.4.1-py3-none-any.whl

Download URL fancy_monday-0.4.1-py3-none-any.whl
Size 20.4 kB
Tags Python 3
SHA-256 checksum
How to use checksums
ac0b3015e35279e6de7af4b9fb05efbc29d060e68b5992adbf331209539d86a7
BLAKE2b-256 checksum
How to use checksums
c2915f575c4dbf72b68286028492dc126ad3c6da6810eec9bfec34fcdc7f1675
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.13.18

Security for fancy-monday 0.4.1

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page