Actions36
- Activity Actions
- Contact Actions
- Customer Actions
- Data Proxy Actions
- Document Actions
- Employer Actions
- Lead Actions
- Meeting Actions
- Meeting Summary Actions
- Report Actions
- Workflow Actions
Meeting → Update a Meeting
AI-generatedOverview
This node integrates with the Surense API to update details of an existing meeting. It allows users to modify various attributes of a meeting such as its subject, type, status, attendees, location, and timing. This is useful in scenarios where meeting information changes after creation, for example, rescheduling a meeting, updating participants, or changing the meeting status.
Practical examples:
- Updating the start and end time of a scheduled meeting.
- Changing the meeting location from physical to online.
- Adding or removing attendees from the meeting.
- Modifying the meeting notes or status (e.g., marking it as canceled).
Properties
| Name | Meaning |
|---|---|
| מזהה פגישה | Meeting ID in UUID format; identifies which meeting to update. |
| Additional Parameters | A collection of optional fields to update various meeting details: |
| - הערות | Meeting notes (text). |
| - מזהה מארח | Host ID in UUID format. |
| - מיקום | Meeting location (string). |
| - משתתפים | User attendees: multiple user attendee IDs (UUIDs) to add or update. |
| - משתתפים קשורים | Related attendees: multiple related attendee IDs (UUIDs). |
| - נושא הפגישה | Meeting subject (string). |
| - סוג הפגישה | Meeting type; options are: פגישה פרונטלית (1), פגישה מקוונת (2), פגישה טלפונית (3). |
| - סטטוס פגישה | Meeting status; options include: מתוכננת (1), התקיימה (2), בוטלה (3), נדחית על ידי הלקוח (4), נדחית על ידי הסוכנות (5). |
| - סטטוס תזכורת | Reminder status; options include: תוזכרה - מאושרת (1), תוזכרה - נדחית (2), תוזכרה - מבוטלת (3), אין מענה - להמשך טיפול (4), אין מענה - ביטול (5). |
| - תאריך התחלה | Start date and time of the meeting (datetime). |
| - תאריך סיום | End date and time of the meeting (datetime). |
Output
The node outputs an array of JSON objects representing the updated meeting(s). Each output item corresponds to one input item processed. The JSON structure contains the updated meeting data returned by the Surense API, reflecting all changes made.
If errors occur during execution and "Continue On Fail" is enabled, the output will include error messages associated with the respective input item.
No binary data output is indicated.
Dependencies
- Requires an active connection to the Surense API via an OAuth2 API credential.
- The node depends on the Surense API being accessible and properly authenticated.
- No additional environment variables or external services beyond the Surense API are required.
Troubleshooting
Common issues:
- Invalid or missing Meeting ID (UUID format) will cause the update to fail.
- Providing invalid UUIDs for attendees or host may result in errors.
- Incorrect date/time formats for start or end dates can cause request rejection.
- Network or authentication failures with the Surense API will prevent updates.
Error messages:
- Errors returned from the API typically include descriptive messages about invalid parameters or authorization failures.
- If "Continue On Fail" is disabled, the node will stop execution on the first error.
- To resolve errors, verify that all required fields are correctly formatted and that the API credentials are valid.
Links and References
- Surense API documentation (not provided here, but recommended to consult for detailed API specs).
- n8n documentation on creating and using custom nodes with OAuth2 authentication.