Hotjar

undefined

Detail	Value
Category	Analytics
Base URL	https://api.hotjar.io/v1
Authentication	Bearer Token
Endpoints	5
Connector key	hotjar

Using Hotjar in a workflow

1. Go to Connections and click New Connection.
2. Pick Hotjar from the marketplace.
3. Enter your credentials (see Authentication above for what's expected).
4. In a workflow, drop an API Call node and select this connection.
5. Pick the operation you need from the Operation dropdown. The full list is below.

Available endpoints

Endpoint	Summary
GET	Sites
GET	Feedback
GET	Surveys
GET	Heatmaps
GET	Recordings

Each endpoint is documented in full below. Use the outline on the right to jump to one.

GET

Sites

Detail	Value
Operation ID	sites_0
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hotjar connection from the Connection dropdown.
3. In the Operation dropdown, select sites_0.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hotjar API reference.

GET

Feedback

Detail	Value
Operation ID	feedback_1
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hotjar connection from the Connection dropdown.
3. In the Operation dropdown, select feedback_1.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hotjar API reference.

GET

Surveys

Detail	Value
Operation ID	surveys_2
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hotjar connection from the Connection dropdown.
3. In the Operation dropdown, select surveys_2.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hotjar API reference.

GET

Heatmaps

Detail	Value
Operation ID	heatmaps_3
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hotjar connection from the Connection dropdown.
3. In the Operation dropdown, select heatmaps_3.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hotjar API reference.

GET

Recordings

Detail	Value
Operation ID	recordings_4
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Hotjar connection from the Connection dropdown.
3. In the Operation dropdown, select recordings_4.
4. Fill in the parameter fields that appear. Use {{...}} to reference upstream values.

What it returns

The API Call node writes the response to the workflow context:

{
  status: 200,
  success: true,
  data: { ...response body from the API... },
  latencyMs: 142
}

Reference response fields downstream as {{nodeId.data.path}}. The exact response shape is documented on the upstream Hotjar API reference.