🔌 Data and Connectivity

One of the historical limits of "No-Code" is lock-in: you build a gorgeous interface, but the moment you need to plug it into your company's information system (CRM, databases, marketing e-mail campaigns), you hit a wall. 🧱
Celestory's architecture blows that limit apart thanks to an API-First, connector-native philosophy. Your graph is not an isolated island: it is an exchange hub able to talk to the cloud in real time. 🌐

1. ☁️ The Age of Decentralised Data (Going "Headless")

In classic software for building games or interactive experiences, the texts are written, the images stored and the character logic defined hard-coded inside the editor. If you need to fix a typo or change a product price, you have to reopen the authoring tool, edit, and re-publish the whole application. 😩
Celestory lets you design what is called a "Headless" architecture (the body and the brain are kept separate). 🧠

🧩 The Role of the Native Connectors (Airtable, Baserow)

Celestory Creator ships specialised blocks to query (read, create, update, delete) the most popular databases on the market, without ever having to write an HTTP request or juggle convoluted API headers. You give the table and column identifiers, and Celestory pulls the content out. 🪄

• Content Management Kept Elsewhere: you can author every single dialogue line of a corporate serious game in a Baserow grid (an open-source database you can also self-host) or in Airtable. 📊
• Hot Reloading: a translator fixes a line in Airtable? The next player sees the correction immediately when they launch the Celestory module. The experience is always up to date, with no re-compilation. 🔥

2. 🌍 A Studio Wired to the World (Webhooks & APIs)

If your company uses a tool that does not have an official connector yet (Hubspot, Notion, an in-house ERP…), no problem. The editor is built to talk to anything. 🤝

💻 Client Side (The Frontend)

The visual part (your compiled Celestory module) has blocks such as:

• Voltask Webhook, Make and Zapier blocks: trigger remote automations straight from your application. The player fills in a form at the end of a module? These blocks capture the answers and send them to Make or Zapier to generate a PDF, an e-mail or a Slack alert in a fraction of a second. ⚡
• HTTP Request block: for everything else, one block lets you configure fully custom GET, POST or PUT requests, with your own headers. It is the universal exit door towards any API whatsoever. 🛠️

3. ⚙️ The In-House Secret Weapon: Voltask (The Automation Engine)

If connecting your front-end application to the whole web ecosystem (Zapier, Airtable) already pushes back the limits of business use, it is Voltask — Celestory's own automation engine — that shows the full extent of that power. 🦸‍♂️

🏢 Automation Within Your Own Walls (The Native Backend)

Voltask is not a third-party tool, it is the automation engine of the Celestory ecosystem — the equivalent of an "internal Zapier". 🔄
🔺 On the Creator side, Voltask is plugged in through a single block: Voltask Webhook. The rest of this chapter describes what Voltask can do once that webhook is called; Voltask has its own documentation, in the Build your Voltask AI Agents and Voltask Blocks categories.

1. Silent Execution: while your user clicks a button in your application, Voltask runs server-side (in the Cloud or on your self-hosted infrastructure). It can execute complex scripts (score computation, sorting through large databases, asynchronous LLM requests) without ever bogging down or slowing the player's device. 🤫
2. Maximum Security: your commercial API keys (your Stripe secret, your Airtable master key) are hidden inside the Voltask orchestrator, server-side. Even if a curious coder dug through your application's front-end code, they would never find a single password in there. 🔒
3. Data Typing: just like the Celestory graph, Voltask checks the format of the data being exchanged, so that one bad integration cannot bring the whole creation down. 🛡️

3bis. 🔗 MCP Connectors (Giving the AI Tools)

Beyond blocks, Celestory can plug the editor's AI assistant into MCP servers (Model Context Protocol) — the standard by which a service exposes its functions to an AI. In practice, this lets the assistant go and fetch a piece of information, or trigger an action in an external tool, while it is helping you.
This happens in the AI Generation window (Cmd+Shift+G), Tools tab:

1. Add a connector: give it a title and the URL of the MCP server.
2. Pick an authentication method: No authentication, API token, JSON headers, or OAuth.
3. With OAuth, an Authorize button opens the service's consent page. Once granted, the connector shows Connected and the list of available tools appears in the Functions tab.

🔺 Your tokens are never sent back to the interface: only the authentication method in use is displayed.

4. 🧰 Pushing Code Further: The Voltask Plugin SDK (Deno/Bun)

If even Voltask's default plugin catalogue does not cover your hyper-specialised business need (a cryptographic connection to an old corporate archiving server, or the use of some exotic legacy Node SDK wrapper), the architecture still does not get in your way. 🚀

• An Open SDK: Celestory provides the Voltask Plugin SDK. It lets any TypeScript developer (using the fast Deno or Bun runtimes) code the missing connector. 👨‍💻
• Turned into No-Code: once the plugin is built, its triggers and actions appear like pure visual magic as new drag-and-drop blocks in the Celestory Creator graph… ready to be used by the creative team, who do not know how to code. ✨

Conclusion: Celestory breaks the traditional silos of design tools by acting as a "technological octopus" 🐙. Front and back-end are finally unified for tenfold productivity, without the mandatory involvement of a battalion of developers, the whole thing secured by its smart asynchronous execution engine (Voltask). 🏆

Updated on: 21/09/2026