Skip to content

Lead Scoring

Use this capability family for creating, updating, and deleting HubSpot lead scores.

Supported actionsBridge or hybrid actionsAccess used
33Varies by plan details
  • Create a lead score for a defined audience and scoring model.
  • Update scoring criteria and suppression logic.
  • Delete an obsolete lead score after confirming it is no longer used.
  • 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.
  • Inspect scoring criteria, score thresholds, and suppression logic before activating customer-facing routing.
  • Confirm any referenced lists or properties exist and match the scoring intent.
Action IDWhat it doesExecutionRequired accessMain details
create_lead_scoreCreate a HubSpot lead score.Requires the Daeda Bridge extensionNo additional connected-portal scopescore configuration
delete_lead_scoreDelete a HubSpot lead score.Requires the Daeda Bridge extensionNo additional connected-portal scopescore ID
update_lead_scoreUpdate a HubSpot lead score.Requires the Daeda Bridge extensionNo additional connected-portal scopescore ID, score configuration

Create a HubSpot lead score. The draft records score configuration for review.

  • Action ID: create_lead_score
  • Change type: Create
  • Execution: Requires the Daeda Bridge extension
  • Required access: No additional connected-portal scope
  • Main details reviewed in the plan: score configuration
  • Planning notes:
    • Keep portal-specific property output names unique.

Delete a HubSpot lead score. The draft records score ID for review.

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

Update a HubSpot lead score. The draft records score ID, score configuration for review.

  • Action ID: update_lead_score
  • Change type: Update
  • Execution: Requires the Daeda Bridge extension
  • Required access: No additional connected-portal scope
  • Main details reviewed in the plan: score ID, score configuration
  • Planning notes:
    • Keep output property names unique unless reusing an output property already attached to this score.

Back to supported actions