Skip to content

CTAs

Use this capability family for HubSpot calls to action, including draft and published CTA changes.

Supported actionsBridge or hybrid actionsAccess used
33Varies by plan details
  • Create a CTA from a known template.
  • Update CTA module content or publish state.
  • Delete a CTA draft after confirming it is not needed.
  • Confirm the target portal is correct.
  • Check the operation names, target assets, and required access.
  • Resolve missing-permission warnings before execution.
  • Review operation results after execution.
  • Review CTA name, template, module content, publish state, and display behavior.
  • Confirm bridge-backed content changes are made in the right browser session.
Action IDWhat it doesExecutionRequired accessMain details
create_ctaCreate a HubSpot CTA.Requires the Daeda Bridge extensionNo additional connected-portal scopename, template path
delete_ctaDelete a HubSpot CTA draft.Requires the Daeda Bridge extensionNo additional connected-portal scopeCTA ID
update_ctaUpdate an existing HubSpot CTA.Requires the Daeda Bridge extensionNo additional connected-portal scopeCTA ID

Create a HubSpot CTA. The draft records name, template path for review.

  • Action ID: create_cta
  • Change type: Create
  • Execution: Requires the Daeda Bridge extension
  • Required access: No additional connected-portal scope
  • Main details reviewed in the plan: name, template path

Delete a HubSpot CTA draft. The draft records CTA ID for review.

  • Action ID: delete_cta
  • Change type: Delete
  • Execution: Requires the Daeda Bridge extension
  • Required access: No additional connected-portal scope
  • Main details reviewed in the plan: CTA ID

Update an existing HubSpot CTA. The draft records CTA ID for review.

  • Action ID: update_cta
  • Change type: Update
  • Execution: Requires the Daeda Bridge extension
  • Required access: No additional connected-portal scope
  • Main details reviewed in the plan: CTA ID

Back to supported actions