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 operation updates an existing question within a specified project in Basecamp. It allows users to modify the question's content, schedule, and the group of people who will be asked to answer it. This is useful for managing survey or feedback questions dynamically, such as correcting typos, changing the timing of when a question is presented, or adjusting the audience.
Practical examples include:
- Updating a question's text after receiving feedback.
- Changing the schedule for when a question should be asked.
- Modifying the list of participants who will receive the question.
Properties
| Name | Meaning |
|---|---|
| Project ID | The numeric ID of the project (bucket) where the question resides; used in the API path. |
| questionId | The numeric ID of the question to update; used in the API path. |
| Content | The updated text content of the question, supports HTML formatting. |
| Question Fields | Additional fields related to the question: |
| - Schedule | A string representing the schedule for the question (e.g., when it should be asked). |
| - Presenting Group JSON | A JSON string array of person IDs who will be asked to answer the question. |
| 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 the response from the Basecamp API after updating the question. By default, it returns only the response body containing the updated question data. If "Return Full Response" is enabled, it outputs the entire HTTP response including status code, headers, and body.
The output json field structure corresponds to the updated question object returned by the Basecamp API, which typically includes properties like question ID, content, schedule, presenting group, timestamps, and other metadata.
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 questions.
- The node expects the Basecamp account ID to be configured in credentials to construct the API base URL.
- No additional external dependencies beyond the Basecamp API and n8n's OAuth2 credential setup.
Troubleshooting
- Invalid Project or Question ID: Errors may occur if the provided project ID or question ID does not exist or the authenticated user lacks access. Verify IDs and permissions.
- Malformed JSON in Presenting Group: The "Presenting Group JSON" must be a valid JSON array string of person IDs. Invalid JSON will cause request failures.
- Missing Required Fields: Ensure that required fields like Project ID, questionId, and Content are provided; otherwise, the API call will fail.
- API Authentication Errors: If the OAuth2 token is expired or invalid, authentication errors will occur. Refresh or reauthorize credentials as needed.
- Return Full Response Misuse: Enabling "Return Full Response" changes the output format; downstream nodes expecting only the body might fail if not adjusted accordingly.