Surense icon

Surense

Interact with Surense API

Actions36

Meeting → Delete a Meeting

AI-generated

Overview

The node named "Surense" provides integration with the Surense API, allowing users to perform various operations on multiple resources such as meetings, contacts, customers, and more. Specifically, for the "Delete a Meeting" operation under the "Meeting" resource, this node enables users to delete a meeting by specifying its unique identifier (UUID). This is useful in scenarios where meetings need to be programmatically removed from the system, such as cleaning up canceled or outdated meetings.

Practical examples include:

  • Automatically deleting meetings that were canceled via another system.
  • Removing test or placeholder meetings created during workflow automation.
  • Managing meeting lifecycle by deleting past meetings no longer needed.

Properties

Name Meaning
מזהה פגישה The meeting ID in UUID format used to identify which meeting to delete. Example: 123e4567-e89b-12d3-a456-426614174000

Output

The output of the node's execution is an array where each element corresponds to the result of the operation performed on each input item. For the "Delete a Meeting" operation, the output JSON typically contains confirmation of deletion or relevant response data from the Surense API. If an error occurs and the node is configured to continue on failure, the output will include an error message within the JSON structure.

No binary data output is indicated for this operation.

Dependencies

  • Requires an active connection to the Surense API.
  • Needs an API authentication token configured via OAuth2 credentials in n8n.
  • The node depends on internal helper modules for operation mapping and pagination but these are bundled internally.

Troubleshooting

  • Common issues:

    • Invalid or missing meeting ID (UUID) will cause the API call to fail.
    • Authentication errors if the OAuth2 token is expired or misconfigured.
    • Network connectivity problems preventing access to the Surense API.

  • Error messages:

    • Errors returned from the API will be surfaced in the node output if "Continue On Fail" is enabled.
    • Typical error messages might include "Meeting not found" if the ID does not exist, or "Unauthorized" if credentials are invalid.

  • Resolutions:

    • Verify the meeting ID is correct and in UUID format.
    • Ensure OAuth2 credentials are properly set up and valid.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion