Toolzz RD icon

Toolzz RD

ToolzzRd

Toolzz RD

AI-generated

Overview

The Toolzz RD node is designed to interact with the RD Station API, allowing users to perform HTTP requests (GET, PUT, POST, PATCH) to various endpoints of the RD Station platform. This node is useful for integrating n8n workflows with RD Station, enabling automation such as sending data, updating records, or retrieving information from the RD Station system.

Common scenarios:

  • Sending leads or contact data to RD Station.
  • Updating existing records in RD Station via API.
  • Retrieving information about contacts, deals, or other resources from RD Station.
  • Automating marketing and sales processes by connecting RD Station with other tools.

Practical example:
You could use this node to automatically send new lead information collected from a web form to RD Station, or to update a contact's status after a specific event occurs in your workflow.

Properties

Name Type Meaning
Local String The endpoint path within the RD Station API (e.g., "leads", "contacts").
Chamada String The request body to be sent with the API call (for POST/PUT/PATCH).
Method String The HTTP method to use: GET, PUT, POST, or PATCH.
Token RdStation String The access token used for authenticating with the RD Station API.

Output

The node outputs the JSON response returned by the RD Station API. The structure of this output depends on the specific endpoint and operation performed, but it will always be a JSON object or array as provided by the API.

Example output:

{
  "id": "12345",
  "name": "John Doe",
  "email": "john@example.com"
}

Note: The actual fields depend on the API endpoint you call.

Dependencies

  • External Service: Requires access to the RD Station API.
  • API Key: You must provide a valid RD Station access token ("Token RdStation" property).
  • n8n Configuration: No special configuration required beyond standard network access.

Troubleshooting

Common issues:

  • Invalid or expired access token: If the "Token RdStation" is incorrect or expired, the API will return an authentication error. Ensure your token is valid.
  • Incorrect endpoint ("Local"): Providing an invalid or misspelled endpoint path may result in 404 errors or unexpected responses.
  • Malformed request body ("Chamada"): For methods like POST or PUT, ensure the body is valid JSON and matches the expected schema for the endpoint.
  • Unsupported HTTP method: Only GET, PUT, POST, and PATCH are supported. Using another method will cause errors.

Common error messages:

  • 401 Unauthorized: Check your access token.
  • 404 Not Found: Verify the "Local" property (endpoint path).
  • 400 Bad Request: Check the format and content of your "Chamada" (body).

Links and References

Discussion