Surense icon

Surense

Interact with Surense API

Actions36

Document → Upload Har Bituach

AI-generated

Overview

The node named "Surense" provides integration with the Surense API, allowing users to interact with various resources such as activities, contacts, customers, documents, and more. Specifically, for the Document resource and the Upload Har Bituach operation, this node enables uploading a Har Bituach file (likely an insurance or security-related document) associated with a customer identified by a UUID.

This operation is useful in scenarios where you need to programmatically attach official documents to customer records within the Surense system, automating workflows related to document management, compliance, or record keeping.

Example use cases:

  • Uploading insurance certificates or security clearance documents for customers.
  • Automating document archival processes linked to customer profiles.
  • Integrating document uploads into broader CRM or ERP workflows.

Properties

Name Meaning
מזהה לקוח (id) Customer ID in UUID format identifying the customer to whom the Har Bituach document belongs.
Binary Property The name of the binary data field that contains the actual Har Bituach file to be uploaded. Default is "data".

Output

The node outputs JSON data representing the result of the upload operation. This typically includes confirmation details from the Surense API about the uploaded document, such as identifiers, status, or metadata returned by the service.

If the node supports binary data output (not explicitly shown here), it would relate to returning the uploaded file or related binary content, but based on the provided code and properties, the main output is JSON confirming the upload.

Dependencies

  • Requires an active connection to the Surense API via OAuth2 authentication (an API key credential).
  • The node depends on the Surense API being accessible and properly configured.
  • No additional external services are indicated beyond the Surense API.
  • Proper configuration of the OAuth2 credentials in n8n is necessary for successful execution.

Troubleshooting

  • Common issues:

    • Invalid or missing Customer ID (UUID): Ensure the id property is correctly formatted as a UUID.
    • Missing or incorrect binary property name: Verify that the binary data field name matches the input binary data.
    • Authentication failures: Check that the OAuth2 credentials are valid and have not expired.
    • API connectivity issues: Confirm network access to the Surense API endpoint.

  • Error messages:

    • Errors thrown by the API will be surfaced in the node's output if "Continue On Fail" is enabled; otherwise, they will stop execution.
    • Typical errors include invalid parameters, unauthorized access, or file upload failures.

  • Resolution tips:

    • Double-check all required fields before running the node.
    • Use the "Continue On Fail" option during testing to capture error details without stopping the workflow.
    • Review API documentation or logs for specific error codes returned by Surense.

Links and References

Discussion