HubSpot Connector

Inbound

• Request target: POST /v1/connectors/:installationId/invoke
• Auth: connector-scoped Veritrellis API key
• Workspace/environment must match the connector installation
• subscriptionType can be normalized into platform_action

Action mapping

Create bindings where:

• platform_action_name matches HubSpot action/event name
• action_template is a canonical Veritrellis action_type
• field_mapping_json maps inbound fields to authorize shape

Example mapping:

{
  "resource_ref": "objectId",
  "payload.customer_id": "properties.email",
  "payload.amount": "properties.amount",
  "payload.currency": "properties.currency",
  "payload.reason": "properties.reason",
  "payload.original_charge_id": "properties.charge_id"
}

Outbound relay

After allow (or post-approval allow), Veritrellis sends one HTTPS POST to installation outbound destination with:

• veritrellis envelope (request_id, decision, optional permit)
• platform payload echo

Use idempotency keys and a domain allowlist on installation config for safe replay behavior.

Response model

Connector invoke responses follow authorize semantics:

• allowed
• pending_approval
• denied (with reason_code)