Actions19
- Agent Actions
- Campaign Actions
- Product Actions
- Prompt Actions
- Prospect Actions
Overview
The node interacts with the Kakiyo API to manage campaigns, specifically allowing updates to existing campaigns. It enables users to modify campaign attributes such as the campaign's name, qualification thresholds, and custom variables. This is useful in scenarios where campaign parameters need adjustment after creation, for example, changing the campaign name to reflect a new marketing focus or updating qualification criteria based on performance data.
Practical examples:
- Renaming a campaign to better align with a new product launch.
- Adjusting automatic and verification qualification thresholds to refine lead scoring.
- Updating campaign-specific variables that influence campaign behavior or messaging dynamically.
Properties
| Name | Meaning |
|---|---|
| Campaign ID | The unique identifier of the campaign to update (required). |
| Name | New name for the campaign. |
| Qualification Automatic | New automatic qualification threshold, a number between 0 and 100 representing the score. |
| Qualification Verification | New verification qualification threshold, a number between 0 and 100 representing the score. |
| Variables | A collection of key-value pairs representing custom variables to update within the campaign. Each variable has: - Name: Variable name - Value: Variable value |
Output
The node outputs JSON data representing the updated campaign object returned by the Kakiyo API. This typically includes the campaign's current state after the update, reflecting any changes made to its properties.
No binary data output is involved.
Dependencies
- Requires an active connection to the Kakiyo API via an API key credential configured in n8n.
- The base URL for the API is taken from the credential configuration.
- The node uses standard HTTP methods (PUT) to send update requests to the
/campaigns/{campaignId}endpoint.
Troubleshooting
Common issues:
- Invalid or missing Campaign ID will cause the update request to fail.
- Providing qualification thresholds outside the 0-100 range may result in API validation errors.
- Incorrectly formatted variables (e.g., missing names or values) might cause the API to reject the update.
- Network or authentication failures if the API key credential is invalid or expired.
Error messages:
"Campaign not found": Verify the Campaign ID is correct and exists."Invalid qualification threshold": Ensure qualificationAutomatic and qualificationVerification are numbers between 0 and 100."Authentication failed": Check the API key credential setup in n8n."Request body malformed": Confirm variables are provided as an array of objects with both name and value fields.
Resolving these usually involves verifying input parameters, ensuring proper credential configuration, and checking network connectivity.
Links and References
- Kakiyo API Documentation (Assumed URL; replace with actual if known)
- n8n documentation on HTTP Request Node for understanding API interactions.
- General best practices for managing API credentials securely in n8n.