Actions80
- Todos Actions
- 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
Overview
This node interacts with the Basecamp API to update project access for people. Specifically, it allows you to modify which people have access to a given project by granting access to some, revoking access from others, and optionally creating new people entries. This is useful in scenarios where you need to manage team permissions dynamically, such as onboarding new members, removing former collaborators, or adjusting access rights based on project needs.
Practical examples:
- Granting access to a list of new team members for a specific project.
- Revoking access from people who no longer should have project permissions.
- Creating new people records while simultaneously updating their project access.
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 potentially granted access. |
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. The exact structure depends on the Basecamp API response but generally reflects the updated state of project access.
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 using the Basecamp account ID from credentials.
- Proper configuration of the API authentication and Basecamp account ID is necessary within n8n.
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, ensure the input is valid JSON. Parsing errors will cause failures.
- Insufficient Permissions: The API key used must have sufficient permissions to modify project access; otherwise, authorization errors may occur.
- Empty Arrays: Passing empty arrays for grant/revoke/create means no changes for that category; ensure this matches your intent.
- API Rate Limits: Frequent updates might hit API rate limits; handle such errors by retrying after some delay.