Serverless functions for the CMS

• Collect and store data in HubDB or the HubSpot CRM
• Run complex data calculators
• Dynamically fetch and display data from external systems
• Send form data to external systems

​

Limits

• 15 seconds of execution time per function.
• a content type of application/json for requests that include a body. Form posts (application/x-www-form-urlencoded) return a 415 response.

​

Building functions

​

Developer projects

• *-hsmeta.json: the function’s configuration file, which includes its unique identifier, the path to its JavaScript file, the secrets it uses, and its endpoint path and methods.
• .js file: the code that gets executed when the function is invoked. You’ll specify the file’s path in the *-hsmeta.json file.

project-folder/
├── hsproject.json
└── src/
    └── app/
        ├── app-hsmeta.json
        └── functions/
            ├── fetch-quote-hsmeta.json
            ├── fetch-quote.js
            └── package.json

​

Design manager

​

Authentication

• App access token: because project-based serverless functions are part of an app, every function can read the app’s access token with process.env.PRIVATE_APP_ACCESS_TOKEN. Requests have access to the scopes in the app’s requiredScopes. The token is available once the app is installed in the account with hs project install-app. Calls authenticated with the token count against your API call limits.
• Secrets: create secrets using the CLI (hs secret add <NAME>) to store credentials securely in HubSpot. You can make a secret available to a function by including the secret’s name in the config.secretKeys array of the function’s *-hsmeta.json file. Learn more about authentication in the reference documentation.

​

Debugging

​

Project-based serverless functions

• From the project directory, run hs project open to open the project in HubSpot.
• Open the app that contains the serverless function.
• Click the Logs tab.
• View logs for specific requests by clicking the request. You can also use the search bar to search by request ID.
• In the right panel, you can then click View log trace for a more in-depth breakdown of the request.

exports.main = async (context) => {
  console.log('Log some debug info');
  console.error('An error occurred');
  return {
    statusCode: 200,
    body: { message: 'Hello World' },
  };
};

​

Design manager serverless functions