AI Marketplace icon

AI Marketplace

Interact with AI Marketplace API
Join our community

Actions24

Overview

This node operation subscribes to marketplace events from the AI Marketplace platform. It allows users to specify which event types they want to receive notifications for, such as lot creation, lot closure, offer creation, offer status changes, and feedback left. The node supports delivering these event notifications via webhook or WebSocket, making it useful for integrating real-time event-driven workflows or automations triggered by marketplace activities. For example, a user can subscribe to 'Lot Created' events to automatically trigger downstream processes whenever a new lot is created in the marketplace.

Use Case Examples

  1. Automatically trigger a workflow when a new lot is created by subscribing to the 'Lot Created' event type with webhook delivery.
  2. Receive real-time updates on offer status changes via WebSocket to update a dashboard or notify users.
  3. Subscribe to feedback left events to analyze customer feedback and trigger sentiment analysis workflows.

Properties

Name Meaning
Environment The environment to connect to, either Development or Production.
Override Base URL Optional URL to override the default base URL for the selected environment.
Event Types The types of marketplace events to subscribe to, such as Lot Created, Lot Closed, Offer Created, Offer Status Changed, and Feedback Left.
Callback URL The HTTPS callback URL where webhook event notifications will be sent. Must use HTTPS for security.
Delivery Method The method to deliver event notifications, either via Webhook or WebSocket.
Additional Fields Optional additional settings such as request timeout in seconds and response format (JSON or raw).

Output

JSON

  • json - The JSON response from the subscription API call, containing subscription details or confirmation.

Dependencies

  • An API key credential for AI Marketplace API authentication is required for this operation.

Troubleshooting

  • Ensure the Callback URL uses HTTPS protocol; HTTP URLs are rejected for security reasons.
  • Verify that the API credentials are configured correctly, as authentication is required for subscribing to events.
  • Check that the event types specified are valid and supported by the API.
  • If using webhook delivery, ensure the callback URL is reachable and can accept POST requests.
  • Timeout errors may occur if the request takes longer than the specified timeout; adjust the timeout setting if needed.

Links

Discussion