Actions72
- Кампания Actions
- Лендинг Actions
- Оффер Actions
- Клик Actions
- Настройки Actions
- Пользователь Actions
- Блэклист Actions
- Бот Actions
- Постбэк Actions
- Источник Actions
- Конверсия Actions
- Статистика Actions
- Группа Actions
- Поток Actions
- Фильтр Actions
- Лог Actions
- Домен Actions
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 'log' resource and 'delete' operation, it deletes a log entry identified by its ID. This node is useful for automating management tasks in Keitaro, such as deleting logs, updating campaigns, or retrieving statistics. For example, it can be used to delete a specific log entry by providing its ID, helping maintain clean and relevant log data.
Use Case Examples
- Deleting a log entry by specifying its log ID to remove outdated or irrelevant logs from Keitaro.
- Automating the cleanup of logs in Keitaro by integrating this node in a workflow that triggers log deletions based on certain conditions.
Properties
| Name | Meaning |
|---|---|
| ID Лога | The unique identifier of the log entry to be deleted. Required for operations get, update, and delete on the log resource. |
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 data like API keys masked.
resource- The resource type involved in the operation, e.g., 'log'.operation- The operation performed, e.g., 'delete'.success- Indicates if the operation was successful (true for delete operation).data- The data returned from the Keitaro API after the operation, typically confirmation of deletion.
Dependencies
- Requires an API key credential for Keitaro API access and the domain URL of the Keitaro instance.
Troubleshooting
- Ensure the 'logId' property is provided and correctly formatted; 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 that the operation 'delete' is supported for the 'log' resource; unsupported operations will throw errors.
- If the API returns an error status, the node will throw an error with the API message; verify the API request parameters and permissions.