Unipile icon

Unipile

Interact with Unipile API

Overview

This node integrates with the Unipile API to create calendar events. It allows users to specify a calendar and account, then send a JSON body describing the event details to be created in that calendar. This is useful for automating event creation workflows, such as scheduling meetings, reminders, or other calendar entries programmatically.

Practical examples include:

  • Automatically adding new project deadlines to a shared team calendar.
  • Creating event invitations based on form submissions or CRM updates.
  • Syncing events from other systems into a unified calendar managed by Unipile.

Properties

Name Meaning
Calendar ID The identifier of the calendar where the event will be created.
Account ID The identifier of the account under which the calendar event will be created (sent as a query parameter account_id).
Body (JSON) Raw JSON object containing the details of the event to create, such as title, time, attendees, etc.

Output

The node outputs JSON data representing the response from the Unipile API after creating the event. This typically includes details of the newly created event such as its unique ID, timestamps, and any metadata returned by the API.

No binary data output is indicated.

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 or invalid credentials: Ensure the API key credential is correctly set up and has permissions to create calendar events.
  • Invalid Calendar ID or Account ID: Verify that the provided IDs exist and are accessible by the authenticated user.
  • Malformed JSON in Body: The "Body (JSON)" property must contain valid JSON; otherwise, the API request will fail.
  • API errors: If the Unipile API returns errors, check the error message for details such as rate limits, permission issues, or invalid parameters.

Links and References

Discussion