Actions119
- 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
- Schedule Actions
- Schedule Entry Actions
- Template Actions
- Todo Actions
- Todolist Actions
- Todolist Group Actions
- Todoset Actions
- Upload Actions
- Vault Actions
- Webhook Actions
Overview
This node integrates with the Basecamp API to update an existing Template resource. It allows users to modify specific fields of a template, such as its name and description, by specifying the template's unique identifier. This operation is useful in scenarios where templates need to be maintained or adjusted dynamically within automated workflows, for example, updating project templates to reflect new standards or correcting template details without manual intervention.
Practical examples include:
- Automatically updating a project template’s description when organizational guidelines change.
- Renaming a template based on external input or triggers from other systems.
- Integrating template updates into larger automation flows that manage project setups.
Properties
| Name | Meaning |
|---|---|
| templateId | The unique numeric identifier of the template to update. Used in the API endpoint path. |
| Template Fields | A collection of fields to update on the template. Options include: |
| - Name: The new name for the template (string). | |
| - Description: The new description for the template (string). | |
| Return Full Response | Boolean flag indicating whether to return the full HTTP response (status code, headers, body) instead of only the response body. |
Output
The node outputs JSON data representing the updated template object returned by the Basecamp API. If the "Return Full Response" property is enabled, the output will include the entire HTTP response, including status code and headers, which can be useful for debugging or advanced handling.
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 templates.
- The node expects the Basecamp account ID to be configured as part of the credentials to construct the API base URL.
- No additional external dependencies are required beyond the Basecamp API access.
Troubleshooting
- Invalid templateId: If the provided template ID does not exist or is incorrect, the API will likely return a 404 Not Found error. Verify the template ID before running the node.
- Insufficient permissions: Errors related to authorization may occur if the API token lacks rights to update templates. Ensure the connected API credentials have the necessary scopes.
- Malformed input fields: Providing invalid data types or empty required fields in "Template Fields" may cause validation errors. Double-check field values conform to expected types.
- API rate limits: Frequent updates might hit Basecamp API rate limits, resulting in throttling errors. Implement retry logic or reduce request frequency if needed.