# Use Extension in Workflow

Once a **Custom Extension** is **enabled** in the application, it becomes available for use in process workflows.\
The extension appears as a **Custom Activity Node** alongside standard activity nodes in Process Designer.

Users can use a custom extension in the workflow **exactly like a built‑in activity node**.

***

### Purpose

Using extensions in workflows allows you to:

* Reuse custom logic across multiple processes
* Incorporate proprietary or advanced functionality into workflows
* Extend process behavior beyond standard activity nodes
* Maintain clean and modular process designs

***

### Using a Custom Extension in a Process

To use an extension in a workflow:

1. Open **Process Designer**
2. Go to the **Activity** tab in the node palette
3. Locate the installed **Custom Extension**
4. **Drag and drop** the extension node onto the process canvas

<figure><img src="https://2015371994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FMpDjHWFRUtZ5nJcSfVXd%2Fuploads%2FXOXaL487sewuEiaqwqA4%2F0?alt=media" alt=""><figcaption></figcaption></figure>

Once placed on the diagram, the extension node behaves like any other activity node.

***

### Configuring the Extension Node

After adding the extension node to the workflow, users can:

* Open the node configuration panel
* Configure **input parameters** defined in the extension
* Configure **output parameters** if applicable
* Map Business Objects for data exchange
* Set execution‑specific properties exposed by the extension

All configuration options are defined by the extension’s **InputModel**, **OutputModel**, and JSON configuration.

***

### Data Mapping and Integration

Custom extension nodes fully support:

* Business Object mapping
* Input and output parameter binding
* Interaction with other activity nodes
* Use within Gateways, Lanes, and Event flows

This allows extension nodes to integrate seamlessly into the overall process logic.

***

### Usage Guidelines

* Ensure the extension is **enabled** in the Extension Store before use
* Place extension nodes inside the appropriate **Lane**
* Clearly map input and output parameters
* Test workflows after adding or updating extensions
* Avoid deleting or disabling extensions already used in active processes

***

### Summary

Custom Extensions can be used in workflows just like native Process Designer activities.

Key points:

* Enabled extensions appear in the **Activity** tab
* Drag‑and‑drop usage on the process canvas
* Fully configurable with Business Objects and parameters
* Seamless integration with existing process logic
* Supports reuse across multiple workflows

Using Custom Extensions in workflows enables ONEWEB users to build **powerful, flexible, and reusable business processes** tailored to their specific enterprise needs.


---

# 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/designer-reference/process-designer/process-designer-component/custom-extensions/use-extension-in-workflow.md?ask=<question>
```

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.