LavaTop icon

LavaTop

Sends data to LavaTop
Join our community

Actions8

Overview

This node integrates with the LavaTop service to manage subscriptions, specifically allowing deletion of a subscription. The "Subscription Delete" operation removes a subscription based on a contract ID and the subscriber's email address.

Common scenarios for this node include:

  • Automating subscription cancellations in workflows when a user requests to unsubscribe.
  • Cleaning up subscription records in LavaTop after a customer cancels their service.
  • Integrating subscription management into broader automation pipelines that handle billing or user account lifecycle.

Example use case: A workflow triggers when a user submits a cancellation form, passing their subscription contract ID and email to this node to delete their subscription from LavaTop automatically.

Properties

Name Meaning
Contract ID The parent contract ID (UUID) from the initial subscription purchase. Required to identify which subscription to delete.
Email Email address of the subscription owner. Used to verify and locate the subscription to delete.

Output

The node outputs JSON data representing the result of the delete operation. This typically includes confirmation of deletion or any error messages returned by the LavaTop API. There is no indication of binary data output.

Dependencies

  • Requires an API key credential for authenticating with the LavaTop service.
  • Needs proper configuration of the LavaTop API credentials within n8n.
  • Depends on the LavaTop API being accessible and operational.

Troubleshooting

  • Common issues:

    • Invalid or missing contract ID or email will cause the deletion to fail.
    • Authentication errors if the API key credential is not set or invalid.
    • Network or API downtime can prevent successful communication.

  • Error messages:

    • Errors related to "subscription not found" indicate incorrect contract ID or email.
    • Authentication errors suggest checking the API key credential setup.
    • Timeout or connection errors require verifying network connectivity and LavaTop API status.

Resolving these usually involves verifying input parameters, ensuring valid credentials, and confirming API availability.

Links and References

  • LavaTop official API documentation (not provided here; consult LavaTop developer resources)
  • n8n documentation on creating and using API credentials
  • UUID format reference for contract IDs

Discussion