Actions12
Contact → Create
AI-generatedOverview
This node integrates with the Missive API to manage contacts within a contact book. Specifically, the Contact - Create operation allows users to create a new contact in a specified contact book by providing details such as name, emails, phones, websites, company, birthday, and description.
Common scenarios where this node is beneficial include:
- Automatically adding new leads or customers from form submissions or CRM systems into a centralized contact book.
- Synchronizing contacts from other platforms or databases into Missive for unified communication management.
- Enriching contact books with detailed information like multiple emails, phone numbers, and company data.
Example use case:
- After receiving a new customer signup via a webhook, use this node to create a contact in a specific Missive contact book with their name, email addresses, and phone numbers.
Properties
| Name | Meaning |
|---|---|
| Contact Book ID | The identifier of the contact book where the new contact will be stored (required). |
| Name | The full name of the contact. |
| Emails | Comma-separated list of email addresses for the contact (e.g., email1@example.com,email2@example.com). |
| Additional Fields | A collection of optional fields to provide more contact details: |
| - Phones | Comma-separated list of phone numbers (e.g., +11234567890,+10987654321). |
| - Websites | Comma-separated list of websites URLs associated with the contact (e.g., https://example.com,https://example.org). |
| - Company | The company name the contact is associated with. |
| - Birthday | Birthday date in YYYY-MM-DD format (e.g., 1990-01-01). |
| - Description | A textual description or notes about the contact. |
Output
The node outputs the JSON response returned by the Missive API after creating the contact. This typically includes the newly created contact's details such as its unique ID, name, emails, phones, and other metadata as stored in Missive.
The output structure is:
{
"json": {
"contacts": {
"id": "string",
"contact_book_id": "string",
"name": "string",
"emails": ["string"],
"phones": ["string"],
"websites": ["string"],
"company": "string",
"birthday": "string",
"description": "string",
...
}
}
}
No binary data output is produced by this operation.
Dependencies
- Requires an active connection to the Missive API using an API authentication token credential.
- The node makes HTTP POST requests to the Missive public API endpoint at
https://public.missiveapp.com/v1/contacts. - Proper API credentials must be configured in n8n for authorization.
Troubleshooting
- Missing or invalid Contact Book ID: The contact book ID is required. Ensure it is provided and valid; otherwise, the API will reject the request.
- Invalid email or phone formats: Emails and phones should be comma-separated strings without extra spaces. Invalid formats may cause API errors.
- API authentication errors: If the API token is missing, expired, or incorrect, the node will fail with authorization errors. Verify the API key credential setup.
- Network or connectivity issues: Temporary network failures can cause request timeouts or errors. Retrying the workflow might help.
- Unexpected API response: If the Missive API changes or returns unexpected data, the node might throw errors. Check the API status and update the node if needed.
Links and References
- Missive API Documentation — Official API docs for managing contacts and other resources.
- n8n Documentation — General guidance on using n8n nodes and workflows.