Skip to content
For LLMsView as Markdown·

Buildium

undefined

DetailValue
CategoryReal Estate
Base URLhttps://api.buildium.com/v1
AuthenticationAPI Key
Endpoints7
Connector keybuildium

Using Buildium in a workflow

  1. Go to Connections and click New Connection.
  2. Pick Buildium 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

EndpointSummary
GET Rentals
GET Units
GET Leases
GET Tenants
GET Work Orders
GET Transactions
GET Vendors

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

GET

Rentals

DetailValue
Operation IDrentals_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Units

DetailValue
Operation IDunits_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Leases

DetailValue
Operation IDleases_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Tenants

DetailValue
Operation IDtenants_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Work Orders

DetailValue
Operation IDwork_orders_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Transactions

DetailValue
Operation IDtransactions_5
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Vendors

DetailValue
Operation IDvendors_6
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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