Missive icon

Missive

Work with the Missive API

Actions12

Contact → Update

AI-generated

Overview

The node integrates with the Missive API to manage contacts within a contact book. Specifically, the Update Contact operation allows users to modify an existing contact's details such as name, emails, phone numbers, websites, company, birthday, and description. This is useful in scenarios where contact information needs to be kept current or corrected, for example updating a customer's email address or adding new phone numbers.

Practical examples:

  • Updating a contact's email list after they provide new addresses.
  • Changing the company name associated with a contact after a job change.
  • Adding a birthday date to a contact record for personalized communications.

Properties

Name Meaning
Contact ID The unique identifier of the contact to update (required).
Contact Book ID The identifier of the contact book where the contact is 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:
- Phones Comma-separated phone numbers (e.g., "+11234567890,+10987654321").
- Websites Comma-separated website URLs (e.g., "https://example.com,https://example.org").
- Company The company name associated with the contact.
- Birthday Birthday in YYYY-MM-DD format (e.g., "1990-01-01").
- Description A textual description or notes about the contact.

Output

The output JSON contains the response from the Missive API after updating the contact. It typically includes the updated contact object with all its properties reflecting the changes made.

Example structure (simplified):

{
  "contacts": {
    "id": "contact-id",
    "contact_book_id": "contact-book-id",
    "name": "Updated Name",
    "emails": ["email1@example.com", "email2@example.com"],
    "phones": ["+11234567890", "+10987654321"],
    "websites": ["https://example.com", "https://example.org"],
    "company": "Updated Company",
    "birthday": "1990-01-01",
    "description": "Updated description"
  }
}

No binary data output is involved in this operation.

Dependencies

  • Requires an API authentication token credential for the Missive API.
  • The node makes HTTP requests to the Missive public API endpoint https://public.missiveapp.com/v1.
  • Proper configuration of the API key credential in n8n is necessary.

Troubleshooting

  • Missing or invalid Contact ID: The update operation requires a valid contact ID. Ensure the Contact ID property is correctly set.
  • Invalid Contact Book ID: The contact book ID must exist and be accessible by the API token used.
  • Malformed emails or phones: Email and phone lists should be comma-separated strings without extra spaces; improper formatting may cause API errors.
  • API authentication errors: If the API token is missing, expired, or incorrect, the request will fail with authorization errors.
  • Network issues: Connectivity problems can cause request failures; verify network access to the Missive API endpoint.
  • Unexpected API responses: Check the error message returned by the API for clues; enabling "Continue on Fail" can help debug by capturing error messages in the output.

Links and References

Discussion