Actions76
- Campfire Actions
- Card Table Actions
- Chatbot Actions
- Client Approval Actions
- Client Correspondence Actions
- Client Reply Actions
- Client Visibility Actions
- Comment Actions
- Document Actions
- Event Actions
- Forward Actions
- Inbox Actions
- Inbox Reply Actions
- Lineup Marker Actions
- Message Actions
- Message Board Actions
- Message Type Actions
- Person Actions
- Project Actions
- Question Actions
- Question Answer Actions
- Questionnaire Actions
- Recording Actions
Overview
This node interacts with the Basecamp API to retrieve people associated with a specific project. It is useful in scenarios where you need to list or manage team members involved in a project, such as for reporting, notifications, or access control purposes.
For example, you might use this node to:
- Fetch all users assigned to a project to send them updates.
- Display project team members in a dashboard.
- Automate workflows based on project personnel changes.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric identifier of the project from which to retrieve people. |
| Return All Results | Whether to fetch all people associated with the project (true) or limit results (false). |
| Return Full Response | Whether to return the complete HTTP response including status code and headers, or just the body. |
Output
The node outputs JSON data representing the people associated with the specified project. This typically includes an array of person objects with details such as names, email addresses, roles, and other relevant metadata.
If "Return Full Response" is enabled, the output will include the full HTTP response object containing status code, headers, and body.
The node does not output binary data.
Dependencies
- Requires an API authentication token configured via OAuth2 credentials to access the Basecamp API.
- Needs the Basecamp account ID to construct the API base URL.
- The node depends on the Basecamp API being accessible and the user having appropriate permissions to read project people.
Troubleshooting
Common Issues:
- Invalid or missing Project ID will cause the API call to fail.
- Insufficient permissions or invalid API credentials may result in authorization errors.
- Network connectivity issues can prevent successful API requests.
Error Messages:
- 404 Not Found: The specified project ID does not exist or is inaccessible.
- 401 Unauthorized: Authentication failed; check API credentials.
- 429 Too Many Requests: Rate limits exceeded; retry after some time.
Resolutions:
- Verify the Project ID is correct and the project exists.
- Ensure the API key or OAuth2 token is valid and has required scopes.
- Handle pagination properly if many people are returned by enabling "Return All Results".
- Check network connectivity and proxy settings if applicable.