Abstract

undefined

Detail	Value
Category	Design
Base URL	https://api.abstract.com
Authentication	Bearer Token
Endpoints	7
Connector key	abstract

Using Abstract in a workflow

1. Go to Connections and click New Connection.
2. Pick Abstract 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	List Projects
GET	List Branches
GET	List Commits
GET	List Files
GET	List Layers
GET	List Collections
GET	List Comments

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

GET

List Projects

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

GET

List Branches

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

GET

List Commits

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

GET

List Files

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

GET

List Layers

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

GET

List Collections

Detail	Value
Operation ID	list_collections_5
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Abstract connection from the Connection dropdown.
3. In the Operation dropdown, select list_collections_5.
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 Abstract API reference.

GET

List Comments

Detail	Value
Operation ID	list_comments_6
Method	GET
Path	``

Parameters

No parameters.

Using this endpoint in a workflow

1. Add an API Call node to your workflow.
2. Pick your Abstract connection from the Connection dropdown.
3. In the Operation dropdown, select list_comments_6.
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 Abstract API reference.