Rocketbot

Saturn Studio agents act in other systems through more than 500 standard apps and components, among them SAP, Salesforce, Microsoft 365, Google Workspace, Oracle, ServiceNow, HubSpot, Zendesk and WhatsApp, plus databases and any REST API, with credentials kept in an encrypted vault and shared by person or team. Where a system has no API, RPA Studio robots work through its screens, and Ai Studio can send an email, a WhatsApp message or an API call once it has read a document. Custom apps for systems outside the catalog come in a limited form on Standard and Enterprise and in full on Corporate.

Sourcedocs.rocketbot.com/2026/06/17/saturn-studio-conectores-e-integracionesread 2026-10-13

In Saturn Studio each agent is a flow of steps that loads its variables and vault credentials, runs with loops, branches and retries, pauses where a person must act and logs how it ended, and one agent finishing can start the next. A Tool Agent step lets an AI model choose among the tools a builder gives it. The Orchestrator queues runs of robots, Python scripts, applications and other RPA platforms and assigns each to the best available machine by tag, capacity and priority. Each Saturn run is capped at between 10 minutes and an hour depending on the plan.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

Ai Studio reads each email, document, image or audio file a flow hands it and returns structured fields that follow a template the team defines, so an agent works from the data its flow fetches on each run. Saturn Studio's Pinecone module creates a vector index, generates embeddings and upserts and queries them, and Rocketbot's own recipes pipe Gmail and PDF content through OpenAI into Pinecone so a question and answer agent can search a company's documents. That index sits in the customer's own Pinecone account, assembled from the recipe, and Rocketbot keeps no knowledge index of its own.

Sourcerocketbot.com/en/ai-studio.htmlread 2026-10-13

A flow can stop and wait for a person, for example sending an approval request by email, Teams or an Xperience form and carrying on only once it is approved, and common recipes hand a case to a human when the AI's confidence is low. Agents act within rules the builder sets, with every decision and action logged for audit. Human in the loop steps come with every plan.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

The Orchestrator is the suite's single identity point, with a role and permission matrix by module, two factor sign in and Google sign in on every plan, and Active Directory sign in and SCIM on Corporate.

Credentials sit in an encrypted vault, can be shared with a person or a team and revoked at once, robot steps are encrypted, and audit logs record who did what, kept from 90 days up to 12 months with SIEM export on Corporate.

Rocketbot holds an ISO/IEC 27001:2022 certificate from NYCE, with an IQNet counterpart, covering its cloud infrastructure, development and support, issued in May 2026, valid to May 2029 and held since June 2023.

Sourcedocs.rocketbot.com/2024/06/05/certificado-iso27001read 2026-10-13

The Orchestrator keeps four kinds of log, robot, process, user and instance, records the input data and the component where a run failed, and shows the live status, metrics, alerts and history of every automation. Saturn Studio keeps each agent run with detailed logs, full text log search and analytics dashboards, holding from 1,000 to 100,000 runs and logs for 7 to 365 days by plan. Older history has to be exported, since retention runs first in, first out, and Rocketbot's terms say the logs carry no forensic evidentiary integrity.

Sourcerocketbot.com/en/orchestrator.htmlread 2026-10-13

The question and answer agent can keep conversation history under an ID the builder sets, such as a chat, a channel or a user, holding the last messages up to a History Size the builder picks, and a datastore makes that history persist between runs. Global variables are set once for the account, readable by every agent and kept between runs, while local variables reset on each run, and Nexus's internal database holds records flows read and write. How long kept history lasts beyond that message window is up to the builder.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

Cloud plans run on the AWS public cloud, where the Orchestrator uses a database across several availability zones watched by Amazon CloudWatch, and the Orchestrator can also run on premises on the customer's own servers. RPA Studio robots always run on the customer's machines or virtual machines. Ai Studio is cloud only, though a customer can point it at its own model hosted on premises. Saturn Studio runs only in Rocketbot's cloud and cannot reach a local network, and no AWS region is named.

Sourcerocketbot.com/en/terms-and-conditions.htmlread 2026-10-13

The Saturn Studio template market is a catalog of prebuilt agents a team previews read only and adds to its workspace with one click, grouped by category and showing the modules each one uses, and administrators can publish their own. Access to templates widens by plan, with a custom set on Corporate.

Sourcedocs.rocketbot.com/2026/03/20/saturn-studio-market-de-templatesread 2026-10-13

Agents start from a webhook, a cron schedule, a form submitted in Xperience, an embedded chat widget, another agent finishing, a new record landing in the datastore, or by hand, and a webhook can answer at once or hold the call open until the agent is done. Ai Studio reads incoming email, documents, images and audio and can set a robot or flow going on what it finds, and WhatsApp and Telegram messages reach flows through their connectors. On the robot side, the Orchestrator schedules runs by cron, webhook or chaining.

Sourcedocs.rocketbot.com/2026/07/01/saturn-studio-referencia-tecnicaread 2026-10-13

A builder picks the model for each AI step in a flow, from OpenAI, Anthropic's Claude, Google's Gemini, Mistral AI, Groq, DeepSeek, xAI's Grok and Hugging Face to models on Azure OpenAI and AWS Bedrock, or any model ID available on OpenRouter, using the team's own keys. Ai Studio runs on Rocketbot's internal model on every plan, and from Standard up a company can connect its own model in the cloud or on its own servers.

Sourcedocs.rocketbot.com/2026/06/25/saturn-studio-changelogread 2026-10-13

API keys created in Saturn Studio let outside software start robots and read account data through the platform API, each key with a name, an expiry, a last used date and instant revocation, and Orchestrator API keys last two years. Inbound webhooks give each agent its own endpoint, and an MCP server lets AI clients such as Claude or Copilot build bots and run tasks in the account. Developers have no public endpoint reference for the platform API.

Sourcedocs.rocketbot.com/2026/03/10/saturn-studio-api-keysread 2026-10-13

Builders test a flow by running it and reading its logs, with log search and console output from custom JavaScript for debugging, and the Orchestrator versions robots with rollback.

Neither Saturn Studio nor the Orchestrator offers separate development, test and production environments inside one instance or Git style versioning, so promotion between stages follows the customer's own procedures, often a global variable that splits resources by environment.

Rocketbot's own guidance asks teams to keep a separate development environment and test robots with real data before production, and its terms say Ai Studio's accuracy in a flow must be validated before production use.

Sourcerocketbot.com/en/terms-and-conditions.htmlread 2026-10-13

RPA Studio builds software robots that work any system the way a person does, clicking, typing, copying data, filling in forms and reading the screen, and they run on the customer's own Windows, macOS or Linux machines. The Orchestrator dispatches them, and a Saturn Studio flow can call a robot as one of its steps.

Sourcerocketbot.com/en/rpa-studio.htmlread 2026-10-13