Skip to main content


In Temporal, Activities are typically used to interact with external resources, like making an HTTP request. Unlike Workflows, Activities execute in the standard Node.js environment, not an isolate. So any code that needs to talk to the outside world needs to be in an Activity.


Below is a simple Activity that accepts a string parameter, appends a word to it, and returns the result. The Temporal Node SDK looks for any .js files in the lib/activities directory, and automatically registers any exported functions as Activities.

export async function greet(name: string): Promise<string> {  return `Hello, ${name}!`;}

Under the hood, the Temporal Node SDK uses Webpack to bundle your Workflows before running them. This may cause issues with certain npm modules.

Importing and Using#

You can import the above greet() Activity in a Workflow as shown below, assuming that the greet function is in the lib/activities/greeter.js file.

import {greet} from "@activities/greeter";

You can also use require() as shown below.

const {greet} = require("@activities/greeter");

When you import an Activity function from a Workflow, the Node SDK replaces the Activity function with a stubbed function that schedules the Activity on the Temporal server. For example, if you print greet.toString() in the previous example, Node will not print the contents of the greet() function from lib/activities.greeter.js. Instead, Node will print a function that calls the Node SDK's internal scheduleActivity() function.


Currently, you need to use the @activities prefix. Do not import your Activity by using the '../activities/greeter' path; otherwise your Activity executes in the same V8 isolate as your Workflow, and your Activity is subject to the same restrictions as your Workflow.

Get notified of updates