Actions22
- Kanban Actions
- Meeting Actions
- Project Actions
- Team Actions
- User Actions
Overview
The node integrates with a Workspace API to create meetings within an organizational context. It allows users to specify detailed meeting information such as title, timing, organizer, attendees, content, and associated project. This node is useful for automating calendar or meeting management workflows, scheduling meetings programmatically, or integrating meeting creation into broader project or team management processes.
Practical examples include:
- Automatically scheduling project meetings when certain project milestones are reached.
- Creating recurring team meetings based on dynamic inputs.
- Integrating meeting creation into onboarding workflows by setting up initial meetings with new team members.
Properties
| Name | Meaning |
|---|---|
| Title | Title of the meeting (required). |
| Start Date | Start date and time of the meeting in ISO 8601 format (required). |
| End Date | End date and time of the meeting in ISO 8601 format (required). |
| Organisator ID | Unique identifier of the meeting organizer (required). |
| Attendee ID List | List of user IDs who will attend the meeting. Multiple attendees can be added. |
| Content | Content or agenda of the meeting. |
| Project ID | Unique identifier of the associated project. |
Output
The node outputs JSON data representing the created meeting object as returned by the Workspace API. This typically includes details such as meeting ID, title, start and end times, organizer, attendees, content, and any metadata related to the meeting.
If the node supports binary data output (not indicated here), it would represent attachments or related files, but this node primarily deals with JSON meeting data.
Dependencies
- Requires connection to the Workspace API via an API key credential and tenant identification.
- The node expects these credentials to be configured in n8n under the appropriate authentication method.
- The API base URL and headers are set dynamically from the provided credentials.
Troubleshooting
- Missing Required Fields: Errors may occur if required fields like Title, Start Date, End Date, or Organisator ID are not provided. Ensure all required properties are filled.
- Invalid Date Format: Start Date and End Date must be in valid ISO 8601 format; otherwise, the API may reject the request.
- Authentication Errors: If API key or tenant credentials are incorrect or missing, the node will fail to authenticate. Verify credentials configuration.
- API Limitations: The Workspace API might impose rate limits or restrictions on meeting creation; check API documentation if requests fail repeatedly.
- Attendee List Format: Ensure attendee IDs are correctly formatted strings; malformed lists may cause errors.
Links and References
- Refer to the Workspace API documentation for detailed information on meeting creation endpoints and field requirements.
- ISO 8601 date format specification: https://en.wikipedia.org/wiki/ISO_8601