Module Types: Input, Processing, and Scheduled

Every module in BRYTER belongs to one of three types. The type controls how the module starts, which node types are available inside it, and whether it can return output values or run on a schedule.

Input modules are opened by a person in the browser. They support the full range of nodes, input nodes, action nodes, and result nodes. They are the right choice for interactive workflows, forms, and document generation that requires end user answers. If you have built modules in BRYTER before, this is the type you already know.

Processing modules run without a user interface. They are triggered by another module, a data view, or an external system calling the module's API endpoint. Because no one interacts with them directly, processing modules do not support input nodes, handover actions, or redirect result nodes. They can return output values that the calling module or API consumer receives when the module finishes.

Scheduled modules also run without a user interface, but they start automatically on a recurring schedule you configure, hourly, daily, weekly, monthly execution. Use them for recurring reports, data syncs, or background jobs. Like processing modules, they do not support input nodes, handover actions, or redirect result nodes.

Each type has a distinct icon and color so you can recognize them at a glance in the application page:

• Input — blue form icon
• Processing — pink bolt icon
• Scheduled — orange clock icon

Choose a type when you create a module

When you click + New on the application page, you will see the three module types with short descriptions. Pick the one that matches how the module will be triggered.

If you are unsure, ask yourself:

• Will a person open this module and answer questions? → Input
• Will another module, data view, or external system call it? → Processing
• Should it run automatically at a set interval? → Scheduled

Change a module's type

You can change a module's type at any time. In the editor, click the Change module type button in the header (the arrows icon ). A dialog will open showing the target types and what will happen during the conversion.

Keep the following in mind:

• Input → Processing or Scheduled: Start parameters are removed. You must first remove any nodes that require user interaction (input nodes, handover actions, and redirect results) before the conversion can proceed.
• Processing → Scheduled: Output values configured on the API node are removed.
• Scheduled → Processing: The schedule is removed.
• Processing or Scheduled → Input: Output values and schedules are removed.

The dialog warns you before any data is deleted, and lists exactly what will be removed so you can confirm.

Configure a schedule for a scheduled module

Scheduled modules run the live-published version of the module on a recurring basis. To set up a schedule:

1. Open the module in the editor and publish the module to the Live environment. Schedules only run against the live version.
2. Click the SCHEDULE node at the very top of your build.
3. Click Create schedule.
4. Configure a recurring schedule for hourly, daily, weekly, or monthly execution.
5. Click Save.

You can edit or delete the schedule at any time from the SCHEDULE node. The timezone is displayed below the configuration.

Existing modules without a type

Modules created before module types were introduced do not have a type assigned yet. When you open one of these modules in the editor, BRYTER classifies it automatically based on its contents:

• If the module contains input nodes, it is classified as Input.
• If the module has a schedule configured at the application level, it is classified as Scheduled.
• If the module is headless and has no schedule, the editor shows a dialog asking you to choose a type. Processing is preselected as the most likely match.

Occasionally asked questions

Related articles

• Introduction to Modules
• Automatically Run a Module on a Schedule
• Make a Module Available via API Key Only