Actions17
- Contact Actions
- Message Actions
- Session Actions
- Panel Actions
Overview
This node integrates with the Helena API to manage contacts, messages, sessions, and panels. Specifically for the Contact - Create Contact operation, it allows users to create a new contact in the Helena system or update an existing one based on provided data.
Typical use cases include:
- Adding new customer or lead information into a CRM system.
- Automatically creating contacts from form submissions or other data sources.
- Updating existing contacts if they already exist (upsert).
- Tagging contacts and adding custom metadata for segmentation or categorization.
For example, you might use this node to add a new contact with their phone number, email, Instagram handle, and notes, while also assigning tags and custom fields relevant to your business needs.
Properties
| Name | Meaning |
|---|---|
| Phone Number | The contact's phone number. Used as a unique identifier or primary contact method. |
| Name | The full name of the contact. |
| The contact's email address. Must be a valid email format. | |
| The Instagram username of the contact. | |
| Annotation | A note or comment about the contact. Useful for additional context or remarks. |
| Tag Names or IDs | Tags to assign to the contact. You can select from a list or specify tag IDs via expressions. Tags help categorize or group contacts. |
| Upsert | Boolean flag indicating whether to update the contact if it already exists (true) or create a new one (false). |
| Get If Exists? | Boolean flag indicating whether to return the existing contact without updating it if found (true), otherwise proceed with creation or update. |
| Custom Fields | A collection of key-value pairs for custom metadata fields associated with the contact. Keys can be selected from predefined options or specified by ID. |
| Metada | Additional metadata key-value pairs to attach to the contact. Similar to custom fields but more generic. |
Output
The node outputs JSON data representing the created or updated contact object returned by the Helena API. This includes all standard contact fields such as ID, name, phone number, email, tags, annotations, custom fields, and metadata.
If the contact already exists and getIfExists is enabled, the existing contact data is returned without modification.
No binary data output is involved in this operation.
Dependencies
- Requires an API key credential for authentication with the Helena API.
- The base URL used is
https://api-test.helena.run. - Uses HTTP POST requests to the endpoint
/core/v1/contactfor creating or updating contacts. - Optional dependencies include dynamic loading of tags and custom fields via helper methods that query the API.
Troubleshooting
- Invalid Email Format: The node validates the email format using a regex pattern. Providing an invalid email will likely cause the API request to fail. Ensure emails are correctly formatted.
- Contact Already Exists: If neither
upsertnorgetIfExistsis enabled and a contact with the same phone number exists, the API may reject the creation. Useupsertto update orgetIfExiststo retrieve existing contacts instead. - Missing Required Fields: While not explicitly enforced in the code, providing at least a phone number or another unique identifier is necessary for meaningful contact creation.
- API Authentication Errors: Ensure the API key credential is correctly configured and has sufficient permissions.
- Network or API Errors: The node catches errors silently in some cases; if no output appears, verify network connectivity and API availability.
Links and References
- Helena API Documentation (assumed base URL)
- n8n Expressions Documentation — for using expressions in tag and custom field inputs
- Email Validation Regex Explanation — similar pattern used for validating email input