Missive icon

Missive

Work with the Missive API

Actions12

Contact → Get All

AI-generated

Overview

This node integrates with the Missive API to manage contacts and other resources. Specifically, the Contact - Get All operation retrieves a list of contacts from a specified contact book or all contacts if no specific book is provided. It supports filtering by search query, pagination through limit and offset parameters.

Typical use cases include:

  • Synchronizing contacts from Missive into another system.
  • Fetching contacts for bulk messaging or analysis.
  • Automating workflows that require access to user contact lists.

For example, you could use this node to fetch all contacts in a particular contact book whose names or emails match a search term, then process or export them elsewhere.

Properties

Name Meaning
Contact Book ID ID of the contact book to list contacts from (optional; if omitted, lists from all books)
Search Query Text query to filter contacts by name, email, or other searchable fields
Limit Maximum number of contacts to return (pagination control)
Offset Number of contacts to skip before starting to collect results (pagination offset)

Output

The output is a JSON object representing the response from the Missive API's contacts endpoint. It typically contains an array of contact objects with their details such as IDs, names, emails, phones, websites, company, birthday, and description.

Example structure (simplified):

{
  "contacts": [
    {
      "id": "contact_id_1",
      "name": "John Doe",
      "emails": ["john@example.com"],
      "phones": ["+1234567890"],
      "websites": ["https://example.com"],
      "company": "Example Inc.",
      "birthday": "1990-01-01",
      "description": "Sample contact"
    },
    ...
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API authentication token credential for the Missive API.
  • The node makes HTTP requests to https://public.missiveapp.com/v1/contacts.
  • No additional environment variables are required beyond the API key credential.

Troubleshooting

  • Common issues:

    • Invalid or missing API token will cause authorization errors.
    • Providing an invalid Contact Book ID may result in empty results or errors.
    • Exceeding rate limits imposed by the Missive API can cause request failures.
    • Incorrectly formatted query parameters (e.g., non-numeric limit or offset) may cause errors.

  • Error messages:

    • Authorization errors: Check that the API token credential is correctly configured and valid.
    • Validation errors: Ensure that numeric fields like limit and offset are numbers.
    • Network errors: Verify network connectivity and that the Missive API endpoint is reachable.

Links and References

Discussion