Actions20
Overview
This node integrates with the OmniFlow API to manage company contacts, specifically allowing users to add or remove contacts from companies. The "Remove" operation under the "Company Contact" resource enables removing a specified contact from a specified company.
Common scenarios include:
- Cleaning up company contact lists by removing outdated or incorrect contacts.
- Managing relationships between companies and their contacts dynamically in workflows.
- Automating contact management tasks within CRM or marketing automation processes.
For example, you might use this node to automatically remove a contact from a company when they unsubscribe or leave the organization.
Properties
| Name | Meaning |
|---|---|
| Authentication | Method of authentication to use: either "Credentials" (API key) or "OAuth2" |
| Contact ID | The unique identifier of the contact to be removed from the company |
| Company ID | The unique identifier of the company from which the contact will be removed |
Output
The output is a JSON object representing the contact after the removal operation. It typically contains the contact's details as returned by the OmniFlow API. The structure corresponds to the contact resource's data fields.
No binary data output 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 company contacts.
- No additional environment variables are required beyond the API authentication setup.
Troubleshooting
- Invalid Contact ID or Company ID: If the provided IDs do not exist or are incorrect, the API may return errors. Verify that the IDs are correct and correspond to existing records.
- Authentication Errors: Ensure that the API credentials or OAuth2 tokens are valid and have sufficient permissions to modify company contacts.
- API Rate Limits or Network Issues: Temporary failures may occur due to rate limiting or connectivity problems. Retrying the operation or checking network status can help.
- Error Messages: The node throws errors if the API response indicates failure. Common messages relate to invalid parameters or unauthorized access. Review the error message details and adjust input parameters or authentication accordingly.
Links and References
- OmniFlow API Documentation (generic link, replace with actual if available)
- n8n Documentation on Creating Custom Nodes
- OAuth2 and API Credential Setup in n8n: Authentication