# Activity creation and deployment controls

Find reusable actions, create a Python activity, configure its inputs, and inspect builds and deployments.

Source: https://docs.rumata.dev/guides/controls-activities
Reviewed: 2026-09-06

## Before you start

- Open the named screen in Rumata. Available controls may depend on your account, permissions, and resource state.

<a id="list"></a>

## Activity list

Open [System Explorer](https://docs.rumata.dev/guides/controls-preview#navigation) → [Activities](https://docs.rumata.dev/guides/controls-activities#list). An activity is a reusable action that a workflow can call. Create an activity by editing its code in the wizard, or ask the Rumata agent to create it for you.

| Control | What it does |
| --- | --- |
| Search activities | Filter the loaded activities by name or description. |
| All Statuses / Active / Disabled / Creating | Narrow the list by activity status. |
| Activity row / Activity details | Open the activity’s [Overview](https://docs.rumata.dev/guides/controls-activities#builds-source) tab. |
| View source / View Code | Open the Source tab for the activity’s recorded builds. |
| Manage access | Control which groups can use, build, deploy, or manage the activity. |
| New Activity | Open a local creation draft. This does not create the resource until you submit [Create Activity](https://docs.rumata.dev/guides/controls-activities#wizard). |

![Sabai Talk Thai Activities list with login, registration, SQL, and file-storage operations.](https://docs.rumata.dev/media/manual/activities.jpg)

Reference capture from the separate Sabai Talk Thai application (September 8, 2026). These reusable operations support the application’s backend. Open [Details](https://docs.rumata.dev/guides/controls-activities#builds-source) to inspect an operation before using it.

<a id="wizard"></a>

## Creation wizard and basic information

The four tabs are [Basic Info](https://docs.rumata.dev/guides/controls-activities#wizard), [Activity Code](https://docs.rumata.dev/guides/controls-activities#wizard), [Configuration](https://docs.rumata.dev/guides/controls-activities#configuration), and [Machine Spec](https://docs.rumata.dev/guides/controls-activities#wizard). Review all four before creating the activity.

| Control | What it does |
| --- | --- |
| Back | Leave the wizard and return to the activity list. This exits the wizard instead of moving back one step. An unsubmitted draft is not a saved activity. |
| Next Step / numbered step tabs | Move through the form or return to a specific section. |
| Activity Name | Enter a unique activity name using lowercase letters, numbers, dots, slashes, underscores, or hyphens, up to 30 characters. |
| Description | Explain the action in up to 120 characters. Both name and description are required. |
| Data Provider | Mark the activity as providing data to other activities. |
| Programming Language | Show Python, the language supported by this wizard. The field is disabled. |
| Create Activity | Validate the form, create the activity, and queue its build. It appears on [Machine Spec](https://docs.rumata.dev/guides/controls-activities#wizard) and becomes Creating… while submitting. |

<a id="draft-files"></a>

## Activity Code: files and editing

The wizard starts with main.py. File operations here edit the creation draft; they do not publish a running activity.

| Control | What it does |
| --- | --- |
| Explorer toggle / divider | Show or hide the file browser and resize it beside the editor. |
| Files / Content search | Search by filename or search text within the available files. Select a result to open the file. |
| File / folder row | Open a file or expand/collapse a directory. |
| File tab / tab close icon | Switch between open files or close a tab. Closing a tab does not delete its file. |
| Code text editor | Edit the selected file in the draft. A modified indicator marks changed contents. |
| Plus / New File / New File Here | Open file creation. Choose Directory, Name, and Type, then Create. A missing extension is added from Type, and duplicate paths are rejected. |
| Folder-plus / New Directory / New Directory Here | Open directory creation. Choose its parent and name, then Create. Cancel or Close leaves the draft unchanged. |
| Rename in the file context menu | Open the filename field. In this activity-file browser, Enter or leaving the field closes it without applying the rename; Escape cancels. Use the full [Code](https://docs.rumata.dev/guides/controls-code#save-push) editor to rename an existing workspace file. |
| Delete file / Delete directory in the context menu | Remove that item from the creation draft. Check its contents before using this action. |

<a id="configuration"></a>

## Entry point and arguments

The entry point tells Rumata which function to call. Arguments are named settings supplied to that function.

| Control | What it does |
| --- | --- |
| Entry File | Choose the file containing the function to run. |
| Entry Function | Enter the function’s name, initially main. |
| Package Manager | Select pip, the supported dependency manager in this wizard. |
| Edit entry function arguments | Open the detected function signature and its configurable parameters. |
| Highlighted argument / argument button | Open the settings for that parameter. |
| Type: String / Number / Boolean / Object / Array | Describe whether the setting is text, a number, yes/no, a structured record, or a list. |
| Argument Description | Explain what a workflow author should provide. |
| Default Value | Set the value to use when a value is not explicitly supplied. |
| Optional | Mark whether the caller may omit this setting. |
| Options (comma separated) | For a string setting, list the choices presented to the caller. |
| Done / Close in argument settings | Return from the argument editor. Changes already update the local creation draft; Done is not deployment. |

![Activity details dialog describing a login operation and its configuration fields.](https://docs.rumata.dev/media/manual/activity-details.jpg)

Reference capture from the separate Sabai Talk Thai application (September 8, 2026). The details describe what the operation expects. Field definitions are different from actual secret values or customer data.

<a id="machine-spec"></a>

## Machine Spec

This specification controls resources requested by the activity when it runs. It is separate from your factory [development machine](https://docs.rumata.dev/guides/development#machine)’s size.

| Control | What it does |
| --- | --- |
| Memory slider | Choose 128–1,024 MB in the current form. The displayed initial value is 512 MB. |
| CPU slider | Choose 0.1–1 CPU core in increments of 0.1. The initial value is 0.4 cores. |
| Activity Summary | Review the name, description, entry point, package manager, and configuration fields before [Create Activity](https://docs.rumata.dev/guides/controls-activities#wizard). |

<a id="builds-source"></a>

## Activity details: builds and source

Open an existing activity to inspect the versions Rumata built and the source used by those builds.

| Control | What it does |
| --- | --- |
| Overview / Builds / Deployments / Source | Switch between metadata, build records, running versions, and source files. |
| Source on a build | Open files for that specific build. Disabled when its repository, activity path, or commit/ref information is missing. |
| Choose a build in Source | Select the recorded revision to inspect. |
| Repository link | Open the source repository in a new tab. |
| Source file explorer / search / tabs | Browse files for the chosen build. This view is read-only; editing and file-creation controls are hidden. |
| Close activity details | Return to the activity list. |

<a id="deployment"></a>

## Deploy and stop an activity

A build packages code. A deployment makes that build available for workflow calls. The deployment state is shown separately from build success.

| Control | What it does |
| --- | --- |
| Deploy on a build | Open deployment settings. Unavailable while the build is in progress or failed, while another request is submitting, or until an active deployment has stopped. |
| Disabled Deploy explanation | Hover over or focus the area around the disabled action to learn why the build cannot be deployed. |
| Idle before sleeping | Choose an allowed auto-sleep duration. The default and plan maximum are marked. The first request after sleep waits for the activity to wake. |
| Deploy activity | Start an on-demand deployment with that idle duration. Cancel closes the form without deploying. |
| Stop on a deployment | Open a confirmation in the Deployments tab. |
| Stop deployment in confirmation | Stop accepting new workflow requests. You can deploy a successful build again after it stops. |
| Cancel stop | Keep the current deployment. |

## Related guides

- [Activities](https://docs.rumata.dev/guides/system-explorer-activities)
- [Groups, invitations, and access controls](https://docs.rumata.dev/guides/controls-access)
- [Code and development machines](https://docs.rumata.dev/guides/development)