Zoost - workbench for Zoho CRM

Zoost turns your Zoho CRM org into a local, version-controllable, searchable codebase - and then draws you a map of it. If you administer or develop on Zoho CRM you know the gaps: no external editor, no Git, no way to search across all your functions at once, no way to see what calls what before you change something, and no quick answer to "what is the API name of that related list?", and no way to tell which functions still use a given connection. Zoost fills them, with no server and no account: everything it reads lands on your own disk. The single exception is the optional AI assistant, which stays off until you enter your own API key - described in full below. WHAT IT DOES - A window of its own. Zoost opens from the toolbar icon, or with Alt+Shift+Z, as an ordinary resizable window you can move to a second monitor and leave beside Zoho. It comes back the size and in the place you left it. The call graph, the ER diagram and the settings are views inside that one window, not extra browser windows. - Judge it before you give it access to anything. "+ Sample" writes a workspace of invented data into your working folder - a couple of hundred Deluge functions with real call chains, modules with lookups, workflows, schedules, blueprints and connections - so you can open the tree, the graph, the audit and the exports without a Zoho tab and without an account. It is generated, never fetched, everything that would talk to Zoho is disabled for it, and it is deleted like any other workspace. - Local mirror, and Git if you want it. Zoho CRM's own version history covers a function, one at a time. Everything else the pull captures - module schema, layouts, related lists, workflows, schedules, blueprints, connections, and what Zoho reports as failing - arrives on your disk as plain files, so with Git it gets a history too, and one diff answers what changed across every kind at once. Deluge functions are plain .dg files; Java, Python and Node functions keep every file in a project folder, with a .meta.json sidecar for each function. Git is optional: without it the mirror is still ordinary files you can search and hand over. Functions and project files removed in Zoho are pruned locally on the next pull, so the folder stays a faithful mirror rather than an accumulating pile. - Search across every function at once. Full-text search over all mirrored Deluge, Java, Python and Node files, literal or regular expression - the closest thing to grep for Zoho CRM, and something the platform does not offer. Find every reference to a field, a module, an endpoint or a hardcoded id before you change it. Named patterns - an email address, Zoho's 18-digit record id, and any you add - are one click away and yours to manage. - Auto-sync on save. Save a function in the native Zoho editor and the matching local file updates by itself, so your working copy always mirrors production. - Reference graph. For any function: which functions call it (the impact if you change it) and which it calls (its dependencies) - as a searchable explorer and as a visual node-link diagram. Calls to custom functions are clickable in the code preview: jump to the definition and back. - Reverse usage. Where each function is actually wired across the org - blueprint, button, schedule and so on - read from Zoho's own signal, with no expensive scans. - Module schema, fields, layouts and pipelines - each pipeline's stages in order, with the outcome, probability and forecast category, plus the stages the module keeps on no pipeline. Every field with type, lookup target, picklist values, mandatory flag and the workflow rules it starts, the ones that check it and the ones that write it. A layout matrix shows, per field, which layouts it belongs to and where it is required - and flags fields that are on no layout at all. - Relations, with the names you actually need. The API name of a related list is not the api name of either module, and it is what zoho.crm.getRelatedRecords() requires. Zoost catalogues every relation with its target module, the lookup or linking module behind it, and the Deluge call ready to copy. - ER diagram that stays readable. Modules as tables, foreign keys as arrows. Focus a module, adjust depth, walk the graph by clicking. A relation-first mode pushes modules into the background and brings relation names forward. Click an arc to isolate one relation and fade everything else. Boxes can be dragged: the automatic layout is a starting point, and what you arrange is what the PDF prints. Live sliders for spacing, spread, label gap and label size, an all-modules scope, and Save PDF for wall-size prints. - Fits the access you actually have. Not every Zoho user may read Deluge or the connections catalogue, and no API says so in advance - so Zoost finds out by asking, once, and records the answer with the date. An area your role is refused is skipped on later pulls, nothing is written for it, and its tab is removed rather than sitting there greyed out; the reason is in Settings, which can also re-check, since roles change. You can hide and reorder the tabs yourself too, and choose which types Pull all should ask for at all. - Every part knows when it was last read. Because a type can be excluded from a pull, the mirror states per area when it last came from Zoho. A report section whose data is behind is unticked in the export dialog, with the date and the reason - you can include it anyway, and the report then says so. Both reports carry the per-area dates whether or not anything is behind. - Automation map. Workflows with triggers, criteria, instant and time-based actions and the functions they invoke; schedules with frequency, status and target function; blueprints with the module and the field each runs on, the states a record moves through, and what each transition does - the field an update writes, the function it calls. Rules with actions that run after a delay carry the count and the delay, a filter shows only thos…