How to connect RD Station and Delighted
Create a New Scenario to Connect RD Station and Delighted
In the workspace, click the “Create New Scenario” button.

Add the First Step
Add the first node – a trigger that will initiate the scenario when it receives the required event. Triggers can be scheduled, called by a RD Station, triggered by another scenario, or executed manually (for testing purposes). In most cases, RD Station or Delighted will be your first step. To do this, click "Choose an app," find RD Station or Delighted, and select the appropriate trigger to start the scenario.

Add the RD Station Node
Select the RD Station node from the app selection panel on the right.


RD Station

Configure the RD Station
Click on the RD Station node to configure it. You can modify the RD Station URL and choose between DEV and PROD versions. You can also copy it for use in further automations.
Add the Delighted Node
Next, click the plus (+) icon on the RD Station node, select Delighted from the list of available apps, and choose the action you need from the list of nodes within Delighted.


RD Station
⚙
Delighted

Authenticate Delighted
Now, click the Delighted node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your Delighted settings. Authentication allows you to use Delighted through Latenode.
Configure the RD Station and Delighted Nodes
Next, configure the nodes by filling in the required parameters according to your logic. Fields marked with a red asterisk (*) are mandatory.
Set Up the RD Station and Delighted Integration
Use various Latenode nodes to transform data and enhance your integration:
- Branching: Create multiple branches within the scenario to handle complex logic.
- Merging: Combine different node branches into one, passing data through it.
- Plug n Play Nodes: Use nodes that don’t require account credentials.
- Ask AI: Use the GPT-powered option to add AI capabilities to any node.
- Wait: Set waiting times, either for intervals or until specific dates.
- Sub-scenarios (Nodules): Create sub-scenarios that are encapsulated in a single node.
- Iteration: Process arrays of data when needed.
- Code: Write custom code or ask our AI assistant to do it for you.

JavaScript
⚙
AI Anthropic Claude 3
⚙
Delighted
Trigger on Webhook
⚙

RD Station
⚙
⚙
Iterator
⚙
Webhook response

Save and Activate the Scenario
After configuring RD Station, Delighted, and any additional nodes, don’t forget to save the scenario and click "Deploy." Activating the scenario ensures it will run automatically whenever the trigger node receives input or a condition is met. By default, all newly created scenarios are deactivated.
Test the Scenario
Run the scenario by clicking “Run once” and triggering an event to check if the RD Station and Delighted integration works as expected. Depending on your setup, data should flow between RD Station and Delighted (or vice versa). Easily troubleshoot the scenario by reviewing the execution history to identify and fix any issues.
Most powerful ways to connect RD Station and Delighted
Delighted + RD Station + Slack: When a new response is received in Delighted, the automation checks for the corresponding contact data in RD Station. If the Delighted score is below a certain threshold, a notification is sent to a Slack channel with the customer's details.
Delighted + RD Station + Google Sheets: When a new response is submitted in Delighted, the automation fetches corresponding contact details from RD Station and adds both the survey response data and the contact information to a new row in a Google Sheet for analysis.
RD Station and Delighted integration alternatives

About RD Station
Use RD Station in Latenode to automate marketing tasks. Update leads, trigger personalized emails, and track campaign performance, all inside automated workflows. Integrate RD Station data with other apps, enrich with AI, and build custom logic without code. Scale your marketing automation affordably and visually.
Related categories
About Delighted
Automate feedback loops with Delighted in Latenode. Send surveys post-interaction and instantly act on results. Route scores to your team's Slack, update records in your CRM, or trigger follow-ups based on sentiment. Build adaptable workflows with no-code tools, custom logic, and AI — all without per-step costs.
Related categories
See how Latenode works
FAQ RD Station and Delighted
How can I connect my RD Station account to Delighted using Latenode?
To connect your RD Station account to Delighted on Latenode, follow these steps:
- Sign in to your Latenode account.
- Navigate to the integrations section.
- Select RD Station and click on "Connect".
- Authenticate your RD Station and Delighted accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I trigger surveys based on RD Station conversion events?
Yes, you can! With Latenode, automate Delighted surveys based on RD Station conversions. Use visual logic or JavaScript for advanced segmentation and personalized timing, boosting response rates.
What types of tasks can I perform by integrating RD Station with Delighted?
Integrating RD Station with Delighted allows you to perform various tasks, including:
- Automatically trigger Delighted surveys after a lead converts in RD Station.
- Update RD Station contact properties based on Delighted survey responses.
- Send personalized thank-you notes via RD Station based on positive feedback.
- Create RD Station leads from new Delighted survey submissions.
- Track customer satisfaction scores alongside marketing campaign performance.
Can I use custom JavaScript to transform data between RD Station and Delighted?
Yes! Latenode supports custom JavaScript code to transform data between RD Station and Delighted, enabling tailored workflows and advanced data manipulation.
Are there any limitations to the RD Station and Delighted integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Real-time data synchronization depends on the API rate limits of both platforms.
- Complex data transformations may require JavaScript knowledge.
- Historical data migration between the two platforms is not directly supported.