Skip to content
For LLMsView as Markdown·

FreshBooks

undefined

DetailValue
CategoryAccounting
Base URLhttps://api.freshbooks.com
AuthenticationOAuth2
Endpoints5
Connector keyfreshbooks

Using FreshBooks in a workflow

  1. Go to Connections and click New Connection.
  2. Pick FreshBooks 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 Clients
GET Invoices
GET Expenses
GET Payments
GET Time Entries

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

GET

Clients

DetailValue
Operation IDclients_0
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Invoices

DetailValue
Operation IDinvoices_1
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Expenses

DetailValue
Operation IDexpenses_2
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Payments

DetailValue
Operation IDpayments_3
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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

GET

Time Entries

DetailValue
Operation IDtime_entries_4
MethodGET
Path``

Parameters

No parameters.

Using this endpoint in a workflow

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