Actions3
Overview
The "Remove Receiver From Campaign" operation in the Growth-x node allows users to remove a specified receiver from a selected Growth-X campaign. This is useful for managing campaign participants dynamically, such as when a contact should no longer receive messages or be part of a campaign workflow.
Typical use cases include:
- Automatically removing contacts who have opted out or unsubscribed.
- Cleaning up campaign lists by removing invalid or duplicate receivers.
- Managing campaign membership based on external CRM updates or business logic.
For example, if you have a LinkedIn profile URL of a contact that should no longer be targeted in a campaign, this node operation can remove that receiver from the campaign efficiently.
Properties
| Name | Meaning |
|---|---|
| Campaign | Choose from the list of available Growth-X campaigns to specify which campaign to modify. |
| LinkedIn URL | The LinkedIn profile URL of the receiver to be removed from the campaign (required). |
| Optional email address of the receiver, used as additional identification. | |
| External CRM ID | Optional external CRM identifier for the receiver, allowing integration with other systems. |
Output
The node outputs JSON data representing the response from the Growth-X API after attempting to remove the receiver from the campaign. This typically includes status information about the success or failure of the removal action.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authenticating requests to the Growth-X API.
- The node uses the Growth-X public API endpoint
https://api.growth-x.com/public/api/actions/remove_receiver_from_campaignvia a POST request. - The user must have access to the relevant Growth-X campaigns and permissions to modify them.
- The node configuration requires setting up the API authentication credential within n8n.
Troubleshooting
Common issues:
- Invalid or missing LinkedIn URL: The operation requires a valid LinkedIn profile URL; ensure it is correctly formatted.
- Campaign not found or inaccessible: Verify that the selected campaign exists and the API key has permission to modify it.
- Network or authentication errors: Check API credentials and network connectivity to the Growth-X API.
Error messages:
- Authentication failures usually indicate invalid or expired API keys; reconfigure the credential.
- Validation errors may occur if required fields are missing or incorrectly formatted.
- API rate limits or server errors might cause temporary failures; retry after some time.
Links and References
- Growth-X API Documentation (for detailed API endpoints and parameters)
- n8n Documentation (for general guidance on using custom nodes and credentials)