Actions32
- Campaign Actions
- List Actions
- Media Actions
- Setting Actions
- Subscriber Actions
- Template Actions
- Transaction Actions
Overview
The node integrates with a list management and email campaign platform, allowing users to perform various operations such as managing lists, campaigns, media, templates, and subscribers. Specifically, the "Test Sending the Campaign" operation enables sending a test version of an existing campaign to verify its content and delivery before launching it broadly. This is useful for marketers or administrators who want to preview how their campaign will appear to recipients and ensure all settings are correct.
Practical examples include:
- Sending a test email campaign to internal team members for review.
- Verifying dynamic content rendering in the campaign.
- Checking that links, images, and personalization tokens work as expected.
Properties
| Name | Meaning |
|---|---|
| Json Body | The JSON payload to send with the request. This can include additional parameters required by the API when testing the campaign. Default is an empty JSON object {}. |
| ID | The unique identifier of the campaign to be tested. This is a required string property specifying which campaign to send a test for. |
Output
The node outputs JSON data representing the response from the campaign test sending API call. This typically includes information about the success or failure of the test send request, any messages returned by the server, and possibly metadata about the test email dispatch.
If the node supports binary data output (not explicitly shown here), it would generally represent attachments or raw email content related to the campaign test.
Dependencies
- Requires connection to a list management and email campaign service via its API.
- Needs credentials including domain URL, username, and password for authentication.
- The base URL for API requests is constructed from the provided domain credential.
- The node expects the API to accept and return JSON-formatted data.
Troubleshooting
- Invalid or missing campaign ID: Ensure the campaign ID is correctly specified; otherwise, the API will reject the request.
- Authentication errors: Verify that the API credentials (domain, username, password) are correct and have sufficient permissions.
- Malformed JSON body: If the JSON body is not properly formatted, the API may return an error. Use valid JSON syntax.
- Network issues: Check connectivity to the API endpoint and firewall settings.
- API rate limits or restrictions: If too many test sends are performed in a short time, the API might throttle requests.
Common error messages might include unauthorized access, resource not found (invalid campaign ID), or bad request due to invalid JSON.
Links and References
- Official list management and campaign platform API documentation (refer to the specific service used).
- n8n documentation on creating and using custom nodes.
- JSON formatting guides for constructing valid request bodies.