Actions72
- Кампания Actions
- Лендинг Actions
- Оффер Actions
- Клик Actions
- Настройки Actions
- Пользователь Actions
- Блэклист Actions
- Бот Actions
- Постбэк Actions
- Источник Actions
- Конверсия Actions
- Статистика Actions
- Группа Actions
- Поток Actions
- Фильтр Actions
- Лог Actions
- Домен Actions
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), it supports operations including retrieving information, updating, and deleting a landing by its ID. The node is useful for automating the management of marketing assets within Keitaro, such as deleting a landing page by specifying its ID.
Use Case Examples
- Deleting a landing page by providing its landing ID to automate cleanup of unused or outdated landing pages in Keitaro.
- Retrieving landing information to synchronize data with other marketing tools.
Properties
| Name | Meaning |
|---|---|
| ID Лендинга | The unique identifier of the landing to be retrieved, updated, or deleted. |
Output
JSON
requesturl- 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., delete).success- Indicates if the operation was successful (true for delete).data- The data returned from the Keitaro API after the operation, typically confirmation of deletion or resource details.
Dependencies
- Requires an API key credential for Keitaro API access and the domain URL of the Keitaro instance.
Troubleshooting
- Ensure the landing ID is provided and valid for delete operations; missing or invalid IDs will cause errors.
- Verify that the API key and domain are correctly configured in the node credentials; missing credentials will prevent API access.
- API errors will include status codes and messages; check these to diagnose issues such as permission errors or resource not found.
- For the 'stats' resource, only the 'getAll' operation is supported; using other operations will throw an error.