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 allows editing an existing calendar event via the Unipile API. It is useful for updating event details such as time, description, or other metadata after the event has been created. Typical use cases include modifying meeting times, correcting event information, or adding additional data to an event in a connected calendar system.
For example, you might use this node to update the title or location of a scheduled meeting based on user input or external triggers.
Properties
| Name | Meaning |
|---|---|
| Event ID | The unique identifier of the calendar event to be edited. |
| Calendar ID | The identifier of the calendar containing the event. |
| Account ID | The identifier of the account owning the calendar; sent as a query parameter account_id. |
| Body (JSON) | Raw JSON object representing the fields and values to update in the event. |
Output
The node outputs the response from the Unipile API after attempting to edit the event. This output is structured as JSON and typically contains the updated event data or confirmation of the successful update.
If the API supports it, binary data output is not indicated for this operation.
Dependencies
- Requires an API key credential for authenticating with the Unipile API.
- The base URL for API requests is configured via credentials.
- The node sends HTTP requests with JSON payloads to the Unipile service.
Troubleshooting
- Missing Required Fields: Ensure that
Event ID,Calendar ID, andAccount IDare provided; these are mandatory. - Invalid JSON in Body: The
Body (JSON)property must contain valid JSON. Malformed JSON will cause request failures. - Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- API Endpoint Issues: Confirm that the base URL in credentials is correct and reachable.
- Event Not Found: If the event ID does not exist, the API may return an error indicating the event was not found.
Links and References
- Unipile API Documentation (hypothetical link)
- n8n documentation on HTTP Request Node for understanding how API calls are made within nodes.