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 retrieve information about a specific person within a Basecamp account. The "Get Person" operation under the "People" resource allows users to fetch detailed data about an individual by specifying their unique person ID. This is useful in scenarios where you need to access user details for project management, reporting, or integration purposes.
For example, you might use this node to:
- Retrieve contact information of a team member.
- Fetch user details to sync with another system.
- Display user profiles dynamically in a workflow.
Properties
| Name | Meaning |
|---|---|
| Person Id | The unique numeric identifier of the person to retrieve from Basecamp. |
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 name, email, role, and other profile information. The output does not include binary data.
Example structure (simplified):
{
"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 being valid within the authenticated Basecamp account.
Troubleshooting
- Invalid Person Id: If the person ID does not exist or is incorrect, the API will return an error. Verify the ID before running the node.
- Authentication Errors: Ensure that the OAuth2 credentials are correctly set up and have sufficient permissions to access people data.
- Network Issues: Connectivity problems can cause request failures; check your network and Basecamp service status.
- API Rate Limits: Excessive requests may be throttled by Basecamp; consider adding delays or handling rate limit errors gracefully.