Lexoffice Public API icon

Lexoffice Public API

Contacts the Lexoffice Public API
Join our community

Actions5

Overview

This n8n node, Lexoffice Public API, allows users to interact with the Lexoffice platform by making API requests to retrieve collections of contacts. Specifically, for the resource Default and operation API Contact GET Collection, the node fetches a paginated list of contacts from Lexoffice. This is useful for automating workflows that require access to contact data, such as synchronizing contacts with other systems, generating reports, or triggering actions based on contact information.

Practical Example:
A business could use this node to regularly pull updated contact lists from Lexoffice into their CRM, or to trigger email campaigns for new contacts added in Lexoffice.

Properties

Name Type Meaning
Category options The type of resource to interact with. For this operation, should be set to "Contacts".
Page number The page number for paginated results when retrieving the contacts collection.

Output

  • The output is an array of objects under the json field.
  • Each object represents a contact retrieved from Lexoffice.
  • The structure of each contact object depends on the Lexoffice API response, but typically includes fields like id, name, email, etc.

Example Output:

[
  {
    "json": {
      "id": "12345",
      "name": "John Doe",
      "email": "john.doe@example.com"
      // ...other contact fields
    }
  },
  {
    "json": {
      "id": "67890",
      "name": "Jane Smith",
      "email": "jane.smith@example.com"
      // ...other contact fields
    }
  }
]
  • Binary data is not relevant for this operation; only JSON contact data is returned.

Dependencies

  • External Service: Requires access to the Lexoffice API.
  • Credentials: Needs a valid Lexoffice Public API credential (API token and domain) configured in n8n.
  • n8n Configuration: The node must be provided with the correct credentials via n8n's credential system.

Troubleshooting

Common Issues:

  • Missing Credentials:
    Error Message: "No API Item found" or authentication errors.
    Resolution: Ensure that the Lexoffice Public API credentials are correctly set up in n8n.

  • Invalid Parameters:
    Error Message: Errors related to missing or invalid parameters (e.g., wrong category or page).
    Resolution: Make sure "Category" is set to "Contacts" and "Page" is a valid number.

  • API Limitations or Errors:
    Error Message: Errors returned from Lexoffice API (e.g., rate limits, permission denied).
    Resolution: Check your Lexoffice account permissions and API usage limits.

  • JSON Parsing Errors:
    Error Message: "Error parsing JSON" (not expected for this operation, but possible if advanced properties are used incorrectly).
    Resolution: Ensure all input fields are filled with valid values.

Links and References

Discussion