HubSpot: List templates

← Email templates operations · Get started

Operation hubspot.email_templates_retrieve_email_templates

Provider route: GET /automation/email-templates/2026-09. Alter supplies the connection’s credentials and routing.

Call through Alter

Install @alter-ai/sdk @alter-ai/hubspot with npm, or alter-sdk-hubspot with pip. Supply your connected customer’s grant ID and the arguments described below.

import { App } from "@alter-ai/sdk";
import { HubSpotIntegration } from "@alter-ai/hubspot";

async function execute(input: Parameters<HubSpotIntegration["emailTemplates"]["retrieveEmailTemplates"]>[0]) {
  const app = new App({ apiKey: process.env.ALTER_API_KEY! });
  try {
    const provider = new HubSpotIntegration(app, { grantId: process.env.PROVIDER_GRANT_ID! });
    const call = await provider.emailTemplates.retrieveEmailTemplates(input);
    const result = await call.wait();
    return result.bodyJson();
  } finally {
    await app.close();
  }
}

import os
from alter_sdk import App
from alter_sdk_hubspot import HubSpotIntegration

async def execute(arguments):
    async with App(api_key=os.environ["ALTER_API_KEY"]) as app:
        provider = HubSpotIntegration(app, {"grant_id": os.environ["PROVIDER_GRANT_ID"]})
        call = await provider.email_templates.retrieve_email_templates(arguments)
        result = await call.wait()
        return result.body_json()

Input

Field	Type	Presence	Description and constraints
$	object	Root	Additional keys: not allowed
query	object	Optional	Additional keys: not allowed
query.after	string	Optional
query.limit	integer	Optional	Default: 20 Format: int32

Response

Response media type: application/json. The table describes the pinned successful response. Referenced models link to their complete fields.

Field	Type	Presence	Description and constraints
$	Model	Root	Expand List templates — response body

Referenced models: List templates — response body

Schemas

List templates — response body

Field	Type	Presence	Description and constraints
$	object	Root
paging	Model	Optional	Expand List folders — response body — paging
results	array	Required within parent	An array of public templates. Each item in the array is an object representing a template with properties such as id, name, subject, body, folderId, ownerId, createdAt, and updatedAt.
results[]	Model	Each item	Expand Update template — response body

Referenced models: List folders — response body — paging, Update template — response body

List folders — response body — paging

Field	Type	Presence	Description and constraints
$	object	Root	Paging information for forward-only pagination. Contains the next page reference when more results are available; omitted or empty on the last page.
next	Model	Optional	Expand List folders — response body — paging next

Referenced models: List folders — response body — paging next

Update template — response body

Field	Type	Presence	Description and constraints
$	object	Root
body	string	Optional	The content of the email template, represented as a string.
createdAt	JSON	Optional
createdAt (anyOf 1)	integer	Alternative	The timestamp indicating when the email template was created, represented as an integer in int64 format. Format: int64
createdAt (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$
folderId	string	Optional	The identifier of the folder where the email template is stored, represented as a string.
id	string	Required within parent	The unique identifier for the email template, represented as a string.
name	string	Optional	The name of the email template, represented as a string.
ownerId	string	Optional	The identifier of the owner of the email template, represented as a string.
subject	string	Optional	The subject line of the email template, represented as a string.
updatedAt	JSON	Optional
updatedAt (anyOf 1)	integer	Alternative	The timestamp indicating when the email template was last updated, represented as an integer in int64 format. Format: int64
updatedAt (anyOf 2)	string	Alternative	Pattern: ^-?[0-9]+(?:\.[0-9]+)?(?:[eE][+-]?[0-9]+)?$

List folders — response body — paging next

Field	Type	Presence	Description and constraints
$	object	Root	Specifies the paging information needed to retrieve the next set of results in a paginated API response
after	string	Required within parent	A string that serves as the paging cursor token, indicating the position after the last successfully read resource.
link	string	Optional	A string representing the URL link to the next page of results.

Policy, approvals and errors

SDK function policy ID: hubspot.email_templates_retrieve_email_templates. Catalog operation: email_templates_retrieve_email_templates. Rules can name either ID; function rules distinguish managed calls and conservatively cover raw calls sharing the route. Existing grant permissions and policy rules apply. wait() returns an immediate result or waits for a required approval; it never approves the request itself. Persist the approval ID to resume after a restart.

Provider errors retain their response; JSON decoding raises ProviderAPIError for provider failures. ManagedOperationError identifies contract/input/retention errors. See error handling and provider-specific behavior. Sensitive input may be refused before approval storage. A decoding error never resubmits a write.

Required provider scopes: ["automation.email_templates.read"]

Official provider source