Serverless functions reference

Last updated:
  • CMS Hub
    • Enterprise

In this article, learn about the files found inside of a serverless .functions folder and the CLI commands you can use with serverless functions.

For a high-level overview of serverless functions, see the serverless functions overview.

Please note: serverless function files must be uploaded locally using the HubSpot CLI.


Your serverless.json file stores your configuration settings for functions inside of your .functions folder. This file is required for serverless functions to work. This file maps your functions to their endpoints.

// serverless.json { "runtime": "nodejs18.x", "version": "1.0", "environment": { "globalConfigKey": "some-value" }, "secrets": ["secretName"], "endpoints": { "events": { "file": "function1.js", "method":"GET" }, "events/update": { "method": "POST", "file": "action2.js", "environment": { "CONFIG_KEY": "some-other-value" }, "secrets": ["googleKeyName","otherkeyname"] } } }
Use this table to describe parameters / fields

The runtime environment. Supports the following Node.js versions:

  • Node 18 (nodejs18.x) (recommended)
  • Node 16 (nodejs16.x)
  • Node 14 (nodejs14.x)

HubSpot serverless function schema version. (Current version 1.0)


Endpoints define the paths that are exposed and their mapping to specific JavaScript files, within your functions folder.


Configuration variables passed to the executing function as environment variables at runtime. You might use this to add logic for using a testing version of an API instead of the real thing based on an environment variable.


An API key is a secret. The secrets in the config file refers to the name of the secret not it’s value. Do not put secrets directly in this file, only reference secret names. 

Please note: do not assign the same name to your secrets and environment variables. Doing so will result in conflicts when returning their values in the function.


Each endpoint can have its own environment variables and secrets. Variables specified outside of endpoints should be used for configuration settings that apply to all functions and endpoints.

"events/update": { "method": "POST", "file": "action2.js", "environment": { "configKey": "some-other-value" }, "secrets": ["googleAPIKeyName","otherKeyName"] }

Endpoints have a couple unique keys.

Use this table to describe parameters / fields
String or array of strings

HTTP method or methods that the endpoint supports. Defaults to GET.


Path to JavaScript function file with the implementation for the endpoint.

Serverless functions are exposed through a path at your HubSpot CMS account’s domain. This includes default sub-domains.

You can access these functions at the following URL: 


Below, learn about each URL component:

Use this table to describe parameters / fields

Your domain name.


The path reserved for serverless functions. All endpoints exist inside this path.


The endpoint name or path that you specified in the serverless.json file.


Your Hub ID. Providing this in the request will enable you to test your functions within module and template previews.

Function file

Each function is created as a Node.js JavaScript file in a folder ending in .functions. In addition to the Node.js standard library, functions can leverage the request library to make HTTP request to HubSpot APIs and other APIs. 

A basic serverless-function.js file looks like:

// Require axios library, to make API requests. const axios = require('axios'); // Environment variables from your serverless.json // process.env.globalConfigKey exports.main = (context, sendResponse) => { // your code called when the function is executed // context.params // context.body // context.accountId // context.limits // secrets created using the CLI are available in the environment variables. // process.env.secretName //sendResponse is what you will send back to services hitting your serverless function. sendResponse({body: {message:"my response"}, statusCode: 200}); };

Context object keys

Context Object Keys

The HubSpot account ID containing the function.


body is populated if the request is sent as a POST with a content type of application/json


If the request is from a cookied contact, the contact object will be present with a set of basic contact properties. These additional properties will also be available:

  • vid: The contact’s visitor id
  • isLoggedIn: when using CMS Memberships, this will be true if the contact is logged into the domain
  • listMemberships: an array of contact list ids that this contact is a member of

Contains headers sent from the client hitting your endpoint. See headers.


params is populated with query string values plus any HTML Form-POSTed values. These are structured as a map with strings as keys and an array of strings for each value. context.params.yourvalue


Returns how close you are to hitting the serverless function rate limits.

  • executionsRemaining - how many executions per minute are remaining.
  • timeRemaining - how much allowed execution time is remaining.


Sometimes it can be helpful to have the headers of the client hitting your endpoint. We provide the following headers through context.headers. This is similar to how you would access information through context.body.

Use this table to describe parameters / fields

Communicates which content types expressed as MIME types, the client understands. See MDN.


Communicates the content encoding the client understands. See MDN.


Communicates which human language and locale is preferred. See MDN.


Holds directives for caching. See MDN.


Communicates whether the network connection stays open. See MDN.


Contains cookies by sent the client. See MDN.


Communicates the domain name and TCP port number of a listening server. See MDN.


IP address of the end-user. See Cloudflare true-client-ip.


Communicates the clients preference for an encrypted and authenticated response. See MDN.


Vendor defined string identifying the application, operating system, application vendor, and version. See MDN.


Identifies the originating IP address of a client through a proxy or load balancer. See MDN.

Redirect by sending a header

You can perform a redirect from your serverless function by  sending a response with a location header and 301 statusCode.

sendResponse({ statusCode: 301, headers: { "Location": "" } });

Set cookies from your endpoint

From your serverless function you can tell the client (web browser) to set a cookie.

exports.main = (context, sendResponse) => { sendResponse({ body: { ... }, 'Set-Cookie': 'myCookie1=12345; expires=...; Max-Age=...', statusCode: 200 }); }

Set multiple values for a single header

For headers that support multiple values, you can use multiValueHeaders, to pass the values. For example: you can tell the browser to set multiple cookies.

exports.main = (context, sendResponse) => { sendResponse({ body: { ... }, multiValueHeaders: { 'Set-Cookie': [ 'myCookie1=12345; expires=...; Max-Age=...', 'myCookie2=56789; expires=...; Max-Age=...' ] }, statusCode: 200 }); }


API keys, and authentication information are referred to as secrets. Once added they are accessible through environment variables (process.env.secretName). You can assign secrets available for specific endpoints to use by adding the "secrets" key to your serverless.json file. Secrets are managed through the HubSpot CLI using the following commands:

Do not return your secret's value through console logging or as a response. Doing so would expose your secrets in your logs or in front-end pages that call your serverless function.

Using serverless functions with the form element

When submitting serverless functions use javascript to handle the form submission, and use the "contentType" : "application/json" header in your request. Do not use the <form> elements action attribute.


Cross Origin Resource Sharing (CORS) is a browser security feature. By default browsers restrict cross-origin requests initiated by javascript. This prevents malicious code running on a different domain, from affecting your site. This is called the same-origin policy. Because sending and retrieving data from other servers is sometimes a necessity, the external server, can supply HTTP headers that communicate which origins are permitted to read the information from a browser.

You should not run into CORS issues calling your serverless function within your HubSpot hosted pages. If you do, verify you are using the correct protocol.

Getting this CORS error?
"Access to fetch at [your function url] from origin [page making request] has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled."

Is your request to a different origin than the site calling it?

  • If the domain name is different, yes.
  • If using a different protocol(http, https), yes.

If using a different protocol, simply change the protocol to match and that will fix it. 

You can't modify HubSpot's Access-Control-Allow-Origin header at this time.

See MDN for further detailed CORS error troubleshooting.

Get requests

Get requests may be able to make CORS requests depending on the client. Do not make GET requests write anything, just return data.

Preloaded packages

HubSpot serverless functions currently come preloaded with the following packages:

To use the latest supported version of a preloaded package, or to use a newly added package:

  1. Clone or copy your function file.
  2. Change your function's endpoint in the serverless.json file to point to your new function file. You can safely delete the old version.

If you want to include packages outside of the preloaded package set, you can use webpack to combine your node modules and have your bundled files be your function files.


Serverless functions are intended to be fast and have a narrow focus. To enable quick calls and responses, HubSpot serverless functions are limited to:

  • 50 secrets per account
  • 128MB of memory
  • No more than 100 endpoints per HubSpot account
  • You must use contentType application/json when calling a function.
  • serverless function logs are stored for 90 days.
  • 6MB on an AWS Lambda invocation payload.

Execution limits

  • Each function has a maximum of 10 seconds of execution time.
  • Each account is limited to 600 total execution seconds per minute.

This means either of these scenarios can happen:

  • 60 function executions that take 10 seconds each to complete.
  • 6,000 function executions that take 100 milliseconds to complete.

Functions that exceed those limits will throw an error. Execution count and time limits will return a 429 response. The execution time of each function is included in the serverless function logs.

To assist in avoiding these limits, limit data is provided automatically to the function context during execution. You can use that to influence your application to stay within those limits. For example, if your application requires polling your endpoint, then you can return with your data a variable to influence the frequency of the polling. That way when traffic is high you can slow the rate of polling avoiding hitting limits, then ramp it back up when traffic is low.

Was this article helpful?
This form is used for documentation feedback only. Learn how to get help with HubSpot.