Actions80
- Card Tables Actions
- Forwards Actions
- Events Actions
- Recordings Actions
- Projects Actions
- People Actions
- Chatbots Actions
- Webhooks Actions
- Attachments Actions
- Templates Actions
- Uploads Actions
- Documents Actions
- Lineup Markers Actions
- Subscriptions Actions
- Schedules Actions
- Schedule Entries Actions
- Todo Sets Actions
- Todo Lists Actions
- Todos Actions
Overview
The "Update Project Access" operation for the "People" resource allows users to manage access permissions of people on a specific project within Basecamp. This node is useful when you want to programmatically grant or revoke access for multiple people, or create new people entries associated with a project.
Typical use cases include:
- Adding team members to a project by granting them access.
- Removing people who no longer need access by revoking their permissions.
- Creating new people records and assigning them to a project in one step.
For example, a project manager could automate onboarding by creating new people and granting them access to relevant projects simultaneously.
Properties
| Name | Meaning |
|---|---|
| Project Id | The numeric identifier of the project for which access is being updated (required). |
| Grant | JSON array of people IDs to be granted access to the specified project. |
| Revoke | JSON array of people IDs to be revoked access from the specified project. |
| Create | JSON array of new people objects to be created and added to the project. |
Output
The node outputs JSON data representing the result of the update operation. This typically includes confirmation of the changes made to project access, such as lists of people granted or revoked access, and details of any newly created people.
No binary data output is indicated.
Dependencies
- Requires an API key credential for authenticating with the Basecamp API.
- The node uses the Basecamp API endpoint constructed with the user's Basecamp account ID.
- Proper configuration of the Basecamp OAuth2 credentials in n8n is necessary.
Troubleshooting
- Invalid Project Id: If the project ID does not exist or is incorrect, the API will likely return an error. Verify the project ID before running the node.
- Malformed JSON in Grant/Revoke/Create: Since these properties expect JSON arrays, invalid JSON syntax will cause parsing errors. Ensure the input is valid JSON.
- Insufficient Permissions: The API key used must have permission to modify project access; otherwise, authorization errors will occur.
- Empty Arrays: Passing empty arrays for grant/revoke/create may result in no changes. Confirm that the arrays contain intended values.