Node Templates

// Publishes a customer PowerPoint master (.pptx or .potx from Drive) as this workspace's layout library. Extracts every layout with its slots, capacities and theme, applies the curator's layout curation, renders each layout's background through document-render, and outputs the library handle, the enabled layouts as a compact text list for choosing each slide's layout, the catalog, the master normalized to .pptx, and the background and thumbnail images. A deck in this workspace wires Library, Master and Backgrounds straight to its slide nodes; a deck elsewhere reads the library through a Layout Library. The library is this node's latest completed run; a failed run keeps the previous one. One Brand Master per workspace.

// Translates one Drive document into another language keeping its page layout (columns, tables, figures) and returns a translated PDF, a bilingual PDF for review (each original page beside its translation, on by default), and a report. Word, PowerPoint and text uploads are translated from the PDF Drive made of them, so they also come back as a PDF, never as an editable file. The run succeeds only when every passage is translated and the result passes the checks for leftover untranslated text and changed numbers; otherwise it fails with a clear message naming the problem and the pages, and returns no PDF. An optional Style says in your own words how the translation should read (formal, plain language, technical). Scanned PDFs (no text layer) are refused. Text inside pictures is not translated. For a text-only reading copy, use the Drive Translate menu instead. To keep the result in Drive, connect it to Save File.

// Generates a single presentation slide from text content and an instruction. Connect multiple Slide Generator outputs to a Presentation Composer to build a full presentation.

// Turns a designed deck into a PowerPoint master for a brand: every slide of the Presentation Composer's deck becomes one slide layout, its look as the layout background and its title, text, lists, picture, table and slide number as placeholders that keep the slide's fonts, sizes and colours; a preview deck, one slide per layout with its sample text, shows the master as PowerPoint draws it. Design the slides with Slide Generators in layout design mode (a layout name on each), then save the master to Drive and select it in a Brand Master to publish it as a layout library.

// Turns one document into images, one per page, to show, check or pass on page by page. Connect ONE source: a PDF; a PowerPoint (.pptx), drawn by LibreOffice (fonts can differ slightly from PowerPoint, hidden slides are left out); an image (PNG, JPEG, WebP, GIF), passed through as it is; or the Presentation Composer's HTML deck. Width sets how wide each page image is (the height follows the page); Max Pages caps how many pages become images; Pages reports how many pages the source has. For a picture of a 3D model, use 3D Snapshot instead.

// Collects multiple inputs into an ordered array. Add items dynamically and drag to reorder. Carries files through when item ports receive image/video/audio outputs.

// Synthesizes an answer from multiple document chunks using an LLM. Connect one or more Document Chunk nodes to the context port.

// THE node for 'how is X connected to Y?' (Start X, To Y) and 'what is related to X?' (Start X alone): explained paths through the ontology, each hop cited to its source passage; it can also walk a typed chain of hops. Emits a synthesizer-ready summaryText; wire Start from Merge Ranked Lists' topId and summaryText into a Knowledge Synthesizer's context. Start and To take an entity's NAME only, as the documents write it and never translated ('现金流风险' stays '现金流风险'): the kind the user names goes in Start Type / To Type ('lo strumento AI' is Start 'AI', Start Type 'AI tool'; 'AI (AI_Model)' is Start 'AI', Start Type 'AI_Model'). A result shows 2 paths unless Max Paths raises it (up to 5). Query (advanced) replaces every field, Start included.

// Walk typed links out of, into, or both directions from an ontology object and return the connected sub-graph.

// Collect the tasks every Plan review produced into one ordered, de-duplicated list. Several reviews wire into its one Tasks input; it drops the duplicates four lenses inevitably raise, sorts by priority then by lens, and emits both the JSON a Task node is built from and the markdown checklist a design doc carries.

// Run one of gstack's plan reviews — spec (office-hours), ceo, design, eng or devex — over a plan, using the passes that review actually runs. Returns findings, the tasks they imply, what is out of scope, what already exists, and its open decisions already shaped as requestUserDecision questions. The workspace agent asks those in the chat, appends the answers to the Decisions node wired into this review, and reruns it to apply them.

// Read a GitHub repository at a branch and map it against a request or a plan: which conventions apply, what already exists for each part of it (with paths), what does not exist yet, and where it touches shared code — plus facts written by code: the branch's commits beyond its base, the pull requests open into it, and the checks the repository can run. Reads the convention files and the files a model picks; a small repository is read whole. Wire its map into every Plan review so their findings are grounded in real code.