HubSpot: List Campaign Assets

List the emails, forms, landing pages, and other assets in a HubSpot marketing campaign, filtered by asset type.

Tool ID: hubspot_list_campaign_assets

Run this action

Use the TypeScript SDK for one call. Use ctx.tools.execute(...) inside a Play for durable calls, scheduled calls, or CSV processing.

import { Deepline } from 'deepline';

const deepline = await Deepline.connect();
const result = await deepline.tools.execute(
  'hubspot_list_campaign_assets',
  {
    "campaign_guid": "campaign_123",
    "asset_type": "AD_CAMPAIGN"
  },
);

console.log(result.toolResponse.raw);

CLI

deepline tools execute hubspot_list_campaign_assets --input '{
  "campaign_guid": "campaign_123",
  "asset_type": "AD_CAMPAIGN"
}' --json

Example response

The static output schema lacks the details for a reliable example. Use deepline describe hubspot_list_campaign_assets --json for the complete live contract.

Input reference

List assets associated with a marketing campaign.

Name	Type	Required	Default	Details
`payload.campaign_guid`	`string`	Yes	—	HubSpot campaign GUID.
`payload.asset_type`	`"AD_CAMPAIGN" \| "BLOG_POST" \| "SOCIAL_BROADCAST" \| "WEB_INTERACTIVE" \| "CTA" \| "EXTERNAL_WEB_URL" \| "FORM" \| "LANDING_PAGE" \| "MARKETING_EMAIL" \| "MARKETING_EVENT" \| "OBJECT_LIST" \| "SITE_PAGE" \| "AUTOMATION_PLATFORM_FLOW" \| "MARKETING_SMS"`	Yes	—	Allowed: `AD_CAMPAIGN`, `BLOG_POST`, `SOCIAL_BROADCAST`, `WEB_INTERACTIVE`, `CTA`, `EXTERNAL_WEB_URL`, `FORM`, `LANDING_PAGE`, `MARKETING_EMAIL`, `MARKETING_EVENT`, `OBJECT_LIST`, `SITE_PAGE`, `AUTOMATION_PLATFORM_FLOW`, `MARKETING_SMS`.
`payload.limit`	`integer`	No	—	Maximum results to return. HubSpot allows values from 1 to 100. Minimum: 1. Maximum: 100.
`payload.after`	`string`	No	—	Forward paging cursor.
`payload.before`	`string`	No	—	Backward paging cursor.
`payload.start_date`	`string`	No	—	Optional start date for asset metrics, formatted as YYYY-MM-DD. Pattern: `^\d{4}-\d{2}-\d{2}$`.
`payload.end_date`	`string`	No	—	Optional end date for asset metrics, formatted as YYYY-MM-DD. Pattern: `^\d{4}-\d{2}-\d{2}$`.
`payload.query_params`	`record`	No	—	—

Output reference

Standard tool result payload.

Name	Type	Required	Default	Details
`result.data`	`record`	Yes	—	Provider response payload.
`result.meta`	`record`	No	—	Additional response metadata (status, paging).

Deepline cost

Pricing model: fixed (per call).
Estimated Deepline credits: 0 per pricing unit.
Provider-native pricing may still exist outside Deepline credit billing.

​Run this action

​CLI

​Example response

​Input reference

​Output reference

​Deepline cost

​Related documentation

Run this action

CLI

Example response

Input reference

Output reference

Deepline cost

Related documentation