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
The "Update a Project" operation in this Basecamp node allows users to modify details of an existing project within their Basecamp account. This is useful for keeping project information current, such as changing the project name, updating its description, adjusting access policies, or modifying schedule attributes.
Typical scenarios include:
- Renaming a project after rebranding or scope changes.
- Adding or updating a project description to provide more context.
- Changing admissions settings to control who can access the project.
- Updating scheduling details related to the project timeline.
For example, a user might update a project's name and description after receiving new client requirements, ensuring all team members see the latest information.
Properties
Name | Meaning |
---|---|
projectId | The unique numeric identifier of the project to update; used in the API endpoint path. |
Project Name | The new name for the project; this is a required string field. |
Project Fields | Additional optional fields to update: |
- Description | Optional textual description providing more details about the project. |
- Admissions | String specifying the access policy for the project within the same account. |
- Schedule Attributes | Optional JSON string representing schedule-related attributes for the project. |
Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) or just the response body. |
Output
The node outputs JSON data representing the updated project resource as returned by the Basecamp API. If the "Return Full Response" option is enabled, the output includes the entire HTTP response object with status code, headers, and body; otherwise, only the response body (the updated project data) is returned.
No binary data output is involved in this operation.
Dependencies
- Requires an active connection to the Basecamp API using OAuth2 authentication with appropriate permissions to update projects.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies are needed beyond the Basecamp API and valid credentials.
Troubleshooting
- Invalid projectId: If the provided project ID does not exist or is incorrect, the API will likely return a 404 Not Found error. Verify the project ID before running the node.
- Insufficient permissions: If the OAuth2 token lacks permission to update projects, the API may return a 403 Forbidden error. Ensure the connected account has adequate rights.
- Malformed JSON in Schedule Attributes: Since schedule attributes expect a JSON string, invalid JSON formatting could cause request failures. Validate JSON syntax before submission.
- Missing required fields: The "Project Name" and "projectId" are required; omitting them will prevent successful execution.
- API rate limits: Frequent updates may hit Basecamp API rate limits, resulting in throttling errors. Implement retries or backoff strategies if necessary.