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
This node interacts with the Basecamp API to retrieve detailed information about a specific person within a Basecamp account. It is useful in scenarios where you need to fetch user details such as name, email, role, or other profile data programmatically from Basecamp. For example, it can be used in workflows that synchronize user data between Basecamp and other systems, or to trigger actions based on user attributes.
Properties
| Name | Meaning |
|---|---|
| Person Id | The unique numeric identifier of the person to retrieve from Basecamp. This property is required. |
Output
The node outputs JSON data representing the person’s details as returned by the Basecamp API. This typically includes fields such as the person's ID, name, email address, and possibly other profile-related information depending on the API response. The output does not include binary data.
Example structure of the json output (fields may vary):
{
"id": 123456,
"name": "John Doe",
"email_address": "john.doe@example.com",
"title": "Project Manager",
"avatar_url": "https://...",
...
}
Dependencies
- Requires an API authentication token configured via OAuth2 credentials for Basecamp.
- The node depends on the Basecamp API being accessible and the provided person ID existing within the authenticated Basecamp account.
- No additional environment variables are needed beyond the API credential setup.
Troubleshooting
- Invalid Person Id: If the person ID does not exist or is incorrect, the API will return an error indicating the resource was not found. Verify the person ID before running the node.
- Authentication Errors: If the OAuth2 token is missing, expired, or invalid, the node will fail with an authentication error. Re-authenticate or refresh the token as needed.
- API Rate Limits: Excessive requests may lead to rate limiting by Basecamp. Implement retry logic or reduce request frequency if this occurs.
- Network Issues: Connectivity problems can cause timeouts or failures. Ensure stable internet access and correct Basecamp API URL configuration.