RogerRoger icon

RogerRoger

Interact with RogerRoger API for Person, Organization and Task resources

Actions15

Person → Update

AI-generated

Overview

The node integrates with the RogerRoger API to manage "Person" resources, specifically supporting updating existing person records. It allows users to modify various attributes of a person such as their name, contact details, associated organizations, tags, and address information.

This node is beneficial in scenarios where you need to keep your contact database synchronized or updated automatically based on external triggers or workflows. For example, when a person's job title changes in an HR system, this node can update that information in RogerRoger. Another use case is enriching contact data by adding new email addresses or phone numbers collected from other sources.

Properties

Name Meaning
Person ID Select the person to update by UUID or search from a list of people.
Update Fields Collection of fields to update for the selected person:
- First Name The person's first name.
- Surname The person's last name.
- Organizations List of organizations the person belongs to (selectable from available organizations).
- Tags Tags associated with the person (selectable from available tags).
- Lists Lists (segments) associated with the person (selectable from available segments).
- Email Addresses One or more email addresses for the person.
- Phone Numbers One or more phone numbers for the person.
- LinkedIn ID LinkedIn identifier for the person.
- Job Title Job title of the person.
- Customer ID Customer identifier for the person.
- Address Address details including street, city, and postal code.

Output

The node outputs JSON data representing the updated person resource as returned by the RogerRoger API after the PATCH request. The output includes all relevant fields of the person resource reflecting the updates made.

No binary data output is produced by this node.

Dependencies

  • Requires an API key credential for authenticating with the RogerRoger API.
  • Needs network access to the RogerRoger API base URL configured in the credentials.
  • Uses internal helper methods to build HTTP requests and parse responses.
  • Supports dynamic loading of options for organizations, tags, and segments via API calls.

Troubleshooting

  • Invalid Person ID: If the provided Person ID is not a valid UUID, the node will throw a validation error. Ensure the ID matches the UUID format.
  • API Authentication Errors: If the API key is missing or invalid, the node will fail with an authentication error. Verify the API key credential configuration.
  • Empty Update Fields: If no update fields are provided, the API may reject the request or no changes will be made. Always specify at least one field to update.
  • Network Issues: Connectivity problems to the RogerRoger API endpoint will cause request failures. Check network settings and API availability.
  • Permission Denied: Insufficient permissions for the API key to update person resources will result in errors. Confirm API key scopes and permissions.

Links and References

Discussion