FullStory

undefined

Detail	Value
Category	Analytics
Base URL	https://api.fullstory.com
Authentication	API Key
Endpoints	5
Connector key	fullstory

Using FullStory in a workflow

1. Go to Connections and click New Connection.
2. Pick FullStory 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	Sessions
GET	Events
GET	Users
GET	Segments
GET	Search

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

GET

Sessions

Detail	Value
Operation ID	sessions_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 FullStory connection from the Connection dropdown.
3. In the Operation dropdown, select sessions_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 FullStory API reference.

GET

Events

Detail	Value
Operation ID	events_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 FullStory connection from the Connection dropdown.
3. In the Operation dropdown, select events_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 FullStory API reference.

GET

Users

Detail	Value
Operation ID	users_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 FullStory connection from the Connection dropdown.
3. In the Operation dropdown, select users_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 FullStory API reference.

GET

Segments

Detail	Value
Operation ID	segments_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 FullStory connection from the Connection dropdown.
3. In the Operation dropdown, select segments_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 FullStory API reference.

GET

Search

Detail	Value
Operation ID	search_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 FullStory connection from the Connection dropdown.
3. In the Operation dropdown, select search_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 FullStory API reference.