Overview

This node integrates with the Keitaro API to manage various resources such as campaigns, streams, landings, offers, and more. Specifically, for the resource "Лендинг" (Landing), the node supports operations like creating, updating, retrieving, and deleting landing entries. It is useful for automating the management of landing pages within the Keitaro platform, allowing users to programmatically create new landing pages by providing JSON-formatted landing data. This can be applied in marketing automation workflows where landing pages need to be dynamically created or updated based on external triggers or data.

Use Case Examples

1. Creating a new landing page by providing JSON data describing the landing page's properties.
2. Updating an existing landing page with new configuration data.
3. Retrieving details of a specific landing page by its ID.

Properties

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 sensitive API keys masked.
• resource - The resource type involved in the operation (e.g., landing).
• operation - The operation performed (e.g., create).
• success - Indicates if the operation was successful (true for create).
• data - The data returned from the Keitaro API after the operation, typically the created or updated landing object.

Dependencies

• Requires an API key credential for Keitaro API access and the domain URL of the Keitaro instance.

Troubleshooting

• Ensure the API key and domain are correctly set in the credentials; missing or incorrect credentials will cause authentication errors.
• When creating or updating a landing, the JSON data must be valid and non-empty; otherwise, the node throws an error indicating missing data.
• For 'stats' resource, only the 'getAll' operation is supported; selecting other operations will cause an error.
• If the API response status code is not in the 2xx range, an error with the status code and message is thrown.
• If the node is set to continue on fail, errors are captured and returned in the output with detailed error information.