Wiresk

Wiresk

HubSpot CRM – Owner & Additional Methods

Estimated reading time: 2 min

What your automation will do…

A connection to your HubSpot account is needed so we can sync it with our platform.
Refer to HubSpot CRM – connection.
You can include between 1 and 255 Methods to build complex Flows.
HUBSPOT HubSpot CRM - Owner & Additional Methods

HubSpot owners assign specific users to records, activities, or marketing tasks, and can be used in personalization tokens for your content. Owners are automatically created and updated in HubSpot when new users are added.
Source: HubSpot

This Method retrieves an owner’s identifying details, including the owner ID. This identifier can then be used to assign ownership to CRM records in HubSpot.
 
See HubSpot doc.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Get Owner
Connection*Select your connection or create one
Map Fields
User ID *  In the default value field, select the specific Owner you want to retrieve information from within a dynamic list of available Owners in your HubSpot database.
If Not Found, Consider as*Success – When Owner ID is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

HUBSPOT HubSpot CRM - Owner & Additional Methods
This endpoint is used to get all pipelines for either deals or tickets. (These are currently the only supported object types for this endpoint).
 
Use case for this endpoint: It can be used to sync all of a particular company’s deal pipelines to an external system.
Note: This endpoint requires either the contacts scope (to fetch deals pipelines) or the tickets scope.
 
Source: HubSpot Docs Pipelines

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*List Deals/Tickets Pipelines
Connection*Select your connection or create one
Map Fields
Object Type*:Select the HubSpot Object type that you want to retrieve the pipelines information:
Deals
Tickets

(*) required field

Read a property identified by it Property Name.
 
See HubSpot doc.

Configuration Table:

Input Options:

  • Input: Allows dynamic inputs, e.g., from a Trigger or from Step responses. Input tab>uncheck “Show recommended” to see all fields).
  • Default Value: You can specify a fixed attribute.
Name*Get a Record Property
Connection*Select your connection or create one
Map Fields
Record Type *  Select the Object Type.
Property Name*  The internal property name, which must be used when referencing the property.
If Not Found, Consider as*Success – When Owner ID is not found during execution, the system does not treat this as an error. Instead, it considers the operation successful and continues with the workflow.

Failed – Wiresk treats this as an error or failure. The workflow stops or takes a predefined failure action.

(*) required field

{
  "createdUserId": "string",
  "hidden": false,
  "modificationMetadata": {
    "readOnlyOptions": true,
    "readOnlyValue": true,
    "readOnlyDefinition": true,
    "archivable": true
  },
  "displayOrder": 2,
  "description": "string",
  "showCurrencySymbol": true,
  "label": "My Contact Property",
  "type": "enumeration",
  "hubspotDefined": true,
  "formField": true,
  "createdAt": "2025-01-21T04:14:12.423Z",
  "archivedAt": "2025-01-21T04:14:12.423Z",
  "archived": true,
  "groupName": "contactinformation",
  "referencedObjectType": "string",
  "name": "my_contact_property",
  "options": [
    {
      "hidden": false,
      "displayOrder": 1,
      "description": "Choice number one",
      "label": "Option A",
      "value": "A"
    }
  ],
  "calculationFormula": "string",
  "hasUniqueValue": false,
  "fieldType": "select",
  "updatedUserId": "string",
  "calculated": true,
  "externalOptions": true,
  "updatedAt": "2025-01-21T04:14:12.423Z"
}

Once your Flow is configured, you can test or automate it using the Run panel or by managing Triggers from the Flow Management screen.

  • Run Flow: Manually runs the Flow once using sample data. Ideal for testing logic and field mapping. See How to Run a Flow.
  • Run Scheduler: Force-runs the Trigger immediately using live input. This bypasses the recurrence rule and is useful for verifying real data mapping. Learn more in Wiresk Scheduler – The Fundamentals.

From the Trigger management panel (clock icon), you can:

  • Activate or deactivate Triggers
  • Force-run the scheduler
  • Copy Routing Keys (for HTTP Triggers)

If your Flow uses a Webhook Trigger, it runs automatically on each incoming webhook—no scheduler required. It remains active until you manually deactivate it.