Surense icon

Surense

Interact with Surense API

Actions36

Data Proxy → Create Data Proxy

AI-generated

Overview

This node integrates with the Surense API, specifically providing functionality to create a Data Proxy URL for a customer. The "Create Data Proxy" operation allows users to generate a proxy link related to a specific customer identified by their Customer ID (UUID). This can be useful in scenarios where you need to securely share or access customer-related data through a proxy mechanism.

Practical examples include:

  • Generating a secure data proxy URL to share customer information with authorized parties.
  • Including specific powers of attorney documents (insurance mountain, policies, clearing) as part of the data proxy.
  • Adding additional contact parameters such as cell number or email to customize the proxy creation request.

Properties

Name Meaning
Customer ID The unique identifier (UUID format) of the customer for whom the data proxy URL is created.
כלול ייפוי כוח הר הביטוח (נספח ה') Boolean flag indicating whether to include the insurance mountain power of attorney (Appendix H).
כלול ייפוי כוח פוליסות (נספח ב') Boolean flag indicating whether to include the policies power of attorney (Appendix B).
כלול ייפוי כוח מסלקה (נספח א') Boolean flag indicating whether to include the clearing power of attorney (Appendix A).
Additional Parameters Collection of optional parameters to further specify the request:
- Cell Number Optional cell phone number associated with the request.
- Email Optional email address associated with the request.
- Licensee Name or ID Select or specify a licensee by name or ID from a list or expression.
- Swiftness Account Name or ID Select or specify a swiftness account by name or ID from a list or expression.

Output

The node outputs an array of JSON objects corresponding to each input item processed. Each output JSON object contains the result of the "Create Data Proxy" operation, typically including the generated data proxy URL and any related metadata returned by the Surense API.

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

No binary data output is indicated for this operation.

Dependencies

  • Requires an API authentication token credential for Surense API access.
  • Uses several helper modules internally for operation execution and pagination.
  • The node depends on external API endpoints provided by Surense to perform the data proxy creation.
  • Some properties load options dynamically via methods that fetch licensees and swiftness accounts lists.

Troubleshooting

  • Common Issues:

    • Invalid or missing Customer ID (UUID) will cause the operation to fail.
    • Incorrect or missing API credentials will prevent successful API calls.
    • Selecting invalid licensee or swiftness account IDs may lead to errors.
    • Network connectivity issues can cause timeouts or failures.

  • Error Messages:

    • Errors returned from the Surense API are surfaced in the output JSON under the error key if "Continue On Fail" is enabled.
    • Authentication errors indicate problems with the API key or OAuth2 token.
    • Validation errors usually relate to missing required fields or invalid parameter formats.

  • Resolution Tips:

    • Verify the Customer ID is correctly formatted as a UUID.
    • Ensure valid and active API credentials are configured in n8n.
    • Use the dynamic option loaders to select valid licensee and swiftness account values.
    • Check network connectivity and API endpoint availability.

Links and References

Discussion