Actions15
Person → Create
AI-generatedOverview
This node integrates with the RogerRoger API to manage "Person" resources, specifically allowing you to create new person entries in your RogerRoger database. It is useful for automating contact management workflows, such as adding new leads, customers, or team members into your CRM system.
Typical use cases include:
- Automatically creating a new person record when a form is submitted.
- Syncing contacts from other systems into RogerRoger.
- Enriching your contact database by programmatically adding detailed person information.
For example, you could use this node to add a new person with their first and last name, email addresses, phone numbers, job title, and associated organizations, all in one step.
Properties
| Name | Meaning |
|---|---|
| First Name | The person's first name (required). |
| Last Name | The person's last name (required). |
| Additional Fields | Optional extra details about the person. These include: |
| - Organizations: List of organizations the person belongs to. | |
| - Tags: Tags associated with the person. | |
| - Lists: Segments or lists the person is part of. | |
| - 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: The person's job title. | |
| - Customer ID: An external customer identifier. | |
| - Address: Structured address details including street, city, and postal code. |
Output
The node outputs JSON data representing the created person resource as returned by the RogerRoger API. This typically includes the unique identifier of the person, their names, contact details, and any additional fields provided.
No binary data output is produced by this node.
Example output structure (simplified):
{
"resource": "person",
"operation": "create",
"id": "uuid-of-created-person",
"name": "First Name",
"surname": "Last Name",
"emailAddresses": ["example@email.com"],
"phoneNumbers": ["+1-555-123-4567"],
"organizations": ["organization-id-1", "organization-id-2"],
"tags": ["tag-id-1"],
"segments": ["segment-id-1"],
"linkedinId": "linkedin-profile-id",
"jobTitle": "Job Title",
"customerId": "external-customer-id",
"address": {
"street": "123 Main St",
"city": "CityName",
"postalCode": "12345"
}
}
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
- Authentication errors: Ensure that the API key credential is correctly set up and has sufficient permissions.
- Validation errors: Required fields like "First Name" and "Last Name" must be provided; missing these will cause errors.
- API request failures: Check network connectivity and verify that the RogerRoger API service is operational.
- Invalid field values: For multi-value fields like email addresses and phone numbers, ensure correct formatting.
- Error messages from the node typically include HTTP response details from the API. Review these messages to identify issues such as rate limits, invalid data, or permission problems.
Links and References
- RogerRoger API Documentation (hypothetical link)
- n8n Expressions Documentation
- n8n Node Development Guide