Appearance
FreshBooks
undefined
| Detail | Value |
|---|---|
| Category | Accounting |
| Base URL | https://api.freshbooks.com |
| Authentication | OAuth2 |
| Endpoints | 5 |
| Connector key | freshbooks |
Using FreshBooks in a workflow
- Go to Connections and click New Connection.
- Pick FreshBooks from the marketplace.
- Enter your credentials (see Authentication above for what's expected).
- In a workflow, drop an API Call node and select this connection.
- Pick the operation you need from the Operation dropdown — the full list is below.
Available endpoints
| Endpoint | Summary |
|---|---|
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
| Detail | Value |
|---|---|
| Operation ID | clients_0 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your FreshBooks connection from the Connection dropdown.
- In the Operation dropdown, select
clients_0. - 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
| Detail | Value |
|---|---|
| Operation ID | invoices_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your FreshBooks connection from the Connection dropdown.
- In the Operation dropdown, select
invoices_1. - 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
| Detail | Value |
|---|---|
| Operation ID | expenses_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your FreshBooks connection from the Connection dropdown.
- In the Operation dropdown, select
expenses_2. - 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
| Detail | Value |
|---|---|
| Operation ID | payments_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your FreshBooks connection from the Connection dropdown.
- In the Operation dropdown, select
payments_3. - 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
| Detail | Value |
|---|---|
| Operation ID | time_entries_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your FreshBooks connection from the Connection dropdown.
- In the Operation dropdown, select
time_entries_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.