Actions20
Overview
This node integrates with the OmniFlow API to manage campaign contacts by adding or removing contacts from campaigns. It is useful in marketing automation workflows where you want to programmatically control which contacts are included in specific campaigns, enabling targeted communication and campaign management.
For example, you can use this node to add a new contact to a promotional email campaign after they sign up on your website, or remove a contact who has unsubscribed from a campaign list.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Credentials" (API key) or "OAuth2" |
| Contact ID | The unique identifier of the contact to add or remove from the campaign |
| Campaign Name or ID | Select a campaign from the dropdown list or specify its ID via an expression |
Output
The node outputs JSON data representing the result of the add or remove operation for each processed item. The output typically contains the updated contact or campaign contact information as returned by the OmniFlow API.
No binary data output is produced by this node.
Dependencies
- Requires an active OmniFlow API connection configured in n8n, using either API key credentials or OAuth2 authentication.
- The node depends on the OmniFlow API endpoints for campaigns and contacts.
- The
getCampaignsmethod dynamically loads available campaigns for selection.
Troubleshooting
- Invalid Contact ID or Campaign ID: If the provided IDs do not exist or are incorrect, the API will return errors. Verify that the IDs are correct and correspond to existing contacts and campaigns.
- Authentication Errors: Ensure that the API credentials or OAuth2 tokens are valid and have sufficient permissions to modify campaign contacts.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems. Implement retry logic or check network status.
- Invalid JSON in Expressions: When specifying IDs or other parameters via expressions, ensure the JSON syntax is correct to avoid parsing errors.
Links and References
- OmniFlow API Documentation (generic link, replace with actual if available)
- n8n Expressions Documentation
- n8n Node Development Guide