Actions68
- Recordings Actions
- Card Tables Actions
- Forwards Actions
- Events 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
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 any newly created people records. There is no indication that binary data is output by this node.
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.
- No other external dependencies are indicated.
Troubleshooting
- Common issues:
- Invalid or missing project ID can cause the API call to fail.
- Malformed JSON in the "Grant", "Revoke", or "Create" fields may lead to parsing errors.
- Insufficient permissions or invalid API credentials will result in authentication errors.
- Error messages:
- Authentication failures usually indicate problems with the provided API key or OAuth token.
- Validation errors from the API may occur if the people IDs do not exist or the project ID is incorrect.
- Resolutions:
- Verify that the project ID is correct and exists in Basecamp.
- Ensure JSON arrays for grant/revoke/create are properly formatted.
- Confirm that the API credentials are valid and have sufficient permissions.
Links and References
- Basecamp API Documentation
- n8n documentation on Using API Credentials