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 - Get operation retrieves detailed information about a single contact using either their unique UUID or email address. This is useful for workflows that need to fetch up-to-date contact data for personalization, segmentation, or further processing.

Common scenarios:

  • Fetching a contact's profile before updating their information.
  • Retrieving contact details to trigger conditional logic in automation.
  • Verifying if a contact exists in RD Station before creating or tagging them.

Practical example:
A marketing automation workflow could use this node to get a contact by email when they fill out a form, then decide whether to update their record or add them to a specific campaign based on the retrieved data.

Properties

Name Meaning
Contact Identifier Choose how to identify the contact: by UUID (unique identifier) or Email address.
Email The contact's email address. Required if "Email" is chosen as the identifier.
UUID The contact's unique UUID. Required if "UUID" is chosen as the identifier.

Output

The node outputs a JSON object representing the contact's data as returned by the RD Station Marketing API. This includes all available fields of the contact such as name, email, job title, custom fields, tags, and other metadata.

  • The output does not include any binary data.
  • The json output contains the full contact record without internal links metadata (these are removed before output).

Example output structure (simplified):

{
  "id": "a111bc22-1234-1234-a1a1-ab12c345d67f",
  "email": "name@email.com",
  "name": "John Doe",
  "job_title": "CEO",
  "tags": ["tag1", "tag2"],
  "custom_fields": {
    "field_name": "value"
  },
  ...
}

Dependencies

  • Requires an API authentication token credential configured in n8n to access the RD Station Marketing API.
  • The node uses HTTP requests to RD Station endpoints under /platform/contacts.
  • No additional external dependencies beyond the RD Station API and n8n credential setup.

Troubleshooting

  • Missing Identifier Error:
    If you select "Email" as the identifier but do not provide an email address, or select "UUID" but leave it empty, the node will throw an error indicating the required field is missing. Ensure the correct identifier value is provided.

  • Contact Not Found:
    If the contact does not exist for the given identifier, the API may return an error or empty response. Handle this case in your workflow by checking for empty results or errors.

  • API Authentication Errors:
    If the API key or OAuth token is invalid or expired, the node will fail. Verify your credentials and re-authenticate if necessary.

  • Rate Limits or Network Issues:
    Temporary failures due to rate limits or connectivity can cause errors. Use the "Continue On Fail" option in n8n to handle retries or fallback logic.

Links and References

Discussion