Masumi Paywall Trigger v1.0.1 icon

Masumi Paywall Trigger v1.0.1

Triggers workflow via Masumi REST endpoints

Masumi Paywall Trigger v1.0.1

AI-generated

Overview

This node acts as a trigger for workflows via Masumi REST endpoints. It listens for HTTP requests on specified endpoints related to Masumi paywall services, such as checking service availability, job status, retrieving input schemas, starting jobs, and internal polling triggers. It is useful for integrating Masumi paywall events into automated workflows, enabling real-time responses to service health checks, job management, and polling triggers.

Use Case Examples

  1. Trigger a workflow when the Masumi service availability is checked to monitor system health.
  2. Start a workflow when a new job is initialized via the Masumi paywall system.
  3. Respond to internal polling triggers to manage payment status updates automatically.

Properties

Name Meaning
Endpoint Specifies which Masumi REST endpoint the webhook will listen to, such as availability check, job status, input schema retrieval, job start, or internal polling trigger.
Path Custom path segment for the webhook URL. If empty, an auto-generated webhook ID is used. For example, setting 'masumi' creates URLs like /webhook/masumi/availability.
HTTP Method The HTTP method used by the webhook, automatically set to POST for start_job and start_polling endpoints, and GET for others.
Response Mode Determines when the webhook sends a response: immediately with fixed data, when the last node finishes, or using a Respond to Webhook node.

Output

JSON

  • endpoint - The endpoint that triggered the webhook.
  • error - Error type if an error occurred during webhook processing.
  • message - Error message describing the issue.
  • requestUrl - The full URL of the incoming webhook request.
  • method - HTTP method of the incoming request.
  • timestamp - Timestamp when the webhook was processed.
  • debug
    • webhookPath - Configured webhook path parameter for debugging.
    • headers - Headers received in the webhook request for debugging.
    • query - Query parameters received in the webhook request for debugging.

Dependencies

  • Masumi Paywall API (optional API key credential)

Troubleshooting

  • Common issues include misconfigured webhook paths or HTTP methods that do not match the expected endpoint, leading to webhook not triggering correctly.
  • Errors during webhook processing return a JSON object with error details, including the error type 'webhook_error' and a descriptive message to help diagnose the problem.
  • Ensure that the webhook URL path matches the configured 'path' and 'endpoint' parameters to avoid routing issues.

Discussion