Actions28
- Кампании Actions
- Создание Кампаний Actions
- Управление Кампаниями Actions
- Финансы Actions
- Параметры Кампаний Actions
- Медиа Actions
- Календарь Акций Actions
Overview
This node interacts with a campaign management API to update the "strong" (negative) search phrases for a specific advertising campaign. It allows users to specify an ID of a campaign and set a list of negative keywords or phrases that should be excluded from the campaign's targeting.
Common scenarios include refining ad campaigns by excluding irrelevant or unwanted search terms, thereby improving ad relevance and reducing wasted spend. For example, a marketing specialist might use this node to bulk update negative keywords across multiple campaigns to prevent ads from showing on unrelated searches.
Properties
| Name | Meaning |
|---|---|
| Id | The unique numeric identifier of the campaign to update. |
| Strong | A JSON array of negative phrases (up to 1000 items) to exclude from the campaign search. |
Output
The node outputs JSON data representing the response from the API after updating the campaign's negative phrases. This typically includes confirmation of the update or details about the modified campaign parameters.
No binary data output is indicated.
Dependencies
- Requires an API key credential to authenticate requests to the campaign management API.
- The node uses a base URL configured from an imported OpenAPI specification.
- The request headers specify JSON content type and accept JSON responses.
Troubleshooting
- Invalid Campaign ID: If the provided campaign ID does not exist or is incorrect, the API may return an error indicating the campaign was not found. Verify the campaign ID before running the node.
- Malformed JSON in Strong Property: The "Strong" property expects a valid JSON array. Invalid JSON syntax will cause parsing errors. Ensure the input is correctly formatted JSON.
- Exceeding Phrase Limit: The API limits the number of negative phrases to 1000. Sending more than this may result in an error.
- Authentication Errors: Missing or invalid API credentials will cause authentication failures. Confirm that the API key is properly configured in n8n credentials.
Links and References
- No direct external links are provided in the source code.
- Users should refer to their campaign management platform’s API documentation for detailed information on the "strong" parameter and campaign updates.