Entries marked 🆕 are new in the 13/10/2026 staging version and are not in the released version of Voltask yet.
Actions
Actions are a type of Connector block that control, in an external service, what that service is going to do (e.g. Send an email). Instead of going through the interface of that service, Voltask controls it through its API. Actions are the opposite of the other type of Connector blocks, triggers, which watch what can happen in an external service (e.g. A row changes in a spreadsheet).
Insights 🆕
🆕 New (13/10/2026, not in production yet). The Insights page (shown as "Analyse" in French; link in the top bar of the My projects page) sums up the executions of your organization over the last 7 or 30 days: number of executions, successes, failure rate, durations, credits used, executions per day, most active projects and projects that fail the most. See the guide "The Insights page".
API
Application Programming Interface. It is a way to control a service or piece of software with code. Each feature of the software must be described in the documentation of the API to be controllable. Some software is very rich in features, which can be complex. A clear, well-documented API shows that the creator of the software wants developers to be able to use it without its interface. And thanks to Voltask, this power is in everyone's hands.
To set up 🆕
🆕 New (13/10/2026, not in production yet). The "To set up" list of the editor gathers what keeps a project from running: for example a connector block with no connection chosen. Each item names the block concerned. The AI assistant connected to the MCP bridge can read it too.
Blocks
Voltask projects are graphs made of blocks that form a logical tree. Each block is a piece of code that follows a standard allowing blocks to be connected to each other. Blocks can be System blocks (internal logic) or Plug-in blocks (external connection).
Credits
Credits correspond to executions of connectors and let you monitor the data exchanges within your logical scenarios. Each time a flow passes through a connector block, it uses one credit. When you create a Voltask account, you have an initial number of credits. You can also ask for extra credits via this form (coming soon).
Paths of the executions 🆕
🆕 New (13/10/2026, not in production yet). A diagram on the Insights page that shows, for one project, which blocks its executions go through. Each band goes from one block to the next, and the wider it is, the more executions went that way. The red part is the part that failed on arrival at the block: it shows where your scenario breaks. Dashed bands are loops.
Comment
A comment is a note you place wherever you like on the graph. Switch to comment mode (the bubble icon in the toolbar, or ⇧C) then click the graph, or right-click and choose Add a comment. You can give it a title (optional) and write the text in Markdown, with the Write and Preview tabs and a toolbar for formatting. Click the note to see its full content in the right-hand panel (also called the inspector), where you can pick its color and text size, resize it, reply in a thread, and edit or delete a reply. Resolve removes the comment from the list of open comments (the All, Open, Resolved filter brings it back). 🆕 New (13/10/2026, not in production yet). Markdown text, the title, the color, the size and resizing are new. See the guide "The editor".
Connectors
Connectors (or plugins) are external services that Voltask can control. The list of supported connectors keeps growing.
Controls
Controls are logic blocks that steer the flow of a graph scenario towards one block or another. For example, a Condition control block steers the flow to its True output if the condition is met, False if it is not. Pauses and repetitions are other examples of controls.
Copy, paste and duplicate 🆕
🆕 New (13/10/2026, not in production yet). In the editor, you can copy blocks (with the links between them and their labels) and paste them under the pointer, in the same project or in another one, with ⌘C and ⌘V (Mac) or Ctrl+C and Ctrl+V (Windows/Linux). ⌘D or Ctrl+D duplicates the selected blocks. The right-click menu also offers Copy, Duplicate and Paste. In read-only mode, pasting is refused.
Triggers
Triggers are a type of Connector block that control, in an external service, the watching of what happens in that service (e.g. Receive an email). Instead of going through the interface of that service, Voltask controls it through its API. Triggers are the opposite of the other type of Connector blocks, actions, which control what the external service can do (e.g. Add a row to a spreadsheet).
Label 🆕
🆕 New (13/10/2026, not in production yet). A label is a colour and a name that you give to a block (right-click the block, then "Label…"). The block is then outlined in the colour of its label, which helps you spot at a glance the blocks that belong together.
Executions
Executions are the tracking of the information passed through each Connector (or plugin) block. They are gathered in the right-hand panel called the inspector, reachable by clicking the journal icon 📄. They are sorted by initial trigger (for example a Webhook, Receive an email...). You can see the number of credits used, shown with the ⚡ symbol. By clicking the initial trigger, you see whether the passages succeeded or hit an error, the date and time of triggering, the number of blocks in the scenario, the total time and the number of credits used. By clicking each passage you can see the details of the blocks the flow went through, and the data that went through the input and output points, which lets you monitor and improve your logical scenario. 🆕 New (13/10/2026, not in production yet). The Insights page complements this tracking project by project with figures over 7 or 30 days and the diagram of the paths of the executions.
Expression
Expression blocks let you create operations and structure data in Voltask. For example, adding 2 values, or converting an object (a set of juxtaposed values that often defines a row in a spreadsheet) into JSON format (a way of writing that sends many values as text).
Format
The Format block lets you define a custom text where the elements between {{singletons}} are recognised as unknowns that can be linked to other data.
Simple format (voltask-flow) 🆕
🆕 New (13/10/2026, not in production yet). A small JSON file that describes a scenario: the blocks, the flow links, the data links, the values and notes, without positions. It is produced with "Export (simple format)" in the project menu and imported with New, then Import. It is handy for writing a template by hand or having an AI write it. Connections (accounts, keys) are never part of it. See the guide "The simple voltask-flow format".
Flow
The Flow is the visual path that runs through the scenario or graph of a Voltask project. It can stop on an error (then shown in the execution journal) or be redirected by control blocks (such as Condition).
Graph
A graph or scenario is, in a Voltask project, the big board in the centre of the interface that gathers the blocks and comments representing the logic of the data operations you want to carry out.
Group 🆕
🆕 New (13/10/2026, not in production yet). A group gathers several blocks under a title and a colour, to tidy a large graph. You can name the group, choose its colour, select all its blocks at once, take a block out of the group or ungroup.
JSON
JSON lets a computer store several pieces of information in a structured way as simple text, like a customer's order for example. Example: { "client": "Marie Dupont", "article": "Pull rouge", "taille": "M", "prix": 30 } In this example, the words between quotes ("client", "article", etc.) are keywords that indicate the type of information. The words or numbers after the colons are the values of that information. JSON is the preferred sending format of webhooks. Data can be received and turned into objects that have output points you can link visually on the graph to other input points. Likewise, objects can be turned into JSON to be sent through webhook returns or HTTP requests.
JSON schema
A JSON Schema is like a plan that describes the structure of JSON data. It makes sure the data is consistent and avoids errors by stating the expected format. Some blocks, like the fromJSON block, need the expected JSON schema. You can get it easily by running a first scenario, analysing the executions and copying the JSON received from a webhook, then pasting it into the site Transform.tools, copying the JSON Schema from there and pasting it into the fromJSON block, then running the scenario a second time.
Copy link 🆕
🆕 New (13/10/2026, not in production yet). An address that lets another person signed in to Voltask see one of your projects in read-only mode and copy it into their own projects. You create it with "Share a copy..." in the project menu, with a validity period and a number of allowed copies, and you can revoke it at any time. Your connections and comments never follow. See the guide "Versions and copy links".
LLM
Large Language Models are files of several GB that condense phenomenal amounts of text (and images for multimodal LLMs) on which they were trained to model concepts according to how close they are, represented by probability weights (e.g. the words Stock and Inventory will have close weights). Open Source and proprietary models are often offered as API access, like ChatGPT from OpenAI, or La Plateforme from Mistral. Indeed LLMs are very demanding in computing resources and need powerful computers to run. For sovereignty and data encapsulation needs, Open Source models like Mistral's can be downloaded and run locally with Voltask.
MCP (MCP bridge) 🆕
🆕 New (13/10/2026, not in production yet). MCP (Model Context Protocol) is a standard that lets an AI use tools. The Voltask MCP bridge (voltask-mcp) gives an assistant such as Claude Desktop or Claude Code what it needs to read and build a scenario: list projects, add and connect blocks, set parameters, run an execution and read its result. It acts with the rights of the person whose session it uses. See the guide "The MCP bridge".
Navigation mode
There are 2 navigation modes in Voltask: Selection mode, shown as a mouse cursor, lets you use your mouse to draw a selection rectangle around blocks for example. Move mode, shown as a hand icon, lets you move around the graph by holding the left mouse button and moving the mouse. In Selection mode, as long as you hold Space, you are in Move mode. When you release Space, you go back to Selection mode.
Object
Objects are like product sheets in code. For example, a product reference has: Information (properties): Name: "Super Product" Quantity: 20 units Price: €4 In Voltask, objects are shown visually as a list of input or output points.
Organization
Organizations in Voltask are defined by a secret organization key (to be made unique and complex and not shared) and all the associated projects.
Input points
Input points are a way to bring data into a block. The data that enters them is called params. They are linked to output points of other blocks.
Output point
Output points are a way to send data out of a block. The data that leaves them is called returns. They are linked to input points of other blocks.
Project
Voltask projects are made of graphs, access keys to outside services, and the execution journal of the connectors' data. Projects are listed on the home page of an organization and are available to all its members.
Scenario
Synonym of graph.
Sub-project 🆕
🆕 New (13/10/2026, not in production yet). A Voltask project that another project calls like a block, so that you do not copy the same blocks everywhere. It has its own executions. See the guide "Sub-projects".
Variable (of the project) 🆕
🆕 New (13/10/2026, not in production yet). A variable is a named value that the blocks of a project can read and change during an execution (a total, a current customer). It has a type (text, number, true or false, object or list) and an initial value. It can start again from its initial value at each execution, or be kept from one execution to the next (a counter, the last date seen). Variables are managed in "Variables of the project", in the project menu.
Version 🆕
🆕 New (13/10/2026, not in production yet). A version is a named snapshot of a project (its blocks, links, comments, labels, groups and variables), saved with a note from "Versions…" in the project menu. You can restore a version to go back; Voltask first saves the current state as an automatic version. See the guide "Versions and copy links".
Webhook
A webhook is a system for receiving text information that comes from another application such as Celestory, for example. This information can be simple text or represent objects as JSON, for example. The return of a webhook is another piece of text information that can be sent back to the sending application.
Write
The Write block at the end of a scenario with a Webhook trigger lets you write a piece of data and a Status code of the operation in the Webhook's response.