RogerRoger icon

RogerRoger

Interact with RogerRoger API for Person, Organization and Task resources

Actions15

Organization → Create

AI-generated

Overview

This node integrates with the RogerRoger API to manage Organization resources, specifically allowing users to create new organizations. It is useful in scenarios where you want to automate the addition of organization data into RogerRoger from other systems or workflows. For example, when a new client signs up on your platform, you can automatically create an organization record in RogerRoger with relevant details such as name, contact information, tags, and associated people.

Properties

Name Meaning
Title The name/title of the organization to be created (required).
Additional Fields Optional extra details about the organization, including:
- People List of people associated with this organization (selectable from existing people).
- Website Website URL of the organization (e.g., https://example.com).
- Description A textual description of the organization.
- Customer ID An identifier for the customer within your system.
- Chamber of Commerce Number Official registration number for the organization.
- Tags Tags associated with the organization (selectable from existing tags).
- Lists Lists or segments associated with the organization (selectable from existing segments).
- Email Addresses One or more email addresses related to the organization.
- Phone Numbers One or more phone numbers related to the organization.
- Address Physical address details including street, city, postal code, and country code (default "NL").

Output

The node outputs JSON data representing the newly created organization resource as returned by the RogerRoger API. This includes all fields stored in the organization record, such as its unique ID, title, contact details, tags, associated people, and any other metadata provided during creation.

No binary data output is produced by this operation.

Dependencies

  • Requires an API key credential for authenticating with the RogerRoger API.
  • The node expects the RogerRoger API base URL and API key to be configured in the credentials.
  • Network access to the RogerRoger API endpoint is necessary.

Troubleshooting

  • Common issues:
    • Missing required fields like the organization title will cause errors.
    • Invalid or missing API credentials will result in authentication failures.
    • Providing invalid formats for fields such as email addresses or URLs may cause the API to reject the request.
  • Error messages:
    • Errors from the RogerRoger API are wrapped and surfaced as node errors with descriptive messages.
    • If the node throws an error about unknown resource or operation, verify that the correct resource ("Organization") and operation ("Create") are selected.
  • Resolution tips:
    • Ensure all required fields are filled correctly.
    • Verify API credentials and permissions.
    • Use valid formats for emails, URLs, and other structured fields.
    • Enable "Continue On Fail" if you want the workflow to proceed despite individual item errors.

Links and References

Discussion