Keitaro icon

Keitaro

Работа с API Keitaro
Join our community

Actions72

Overview

This node interacts with the Keitaro API to perform various operations on different resources such as campaigns, streams, landings, offers, traffic, users, blacklists, bots, postbacks, sources, conversions, domains, clicks, filters, settings, logs, statistics, and groups. Specifically, for the resource "Конверсия" (Conversion) and operation "Получить" (Get), the node retrieves detailed information about a specific conversion by its ID. This is useful for scenarios where you need to fetch conversion data for analysis, reporting, or further processing in automation workflows.

Use Case Examples

  1. Retrieve a conversion record by its ID to analyze conversion performance.
  2. Fetch conversion details to update or validate conversion data in your marketing automation.
  3. Use conversion data to trigger downstream processes such as notifications or data synchronization.

Properties

Name Meaning
ID Конверсии The unique identifier of the conversion to retrieve. This is required for the 'get' operation on the conversion resource.

Output

JSON

  • request
    • url - The URL of the API request made to Keitaro.
    • method - The HTTP method used for the API request.
    • headers - Headers sent with the API request, with the API key masked for security.
  • resource - The resource type involved in the operation, e.g., 'conversion'.
  • operation - The operation performed, e.g., 'get'.
  • data - The data returned from the Keitaro API for the requested conversion.
  • success - Indicates if the operation was successful (true for successful get operations).

Dependencies

  • Requires an API key credential for Keitaro API access and the domain URL configured in the credentials.

Troubleshooting

  • Ensure the 'ID Конверсии' (conversion ID) is provided and correctly formatted for 'get' operations; missing or invalid IDs will cause errors.
  • Verify that the API key and domain are correctly set in the credentials; missing credentials will prevent API access.
  • Check for API response errors indicating issues such as invalid permissions, non-existent conversion IDs, or network problems.
  • If the node throws an error about unsupported operations for the 'stats' resource, ensure only the 'getAll' operation is used for 'stats'.
  • Use the node's 'continueOnFail' option to handle errors gracefully in workflows and inspect error details in the output for debugging.

Discussion