# Activity Nodes
In ONEWEB, **Activity Nodes** are the fundamental building blocks used to design **integration logic and execution flow**.\
They represent individual actions, decisions, and events that occur during the execution of a **Microflow or Process Flow**.
In **Process Designer**, an Activity Node is also referred to as a **Node Task**.\
Node Tasks are grouped into logical categories to support different integration and workflow scenarios.
***
### Node Task Groups Overview
The Node Task panel is divided into **four main groups**:
1. **Activity Tasks** – perform integration or execution actions
2. **Gateway Tasks** – control execution paths using conditions
3. **Event Notations** – start or end flows based on events
4. **Boundary Events** – handle timers and error conditions
Each group serves a specific role in defining how integration logic is executed.
***
### Activity Tasks
**Activity Tasks** are used to perform concrete actions such as calling services, accessing databases, or executing custom logic.
| Notation | Name | Description |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | --------------------------------------------------------------------- |
|  | **Java Task** | Executes custom Java functions from uploaded Java libraries. |
|  | **Database Task** | Executes SQL operations such as SELECT, INSERT, UPDATE, and DELETE. |
|  | **Web Service Task** | Calls external SOAP web services or REST APIs. |
|  | **Sub Flow Task** | Calls another Process or Microflow within the same project for reuse. |
|  | **Push Notification** | Sends notifications to mobile applications. |
Activity Tasks are typically used to **interact with external systems or perform integration logic**.
***
### Gateway Tasks
**Gateway Tasks** control the execution path of a process based on conditions.\
They allow the flow to branch into different paths.
| Notation | Name | Description |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------- | ------------------------------------------------------------------------------------- |
|  | **Exclusive Gateway** | Routes execution to one path based on conditions. Only the first valid path is taken. |
Gateway Tasks are essential for **decision‑based integration flows**.
***
### Event Notations
**Event Notations** represent triggers that **start or end** a process.
| Notation | Name | Description |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------- | ----------------------------- |
|  | **Start Event** | Initiates the flow. |
|  | **End Event** | Marks completion of the flow. |
Events define **when integration logic begins and ends**.
***
### Boundary Event Notations
**Boundary Events** are attached to Activity Tasks and act as listeners for specific situations.
| Notation | Name | Description |
| --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------- | ------------------------------------------------------ |
|  | **Timer** | Triggers another task after a specified time duration. |
|  | **Error** | Triggers an alternate path when an error occurs. |
Boundary events support **resilience, timeout handling, and exception management**.
***
### Properties of Activity Nodes
Each Activity Node includes a **General tab**, displayed when double‑clicking a node.\
This tab provides generic metadata for the node.
#### General Tab Properties
| Property | Mandatory | Default | Description |
| ----------- | --------- | ------- | ---------------------------------- |
| Name | Yes | No | Name of the node task |
| ID | Yes | Yes | System‑generated unique identifier |
| Type | Yes | Yes | Type of the node task |
| Description | No | No | Optional descriptive text |
***
### Summary
**Activity Nodes** define how integration logic is executed in ONEWEB through Microflows and Process Flows.
They enable applications to:
* Interact with databases, services, and external systems
* Control execution paths and decisions
* Handle events, delays, and errors
* Build clean, reusable, and maintainable integration flows
Together, Activity Nodes form the **execution backbone of ONEWEB’s integration architecture**.
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.onewebstack.com/oneweb-platform-th/building-apps/integrations/develop-integration-with-oneweb-microflow/activity-nodes.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
