Actions28
- Кампании Actions
- Создание Кампаний Actions
- Управление Кампаниями Actions
- Финансы Actions
- Параметры Кампаний Actions
- Медиа Actions
- Календарь Акций Actions
Overview
This node operation allows you to post a deposit to an advertising campaign's budget within a financial management context. It is useful for automating the process of adding funds to campaigns, ensuring that budgets are updated programmatically without manual intervention. Typical use cases include replenishing campaign budgets based on external triggers or scheduled workflows, such as increasing ad spend when certain performance thresholds are met.
For example, you might use this node to add 5000 units of currency to a campaign's balance or bonus account, specifying the source type of the deposit and optionally requesting the updated budget size in the response.
Properties
| Name | Meaning |
|---|---|
| Id | The unique identifier of the campaign to which the budget deposit will be applied. |
| Sum | The amount of money to deposit into the campaign's budget. |
| Type | The source type of the deposit: - 0 — Account - 1 — Balance - 3 — Bonuses |
| Return | Flag indicating whether to return the updated campaign budget in the response: - true — returns updated budget size - false or omitted — no budget info returned |
Output
The output JSON contains the response from the API after posting the budget deposit. If the Return property is set to true, the response includes the updated size of the campaign's budget. Otherwise, the response may not contain budget details.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential to authenticate requests to the external advertising platform's financial API.
- The node uses a base URL configured from an imported Swagger/OpenAPI specification.
- Proper network access and permissions to the external service are necessary.
Troubleshooting
Common issues:
- Invalid campaign ID (
Id) leading to "campaign not found" errors. - Insufficient permissions or invalid API credentials causing authentication failures.
- Incorrect
Typevalues resulting in rejected requests. - Network connectivity problems preventing API calls.
- Invalid campaign ID (
Error messages and resolutions:
- "Unauthorized" — Check that the API key credential is correctly configured and has required permissions.
- "Invalid campaign ID" — Verify the campaign ID exists and is correct.
- "Bad Request" — Ensure all required properties are provided and valid, especially
SumandType. - Timeouts or network errors — Confirm network connectivity and endpoint availability.
Links and References
- Refer to the advertising platform’s official API documentation for detailed information about budget deposit endpoints and parameters.
- Consult n8n documentation on how to configure API credentials and handle HTTP request nodes for similar integrations.