Skip to main content

HubSpot Workflow Action

Flow​

  1. HubSpot workflow triggers webhook/custom code action
  2. Call POST /v1/connectors/:installationId/invoke
  3. Veritrellis returns allowed, pending_approval, or denied
  4. Workflow stores request_id and status in CRM properties
  5. UI extension reads /public/requests/:requestId/summary for status display

Request target​

POST https://api.veritrellis.ai/v1/connectors/<INSTALLATION_ID>/invoke

Headers:

X-Veritrellis-Inbound-Key: <inbound key>
Content-Type: application/json

Security notes​

  • Keep sandbox and production installations separated
  • Never write permit JWTs into CRM properties
  • Use admin console for approve/reject decisions (CRM card is status-only by default)