Vidext - Session End Trigger icon

Vidext - Session End Trigger

Activates when a session ends for a Deck ID configured. Automatically manages the webhook subscription with the Vidext API

Overview

This node triggers a workflow when a session ends for a specific presentation deck in Vidext. It automatically manages webhook subscriptions with the Vidext API to listen for "session end" events related to the configured Deck ID.

Common scenarios:

  • Automating follow-up actions after a viewer finishes watching a Vidext presentation.
  • Logging or analytics workflows that track session completions.
  • Sending notifications or updating CRM systems when a session ends.

Practical example:
You configure the node with a Deck ID of a Vidext presentation. When any user finishes their session viewing that deck, Vidext sends an event to this node’s webhook, triggering downstream workflow steps such as sending a thank-you email or updating a database record.

Properties

Name Meaning
Deck ID The unique identifier of the Vidext presentation (deck) for which session end events are listened to. This is required.
Internal Vidext Subscription ID Hidden property used internally to store the subscription ID returned by Vidext when creating the webhook subscription. Not user-configurable.

Output

The node outputs JSON data representing the session end event(s) received from Vidext. The output is always an array of JSON objects, each corresponding to one session end event payload sent by Vidext.

  • The exact structure of the JSON depends on Vidext's webhook payload but typically includes details about the session and deck.
  • No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the Vidext API.
  • The node uses the Vidext API endpoint (default https://vidext.ai) to manage webhook subscriptions.
  • The workflow must be active and publicly accessible so Vidext can send webhook POST requests to the node’s webhook URL.
  • Proper configuration of the Vidext API key credential in n8n is necessary.

Troubleshooting

  • Invalid or missing API Key in webhook request:
    The node checks the x-api-key header in incoming webhook requests against the stored API key. If they do not match, it returns a 401 Unauthorized error.
    Resolution: Ensure the Vidext service is configured to send the correct API key in webhook requests.

  • Webhook creation errors:
    Errors during subscription creation may include:

    • 400 Bad Request: Invalid parameters (e.g., missing Deck ID).
    • 401 Unauthorized: Incorrect API key.
    • 409 Conflict: Webhook already exists for the Deck ID.
    • 422 Unprocessable Entity: Invalid webhook type or parameters.
    • 500 Internal Server Error: Vidext server issues.
      Resolution: Verify Deck ID correctness, API key validity, and check Vidext service status.

  • Webhook URL issues:
    If the workflow is not active or the webhook URL cannot be retrieved, subscription creation will fail.
    Resolution: Activate the workflow and ensure it has a valid webhook URL.

  • Subscription cancellation warnings:
    If no subscription ID is found when trying to unsubscribe, a warning is logged but no error is thrown.

Links and References

Discussion