Skip to content

HubSpot: Create — task Series create Tasks Series

HubSpot taskSeries.createTasksSeries: arguments, response, policy and SDK examples.

← Task series operations · Get started

Operation hubspot.task_series_create_tasks_series

Provider route: POST /crm/task-series/2026-09. Alter supplies the connection’s credentials and routing.

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["taskSeries"]["createTasksSeries"]>[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.taskSeries.createTasksSeries(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.task_series.create_tasks_series(arguments)
result = await call.wait()
return result.body_json()
FieldTypePresenceDescription and constraints
$objectRootAdditional keys: not allowed
bodyModelRequired within parentExpand Create — task Series create Tasks Series — request body — body

Referenced models: Create — task Series create Tasks Series — request body — body

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

FieldTypePresenceDescription and constraints
$ModelRootExpand Update task series — response body

Referenced models: Update task series — response body

Update task series — response body
FieldTypePresenceDescription and constraints
$objectRoot
createdAtstringOptionalThe date and time when the task series was created, in ISO 8601 format.
Format: date-time
idstringRequired within parentThe unique identifier for the task series, represented as a string.
propertiesobjectRequired within parentA map of custom property names to their values, where each value is a string.
Additional keys: see wildcard field
properties.*stringAdditional keys
seriesModelRequired within parentExpand Update task series — response body — series
updatedAtstringOptionalThe date and time when the task series was last updated, in ISO 8601 format.
Format: date-time

Referenced models: Update task series — response body — series

Create — task Series create Tasks Series — request body — body
FieldTypePresenceDescription and constraints
$objectRoot
propertiesobjectRequired within parentA map of additional property names to their values, represented as a string-to-string object.
Additional keys: see wildcard field
properties.*stringAdditional keys
seriesModelRequired within parentExpand Update task series — response body — series
taskIdintegerRequired within parentThe unique identifier for the task, represented as an integer in int64 format.
Format: int64

Referenced models: Update task series — response body — series

Update task series — response body — series
FieldTypePresenceDescription and constraints
$objectRoot
repeatIntervalstringOptionalThe recurrence schedule as a standards-compliant RFC-5545 RRULE string.
repeatStatusstringOptionalA string representing the current status of the task series repetition.
startsAtstringOptionalThe date and time when the task series is scheduled to start, in ISO 8601 format.
Format: date-time

SDK function policy ID: hubspot.task_series_create_tasks_series. Catalog operation: task_series_create_tasks_series. 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: ["crm.objects.contacts.read", "crm.objects.contacts.write"]

Official provider source

Report an issue with this page

Necessary

Required for sign-in, security, authorization, and remembering your choices.

Always active

Analytics

Helps us understand which product and documentation features are useful.

Performance diagnostics

Uses performance tracing and privacy-masked session replay to diagnose problems.

You can change these choices at any time from Cookie settings.