Actions33
- Public Actions
- Public Admin Actions
- Reseller Actions
- Create New Team
- Get Team Information
- Update Team
- Remove Team From Reseller
- Update Team Avatar
- Create Team Bulk Inboxes And Users
- Get Team Users
- Add User To Team
- Remove Users From Team
- Get Team Inboxes
- Remove Team Inboxes
- Create Team Bulk Inboxes
- Assign Users To Inbox
- Remove Users From Inbox
- Get Team Whitelist Domains
- Create Team Whitelisted Domain
- Remove Team Whitelisted Domain
- Create Reseller
- Import Team Users
- Get Import Team Users Job Status
Overview
This node allows creating a new contact in the "Public" resource context. It is designed to send contact details such as name, phone number, email, and visibility status (public or not) to an external service via an API call. This node is useful for automating the addition of contacts into a CRM system, marketing platform, or any contact management backend that supports this API.
Practical examples include:
- Automatically adding new leads collected from a web form into a public contact list.
- Syncing user sign-ups with a centralized contact database.
- Creating contacts programmatically during onboarding workflows.
Properties
Name | Meaning |
---|---|
Name | The full name of the contact to be created. |
Phone | The phone number of the contact. |
The email address of the contact. | |
Public | Boolean flag indicating whether the contact should be marked as public (true/false). |
Additional Body Fields | Optional additional metadata for the contact, provided as a JSON object. |
Output
The node outputs JSON data representing the response from the API after creating the contact. This typically includes details of the newly created contact such as its unique identifier, stored fields, and any server-generated metadata.
If the API supports binary data output, it would be related to attachments or files associated with the contact, but based on the provided code and properties, this node primarily handles JSON data.
Dependencies
- Requires an API key credential for authenticating requests to the external contact management service.
- The base URL for the API is configured via credentials.
- Uses HTTP headers
Accept: application/json
andContent-Type: application/json
. - Depends on the
@avantguardllc/n8n-openapi-node
package and an OpenAPI specification (openapi.json
) bundled with the node for request building.
Troubleshooting
- Missing Required Fields: Ensure all required properties (Name, Phone, Email, Public) are provided; otherwise, the API may reject the request.
- Invalid JSON in Additional Fields: The "Additional Body Fields" property expects valid JSON. Malformed JSON will cause parsing errors.
- Authentication Errors: Verify that the API key credential is correctly set up and has sufficient permissions.
- Network Issues: Check connectivity to the API endpoint specified in credentials.
- API Response Errors: If the API returns errors, inspect the returned message for details such as duplicate contacts or invalid field formats.
Links and References
- No direct external links were found in the source code.
- For more information, consult the documentation of the external contact management API used by this node.