RD Station Marketing icon

RD Station Marketing

Consume RD Station Marketing API
Join our community

Actions5

Overview

This node integrates with the RD Station Marketing API to manage marketing contacts. Specifically, the Contact - Update operation allows users to update existing contact records in RD Station by specifying either the contact's UUID or email address as an identifier.

Typical use cases include:

  • Synchronizing updated customer information from other systems into RD Station.
  • Correcting or enriching contact data such as job title, social media profiles, location, and custom fields.
  • Managing tags and notes on contacts to improve segmentation and targeting.

For example, a marketing automation workflow could update a contact’s phone number and add new tags after a customer support interaction.

Properties

Name Meaning
Contact Identifier Choose how to identify the contact to update: by UUID (unique identifier) or Email address.
Email The contact's email address. Required if identifying by email or optionally used when identifying by UUID to update the email field.
UUID The unique identifier of the contact. Required if identifying by UUID.
Additional Fields A collection of optional fields to update on the contact, including:
• Bio (notes about the contact)
• Birthday Date
• City
• Country
• Custom Fields (arbitrary key-value pairs)
• Facebook URL
• Job Title
• Linkedin URL
• Mobile Phone
• Name
• Phone
• State
• Tags (comma-separated list replacing existing tags)
• Twitter URL
• Website URL

Output

The node outputs the updated contact object as JSON. This includes all the contact properties returned by the RD Station API after the update operation. The output does not contain binary data.

Example output structure (simplified):

{
  "id": "uuid-string",
  "email": "name@email.com",
  "name": "John Doe",
  "job_title": "CEO",
  "city": "New York",
  "country": "USA",
  "tags": ["tag1", "tag2"],
  "custom_fields": {
    "field_key": "value"
  },
  ...
}

Dependencies

  • Requires an active connection to the RD Station Marketing API.
  • Needs an API authentication token configured in n8n credentials for RD Station.
  • Uses HTTP PATCH requests to update contact data via /platform/contacts/{identifier}:{value} endpoint.

Troubleshooting

  • Missing Identifier Error: If you select to identify the contact by email but do not provide an email, or by UUID without providing a UUID, the node will throw an error indicating the required field is missing. Ensure the correct identifier and its value are provided.
  • API Request Failures: Network issues or invalid API credentials can cause request failures. Verify your API key/token and network connectivity.
  • Invalid Field Values: Providing unsupported or incorrectly formatted values in additional fields may result in API errors. Validate field formats, especially dates and URLs.
  • Tags Replacement: When updating tags, note that the new tags replace existing ones rather than appending. To preserve tags, include all desired tags in the update.

Links and References

Discussion