Outseta icon

Outseta

Interact with Outseta CRM API to manage people, accounts, and deals

Actions16

Overview

The "Person - Get Many" operation in this node allows you to retrieve multiple person records from the Outseta CRM system. It is useful when you want to fetch lists of people based on various filters such as email, first name, last name, or other criteria. This operation supports pagination through limit and offset parameters and lets you specify which fields to return.

Practical examples include:

  • Fetching all contacts with a specific last name.
  • Retrieving a list of people filtered by their email domain.
  • Getting a paginated list of people for reporting or synchronization purposes.

Properties

Name Meaning
Additional Options A collection of optional filters and settings to refine the query:
  Fields Comma-separated list of fields to return (e.g., Uid,Email,FirstName,LastName)
  Filter by Email Filter people by email address
  Filter by First Name Filter people by first name
  Filter by Last Name Filter people by last name
Limit Maximum number of results to return (minimum 1, default 50)
Offset Number of results to skip before starting to collect the output (minimum 0, default 0)

Note: The filters under "Additional Options" are only applicable when the resource is "Person" and operation is "Get Many".

Output

The output is a JSON array where each element represents a person record retrieved from the Outseta CRM. Each person object contains fields such as unique identifier (Uid), email, first name, last name, and any other requested fields specified in the "Fields" property.

No binary data output is produced by this operation.

Example output snippet (simplified):

[
  {
    "Uid": "abc123",
    "Email": "[email protected]",
    "FirstName": "John",
    "LastName": "Doe"
  },
  {
    "Uid": "def456",
    "Email": "[email protected]",
    "FirstName": "Jane",
    "LastName": "Smith"
  }
]

Dependencies

  • Requires an API key credential for authenticating with the Outseta CRM API.
  • The node expects the base URL to be configured dynamically using the domain provided in credentials.
  • No additional external dependencies are required.

Troubleshooting

  • Empty results: If no people are returned, verify that your filter values (email, first name, last name) are correct and match existing records.
  • Invalid field names: Specifying unknown fields in the "Fields" option may cause the API to ignore them or return errors. Use valid field names like Uid, Email, FirstName, LastName.
  • Authentication errors: Ensure the API key credential is correctly set up and has sufficient permissions.
  • Pagination issues: If you request a large limit, the API might throttle or limit responses. Use reasonable limits and offsets.

Links and References

Discussion