Actions85
- Account Actions
- Calendar Actions
- Email Actions
- LinkedIn Actions
- Close Job Posting
- Create Job Posting
- Download Applicant Resume
- Edit Job Posting
- Endorse Skill
- Get Company Profile
- Get Hiring Project by ID
- Get Hiring Projects
- Get Inmail Balance
- Get Job Applicant
- Get Job Applicants
- Get Job Offer
- Get Job Postings
- Get Raw Data
- Perform Action on Member
- Publish Job Posting
- Search
- Search Parameters
- Solve Job Publishing Checkpoint
- Messaging Actions
- Post Actions
- User Actions
- Webhook Actions
Overview
The node interacts with the Unipile API to retrieve calendar information. Specifically, the "Get Calendar" operation fetches details about a particular calendar associated with an account. This is useful in scenarios where you want to integrate calendar data from Unipile into your workflows, such as displaying upcoming events, syncing calendars, or managing scheduling tasks.
Practical examples include:
- Fetching a user's calendar details to display in a dashboard.
- Integrating calendar data into automated email reminders.
- Syncing calendar events with other applications or services.
Properties
| Name | Meaning |
|---|---|
| Calendar ID | The unique identifier of the calendar you want to retrieve. |
| Account ID | The unique identifier of the account that owns the calendar. This is sent as a query parameter named account_id. |
Output
The node outputs JSON data representing the calendar details retrieved from the Unipile API. The exact structure depends on the API response but typically includes calendar metadata such as its name, description, timezone, and possibly event summaries.
No binary data output is indicated by the source code.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials (likely an environment variable or credential setting).
- The node sends HTTP requests with headers specifying JSON content type and acceptance.
Troubleshooting
- Missing or invalid API credentials: Ensure the API key credential is correctly set up and has access rights to the Unipile API.
- Invalid Calendar ID or Account ID: Verify that the provided IDs exist and are correct; otherwise, the API may return errors or empty results.
- Network issues or incorrect base URL: Confirm that the base URL configured in credentials is reachable and correct.
- API rate limits or permissions: If the API returns permission errors, check the API key's scopes and usage limits.
Common error messages would likely relate to authentication failures, resource not found, or bad request due to missing parameters.
Links and References
- Unipile API Documentation (Assumed official API docs)
- n8n documentation on Creating Custom Nodes