Wave Accounting

undefined

Detail	Value
Category	Accounting
Base URL	https://gql.waveapps.com/graphql/public
Authentication	OAuth2
Endpoints	5
Connector key	wave

Using Wave Accounting in a workflow

1. Go to Connections and click New Connection.
2. Pick Wave Accounting 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	Businesses
GET	Customers
GET	Invoices
GET	Products
GET	Accounts

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

GET

Businesses

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

GET

Customers

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

GET

Invoices

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

GET

Products

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

GET

Accounts

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