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


RD Station
β
Woodpecker

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

RD Station
β
β
Iterator
β
Webhook response

Save and Activate the Scenario
After configuring RD Station, Woodpecker, 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 Woodpecker integration works as expected. Depending on your setup, data should flow between RD Station and Woodpecker (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 Woodpecker
Woodpecker + RD Station + Google Sheets: When an email is opened in Woodpecker, the data is sent to RD Station. A new row is then added to a Google Sheet to track campaign engagement and lead data.
RD Station + Woodpecker + Slack: When a new lead conversion occurs in RD Station, find the prospect in Woodpecker using their email, then send a message to a Slack channel alerting sales reps.
RD Station and Woodpecker 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 Woodpecker
Use Woodpecker in Latenode to automate personalized email outreach at scale. Trigger Woodpecker campaigns from any Latenode workflow (e.g., new CRM leads) and track results. Enrich contact data, personalize messages with AI, and route follow-ups based on engagement. All visually, with full Javascript customization if needed.
Related categories
See how Latenode works
FAQ RD Station and Woodpecker
How can I connect my RD Station account to Woodpecker using Latenode?
To connect your RD Station account to Woodpecker 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 Woodpecker accounts by providing the necessary permissions.
- Once connected, you can create workflows using both apps.
Can I automatically update RD Station when Woodpecker finds a lead?
Yes, with Latenode! Automatically update RD Station contact properties based on Woodpecker campaign results. Use our visual editor and JavaScript blocks for advanced data transformations and enrichment.
What types of tasks can I perform by integrating RD Station with Woodpecker?
Integrating RD Station with Woodpecker allows you to perform various tasks, including:
- Add new RD Station leads when Woodpecker identifies a qualified prospect.
- Update RD Station contact lifecycle stages based on Woodpecker email engagement.
- Create RD Station tasks when a Woodpecker email campaign reaches a specific milestone.
- Sync RD Station contact information with Woodpecker's prospect database.
- Trigger personalized Woodpecker email sequences based on RD Station events.
How do I handle errors during RD Station and Woodpecker data syncs?
Latenode provides robust error handling. Use conditional logic and error-handling blocks to manage failed RD Station/Woodpecker syncs and trigger notifications.
Are there any limitations to the RD Station and Woodpecker integration on Latenode?
While the integration is powerful, there are certain limitations to be aware of:
- Complex data transformations may require JavaScript coding.
- Rate limits on RD Station and Woodpecker APIs can affect workflow speed.
- Historical data migration might need a separate, one-time setup.