INTEGRATIONS / WORK ALREADY HAS A HOME
Can You Just does not have to replace the systems where your work already lives.
Your team may manage requests in a project system, tickets in a service desk or work in an internal application. CYJ adds a capacity-aware plan: who or what can do the work, when they are available and what changes when another request arrives.
Connector reads bring source information into CYJ. Supported outbound operations, such as an authored Monday.com update, are separate actions. A revised forecast is not automatically written into the source system.
Source title, description and business status give the work context. CYJ’s estimates, resource assignments, dependencies, priorities and deadlines determine its scheduling consequences. Importing work does not make an external due date an instruction to invent capacity.
For Monday.com, newly discovered sub-items remain suggestions until reviewed. Accepted work uses the ordinary stage workflow. Floating requests to another person likewise consume no capacity until that recipient accepts them.
Refresh updates cached source facts; it is different from accepting new work or sending an update. Active externally linked execution also checks source freshness. When the source cannot be checked, CYJ retains cached context and reports the problem rather than quietly claiming that it is current.
Read and write capabilities vary by connector and connection. There is no blanket promise of two-way synchronisation across every field.
CYJ uses a provider-based connection model, so additional work-management systems can connect without changing the scheduling model. This page focuses on the verified Monday.com workflow and the assigned-worker API; it is not a roadmap of promised connectors.
Custom software can participate through the operations the API actually exposes. It does not currently offer general project creation, team administration or a complete schedule export.
Building an assigned worker? Read the API v1 developer documentation →