Default USD pricelist
  1. All Products
  2. Bellum Automation

Bellum Automation

https://nexusoneapp.com/web/image/product.template/353/image_1920?unique=556f80c

Bellum Automation
===================================

A dedicated automation control center for Bellum AI and Nexus One.

Key capabilities
----------------
* View every Bellum automation in one Nexus One app.
* Create, edit, duplicate, pause, resume, run, archive, or delete automations.
* Trigger workflows manually, on a schedule, by secure webhook, or from Nexus One model events.
* Build multi-step workflows for searching, creating, updating, duplicating, archiving, deleting, and calling administrator-approved business actions.
* Manage files through Nexus One attachment/document models instead of unsafe server filesystem access.
* Record complete execution and step-level audit history.
* Enforce the existing MCP model allowlist and read/create/update/delete permissions before every step.
* Expose Bellum connector-token-protected automation APIs.

Architecture
------------
The MCP module remains the secure connection and permission gateway. This module is the automation registry and execution engine. Keeping them separate avoids mixing transport security with workflow management while allowing both modules to share the same permissions and connector token.

$ 0.00 0.0 USD $ 0.00

$ 0.00

Not Available For Sale

This combination does not exist.

Contact Us

Terms and Conditions
30-day money-back guarantee
Shipping: 2-3 Business Days

Bellum Automation =================================== A dedicated automation control center for Bellum AI and Nexus One. Key capabilities ---------------- * View every Bellum automation in one Nexus One app. * Create, edit, duplicate, pause, resume, run, archive, or delete automations. * Trigger workflows manually, on a schedule, by secure webhook, or from Nexus One model events. * Build multi-step workflows for searching, creating, updating, duplicating, archiving, deleting, and calling administrator-approved business actions. * Manage files through Nexus One attachment/document models instead of unsafe server filesystem access. * Record complete execution and step-level audit history. * Enforce the existing MCP model allowlist and read/create/update/delete permissions before every step. * Expose Bellum connector-token-protected automation APIs. Architecture ------------ The MCP module remains the secure connection and permission gateway. This module is the automation registry and execution engine. Keeping them separate avoids mixing transport security with workflow management while allowing both modules to share the same permissions and connector token.