Actions20
Overview
This node integrates with the OmniFlow API to manage contacts and their associations with segments, campaigns, companies, and emails. Specifically, for the Contact Segment - Add operation, it adds a specified contact to a chosen segment within OmniFlow.
Common scenarios where this node is beneficial include:
- Automatically grouping contacts into marketing or sales segments based on workflow triggers.
- Managing dynamic contact lists for targeted communications.
- Synchronizing contact segmentation between OmniFlow and other systems.
For example, after capturing a new lead in a CRM, you can use this node to add that contact to a specific segment for a follow-up email campaign.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authenticating with OmniFlow API: either using static credentials or OAuth2 authentication. |
| Contact ID | The unique identifier of the contact to be added to the segment. |
| Segment Name or ID | The target segment to which the contact will be added. Can be selected from a list or specified by ID. |
Output
The output JSON contains the response from the OmniFlow API after attempting to add the contact to the segment. Typically, this includes confirmation details about the updated segment membership or the contact's status within the segment.
No binary data is produced by this operation.
Dependencies
- Requires an active OmniFlow API connection configured in n8n, authenticated either via API credentials or OAuth2.
- The node depends on the OmniFlow API endpoints for managing segments and contacts.
- The "Segment Name or ID" property dynamically loads available segments from the OmniFlow account.
Troubleshooting
- Invalid Contact ID or Segment ID: If the provided contact or segment identifiers are incorrect or do not exist, the API call will fail. Verify IDs are correct and that the contact and segment exist in OmniFlow.
- Authentication Errors: Ensure that the API credentials or OAuth2 tokens are valid and have sufficient permissions to modify segments.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems. Retrying the operation after some time may resolve these issues.
- Error Messages: The node throws errors if the API returns an error response. The error message typically indicates the cause (e.g., "Contact not found", "Segment not found"). Review the message and adjust inputs accordingly.
Links and References
- OmniFlow API Documentation (generic link, replace with actual if known)
- n8n Expressions Documentation — for specifying dynamic values in properties
- OmniFlow Segments Management Guide (generic link)
If you need summaries for other resources or operations, please provide their names.