Teamwork
Collect read-only Teamwork project and task evidence for change, incident, access-request, or approval workflows. This is not a general task-automation connector.
What this connector audits
Checks this connector runs once it's connected. This is the full list; we don't claim coverage beyond what's implemented.
- Project and task evidence through Teamwork API read endpoints
- Customer-scoped workflow status or approval fields
- User inventory for access-review context
Endpoints this template queries
The exact Teamwork API endpoints called once connected. All read-only GET requests unless noted.
- GET/projects/api/v3/projects.json
- GET/projects/api/v3/tasks.json
- GET/people.json?pageSize=100
What we need
Field labels only. We never show secret values here. Credentials are encrypted at rest and used only to run the checks above.
- Base URL(prefilled: https://{yourSiteName}.teamwork.com)
- Endpoints (JSON)(prefilled: [ { "id": "projects", "name": "Projects", "path": "/projects/api/v3/projects.json" }, { "id": "tasks", "name": "Tasks", "path": "/projects/api/v3/tasks.json" }, { "id": "people", "name": "People", "path": "/people.json?pageSize=100" } ])
- Auth header name(prefilled: Authorization)
- Auth header value(secret credential)
Required
Optional
Which frameworks this evidence supports
Teamwork evidence feeds into controls for any framework you run that requires this check type; the same synced evidence can satisfy more than one framework's requirements instead of being collected per audit.
Don't see your system?
Tell us what you use and what it needs to prove. We'll follow up about adding a connector.
Wire in Teamwork evidence
Get a guided demo, or start by scanning any domain for free.