RogerRoger icon

RogerRoger

Interact with RogerRoger API for Person, Organization and Task resources

Actions15

Person → Get many

AI-generated

Overview

This node integrates with the RogerRoger API to manage data related to Persons, Organizations, and Tasks. Specifically for the Person resource with the Get many operation, it retrieves multiple person records from the RogerRoger system.

Common scenarios where this node is beneficial include:

  • Fetching a list of contacts or people stored in RogerRoger for further processing or analysis.
  • Synchronizing person data from RogerRoger into other systems or databases.
  • Automating workflows that require bulk access to person information, such as marketing campaigns or customer relationship management.

For example, you might use this node to retrieve up to 30 persons by default or all persons if configured, then filter or enrich this data downstream in your workflow.

Properties

Name Meaning
Return All Whether to return all results or only up to a given limit. Options: true or false.
Limit Max number of results to return when "Return All" is false. Minimum value is 1, default 30.

Output

The output JSON contains an items array with person objects retrieved from the RogerRoger API. Each item represents a person record with all available fields as returned by the API.

Example structure of the output JSON field:

{
  "items": [
    {
      "id": "uuid",
      "givenName": "First name",
      "familyName": "Last name",
      "emailAddresses": [...],
      "phoneNumbers": [...],
      "organizations": [...],
      "tags": [...],
      "segments": [...],
      // other person-related fields
    },
    ...
  ]
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the RogerRoger API.
  • The node uses HTTP requests to the RogerRoger API base URL configured in the credentials.
  • Proper network connectivity to the RogerRoger API endpoint is necessary.

Troubleshooting

  • Common issues:

    • Invalid or missing API key credential will cause authentication failures.
    • Network connectivity problems can lead to request timeouts or errors.
    • Exceeding API rate limits may result in error responses from the RogerRoger API.
    • Providing invalid parameter values (e.g., negative limit) may cause validation errors.

  • Error messages:

    • Errors from the RogerRoger API are wrapped and thrown as node errors with context about the failed item index.
    • If an unknown operation or resource is specified, the node throws an explicit error indicating the issue.
    • To handle partial failures, enable "Continue On Fail" in the node settings to receive error details per item without stopping the entire workflow.

Links and References

Discussion