RogerRoger icon

RogerRoger

Interact with RogerRoger API for Person, Organization and Task resources

Actions15

Organization → Get

AI-generated

Overview

This node integrates with the RogerRoger API to manage organizational data, among other resources like Person and Task. Specifically, the Organization - Get operation retrieves detailed information about a single organization by its unique identifier (UUID). This is useful when you want to fetch up-to-date details of an organization stored in RogerRoger, such as for syncing data, displaying organization info in workflows, or using it as input for further automation steps.

Practical examples:

  • Fetching an organization's full profile before updating related records.
  • Retrieving organization details to send personalized emails or notifications.
  • Using organization data to enrich CRM or ERP systems via n8n workflows.

Properties

Name Meaning
Organization ID Select an organization by its UUID or search from a list of organizations. Must be a valid UUID string (e.g., 0197cb13-ae93-7368-a3d6-ad8b6ba808db).

The property supports two modes:

  • ID: Directly enter the UUID of the organization.
  • List: Search and select from existing organizations fetched dynamically from the RogerRoger API.

Output

The output JSON contains the full organization data object returned by the RogerRoger API for the specified organization ID. It includes all available fields describing the organization, such as name, website, description, contact details, tags, associated people, and address information.

Example structure (simplified):

{
  "resource": "organization",
  "operation": "get",
  "id": "uuid-string",
  "title": "Organization Name",
  "website": "https://example.com",
  "description": "Description text",
  "emailAddresses": ["contact@example.com"],
  "phoneNumbers": ["+1-555-123-4567"],
  "tags": ["tag1", "tag2"],
  "people": ["person-id-1", "person-id-2"],
  "address": {
    "street": "123 Main St",
    "city": "CityName",
    "postalCode": "12345",
    "country": "NL"
  }
}

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the RogerRoger API.
  • The node uses the base URL configured in the credentials to construct API requests.
  • Network access to the RogerRoger API endpoints must be available.

Troubleshooting

  • Invalid UUID error: If the Organization ID does not match the UUID regex pattern, the node will reject the input. Ensure the ID is a valid UUID.
  • Authentication errors: If the API key is missing, invalid, or expired, the node will throw an authentication error. Verify the API key credential configuration.
  • Not found error: If the organization ID does not exist in RogerRoger, the API returns a 404 error. Confirm the ID is correct and the organization exists.
  • Network issues: Timeouts or connectivity problems can cause request failures. Check network settings and API availability.
  • Unknown resource or operation: The node throws errors if an unsupported resource or operation is requested. Use only supported combinations.

Links and References

Discussion