Appearance
Teamwork
undefined
| Detail | Value |
|---|---|
| Category | Project Management |
| Base URL | https://{site_name}.teamwork.com |
| Authentication | Bearer Token |
| Endpoints | 6 |
| Connector key | teamwork |
Using Teamwork in a workflow
- Go to Connections and click New Connection.
- Pick Teamwork 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 | List Projects |
GET | Create Task |
GET | Get Task |
GET | Log Time |
GET | List People |
GET | List Milestones |
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
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
list_projects_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 Teamwork API reference.
GET
Create Task
| Detail | Value |
|---|---|
| Operation ID | create_task_1 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
create_task_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 Teamwork API reference.
GET
Get Task
| Detail | Value |
|---|---|
| Operation ID | get_task_2 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
get_task_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 Teamwork API reference.
GET
Log Time
| Detail | Value |
|---|---|
| Operation ID | log_time_3 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
log_time_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 Teamwork API reference.
GET
List People
| Detail | Value |
|---|---|
| Operation ID | list_people_4 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
list_people_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 Teamwork API reference.
GET
List Milestones
| Detail | Value |
|---|---|
| Operation ID | list_milestones_5 |
| Method | GET |
| Path | `` |
Parameters
No parameters.
Using this endpoint in a workflow
- Add an API Call node to your workflow.
- Pick your Teamwork connection from the Connection dropdown.
- In the Operation dropdown, select
list_milestones_5. - 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 Teamwork API reference.