How to connect RD Station and SOS Inventory
Create a New Scenario to Connect RD Station and SOS Inventory
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 SOS Inventory will be your first step. To do this, click "Choose an app," find RD Station or SOS Inventory, 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 SOS Inventory Node
Next, click the plus (+) icon on the RD Station node, select SOS Inventory from the list of available apps, and choose the action you need from the list of nodes within SOS Inventory.


RD Station
β
SOS Inventory

Authenticate SOS Inventory
Now, click the SOS Inventory node and select the connection option. This can be an OAuth2 connection or an API key, which you can obtain in your SOS Inventory settings. Authentication allows you to use SOS Inventory through Latenode.
Configure the RD Station and SOS Inventory 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 SOS Inventory 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
β
SOS Inventory
Trigger on Webhook
β

RD Station
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring RD Station, SOS Inventory, 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 SOS Inventory integration works as expected. Depending on your setup, data should flow between RD Station and SOS Inventory (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 SOS Inventory
RD Station + SOS Inventory + Slack: When a deal is won in RD Station, SOS Inventory creates a sales order and Slack notifies the sales team about the new order.
SOS Inventory + RD Station + QuickBooks: When stock is low (simulated by a new sales order) in SOS Inventory, a new lead is created in RD Station, and a new customer record is created in QuickBooks.
RD Station and SOS Inventory 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 SOS Inventory
Sync SOS Inventory with Latenode to automate stock updates and order processing. Connect your inventory data to accounting, e-commerce, or shipping platforms. Build visual workflows to trigger actions based on inventory levels or sales data. Use no-code tools or custom scripts to tailor the flow, avoiding manual data entry and ensuring real-time accuracy.
Related categories
See how Latenode works
FAQ RD Station and SOS Inventory
How can I connect my RD Station account to SOS Inventory using Latenode?
To connect your RD Station account to SOS Inventory 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 SOS Inventory accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update SOS Inventory with new RD Station leads?
Yes, you can! Latenode lets you sync new leads from RD Station to SOS Inventory, automatically updating inventory data. Enjoy seamless lead-driven stock management.
What types of tasks can I perform by integrating RD Station with SOS Inventory?
Integrating RD Station with SOS Inventory allows you to perform various tasks, including:
- Create new SOS Inventory customers from qualified RD Station leads.
- Update SOS Inventory stock levels based on successful RD Station sales.
- Trigger RD Station marketing actions based on SOS Inventory stock alerts.
- Send personalized emails via RD Station after SOS Inventory order fulfillment.
- Generate sales reports by combining RD Station data with SOS Inventory data.
How does Latenode handle data mapping between RD Station and SOS Inventory?
Latenode offers visual data mapping, with JavaScript steps for advanced transformations, ensuring accurate data transfers every time.
Are there any limitations to the RD Station and SOS Inventory integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex custom fields in RD Station might require advanced scripting.
- Real-time updates depend on the API request limits of both platforms.
- Historical data migration might require batch processing strategies.