Surense icon

Surense

Interact with Surense API

Actions36

Meeting Summary → Create a Meeting Summary

AI-generated

Overview

The node named "Surense" provides integration with the Surense API, enabling users to interact with various resources such as meetings, customers, contacts, and meeting summaries. Specifically, for the Meeting Summary resource and the Create a Meeting Summary operation, this node allows users to create detailed summaries of meetings including titles, background information, and recommendations.

This functionality is beneficial in scenarios where teams need to document meeting outcomes systematically, share insights with stakeholders, or maintain records for future reference. For example, after a client meeting, a user can create a meeting summary capturing key points and action items, which can then be stored or forwarded automatically.

Properties

Name Meaning
Customer ID The unique identifier (UUID format) of the customer associated with the meeting summary.
Title The title of the meeting summary.
Summary The main content of the meeting summary, including notes and recommendations.
Additional Parameters Optional extra fields; currently supports:
- Background Description and background information related to the meeting.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON object contains the result of the executed operation, typically the created meeting summary data returned from the Surense API.

If an error occurs during processing and the node is configured to continue on failure, the output will include an error message within the JSON under an error field for the respective item.

The node does not explicitly handle binary data output.

Dependencies

  • Requires an active connection to the Surense API.
  • Requires an API authentication token configured via OAuth2 credentials in n8n.
  • No additional external dependencies are indicated beyond the bundled Surense API modules.

Troubleshooting

  • Common Issues:

    • Invalid or missing Customer ID (UUID format) may cause API errors.
    • Missing required fields like Title or Summary will likely result in validation errors.
    • Network or authentication failures if the OAuth2 credential is not properly set up or expired.

  • Error Messages:

    • Errors thrown by the Surense API will be surfaced in the node's output if "Continue On Fail" is enabled.
    • Typical messages might include invalid parameter formats or authorization failures.

  • Resolutions:

    • Verify that all required fields are correctly filled and formatted.
    • Ensure the OAuth2 credential is valid and has necessary permissions.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion