Last updated Nov 17, 2025

Forge modules

You can use the following modules with Jira, Confluence, Bitbucket, and Compass:

Consumer

Define how the queue processes async events with the consumer module.

Function

Define the app's behavior in the function module.

Scheduled trigger

Invoke a function repeatedly using the scheduledTrigger module. Each trigger starts about 5 minutes after app deployment and then runs at set intervals—hourly, daily, or weekly.

SQL

Enable Forge SQL on the app. This storage capability is currently in Preview.

Trigger

Invoke a function with the trigger module when an Atlassian app event, app lifecycle event, or data security policy event occurs. For example, when an issue is created in Jira.

Web trigger

Invoke a function with the webtrigger module when an HTTP request is made. Use the web trigger runtime API within your app to get the URL for calling the web trigger.

Dynamic Modules (EAP)

Forge Dynamic Modules is now available as part of Forge’s Early Access Program (EAP). To start testing this, sign up here.

EAP features and APIs are unsupported, and subject to change without notice. Apps that use dynamic modules should not be deployed to production environments.

All dynamic modules created during EAP will not be carried over to Preview. For more details, see Forge EAP, Preview, and GA.

In addition to declaring modules in your app manifest, Forge apps can register some modules dynamically at runtime. This capability provides you with the flexibility to define an app's behaviour, and is useful for adding app features that are more responsive to arbitrary user needs.

Dynamic modules are registered in the context of an app installation, which means that an app can register different modules for each app installation. For now, only the Trigger module can be declared as a dynamic module. We are planning to add more in the future.

For more details, see Dynamic Modules.