Surense icon

Surense

Interact with Surense API

Actions36

Meeting → Create a Meeting

AI-generated

Overview

This node integrates with the Surense API to create meetings associated with customers. It allows users to specify detailed meeting information such as subject, type, host, timing, and attendees. This node is useful in scenarios where automated scheduling or logging of meetings is required within a workflow, for example:

  • Automatically creating a meeting when a new customer is onboarded.
  • Scheduling follow-up calls or appointments based on lead status changes.
  • Logging internal or external meetings with relevant notes and attendees.

Properties

Name Meaning
Subject The title or subject of the meeting.
Type The format of the meeting. Options are: פרונטלית (In-person), מקוונת (Online), טלפונית (Phone).
Host Name or ID The user who will host the meeting. Can be selected from a list of users or specified via an expression.
Customer ID The unique identifier (UUID) of the customer related to the meeting.
Start Date The start date and time of the meeting.
End Date The end date and time of the meeting.
Additional Parameters A collection of optional parameters including:
- Create Event: Whether to create a calendar event.
- Location: Physical or virtual location of the meeting.
- Notes: Additional notes about the meeting.
- Related Attendees: List of related attendee IDs (UUIDs).
- User Attendees: List of user attendees selected from users or by expression.

Output

The node outputs JSON data representing the created meeting details as returned by the Surense API. This typically includes identifiers, timestamps, and any metadata related to the meeting creation.

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 an API authentication token credential configured in n8n to connect to the Surense API.
  • Uses dynamic loading of users for host and attendee selection via API calls.
  • No other external dependencies are indicated.

Troubleshooting

  • Common Issues:

    • Invalid or missing Customer ID (UUID format) may cause API errors.
    • Selecting a Host or User Attendee that does not exist or lacks permissions can result in failures.
    • Incorrect date/time formats or logical errors like end date before start date may cause validation errors.

  • Error Messages:

    • Errors from the Surense API will be surfaced, often indicating invalid parameters or authentication issues.
    • If "continue on fail" is disabled, the node execution will stop on the first error; enabling it allows processing subsequent items.

  • Resolutions:

    • Ensure all required fields are correctly filled and formatted.
    • Verify API credentials and permissions.
    • Use expressions carefully to dynamically set IDs and dates.

Links and References

Discussion