Letterdrop Workflows let you automate LinkedIn outreach based on buying signals. You build logic by chaining together different types of nodes:
- Source nodes: Where leads come from
- Filter nodes: Rules to qualify leads
- Action nodes: What to do once a lead qualifies
This guide covers each node type, its properties, and how to use them.
🟢 Source Nodes (Lead Triggers)
These nodes define where your leads come from - whether they engaged on LinkedIn, were sent via webhook, or appeared in your CRM.
Node | Purpose | Key Properties | Notes |
Aware of Team | Trigger for leads who engaged with your team or company page | Rotate sender based on capacity | Use to engage people already interacting with your team |
Competitor & Influencers | Lead liked or commented on a tracked competitor or influencer post | Rotate sender based on capacity | Requires active keyword/competitor monitoring |
Posted About Relevant Topic | Lead made a post that contains a tracked keyword | Rotate sender based on capacity | Great for signals |
Account Monitoring | Lead posted and is part of a target account list | Rotate sender based on capacity | Targets decision makers already in your ICP |
Closed Lost Deals | Filters for leads who were marked as closed/lost in your CRM | N/A | Helps re-engage former pipeline |
External Lead | Trigger leads from tools like Clay, RB2B, Vector via webhook | Webhook URL, api-key header, JSON payload (lead is required) | Way to push in external intent data; Use in Campaigns |
Competitor/Influencer Monitored Post | Leads who engaged with posts you’re tracking from keywords or competitors | N/A | Requires active keyword/competitor monitoring |
🟡 Filter Nodes (Qualification Logic)
These let you gate or route leads based on firmographics, CRM data, awareness stage, or past activity.
Node | Purpose | Key Properties | Notes |
Firmographic Filter | Filters based on buyer profile (size, industry, etc.) | Set default in Knowledge Base; Use Deal Stages to filter existing customers from CRM | Can be reused across workflows |
Awareness Stage Filter | Filters based on lead’s stage in buying journey | Choose awareness level + recommended action | Helps tailor outreach messaging |
Profiles or Keyword Group Filter | Filters leads based on specific keyword groups or profiles | Select tracked | Combine with source nodes for tighter targeting |
Post Boolean Filter | Filters based on AI-generated true/false answer from post context | Define prompt | Good for opinionated or behavioral signals |
Target Account Filter | Filters if lead belongs to target accounts list | Select from your account lists | Focuses workflow on high-value targets |
Lead Exists in CRM | Filters leads already in your CRM | Match contact or account fields (equals, contains, etc.) | Prevents duplicates or unwanted outreach |
LLM Question Filter | Uses AI to answer a true/false question about a lead | Define question | Adds nuance with natural language logic |
Last Outreach Filter | Filters based on time since last outreach | Choose activity type (DM, Connect) + time window | Prevents spamming leads too soon |
If Connected | Branches logic based on LinkedIn connection status | Choose path for “connected” or “not connected” | Useful for fallback InMail if not connected |
🔴 Action Nodes (What Happens Next)
These nodes define what to do with qualified leads — from DMs to Slack alerts.
Node | Purpose | Key Properties | Notes |
Like Post | Likes the lead’s post from a selected account | Select account(s) | Good low-effort engagement |
Comment on Post | Comments from selected account | Choose manual or AI message | Boosts visibility with thoughtful replies |
Connect with Lead | Sends a connection request | Select account; choose manual or AI message | Can customize per persona |
DM Lead | Sends a direct message | Choose manual or AI message; optional approval step; DM delay | Most effective when post is recent |
Send InMail | Sends InMail if not connected | Select account; message options | Use with If Connected node |
Email Alert | Sends an email to a team member | Add email address | Useful for manual follow-ups |
Add to Apollo Sequence | Pushes lead to a pre-built Apollo sequence | Choose sequence, template, sender account | Requires Apollo integration |
Send to Webhook | Sends lead to external tools (e.g. Clay) | Webhook URL, payload fields | Use to enrich or track leads elsewhere |
Post to Slack Channel | Shares lead in a Slack channel | Select Slack channel | For real-time rep notification |
DM to Slack User | Sends a Slack DM to specific teammate | Choose user | Great for fast handoff to BDRs |
Wait | Delays next step for set number of days | Choose delay duration | Helps stagger outreach and follow-ups |
✅ Best Practices
- Use External Lead node to bring in data from enrichment tools like Clay and RB2B.
- Pair Target Account Filter + Keyword Group Filter for high-intent ICP targeting.
- Always add an “If Connected” node before a Connect and DM actions
- For outbound coordination, use Post to Slack to keep sales in the loop.
🙋♀️ FAQs
Q: Can I use multiple source nodes?
No — a workflow will start with only one source node.
Q: What's the difference between AI and manual messages?
AI messages are generated using much more context and the DM prompt we use by default. Manual messages are fully written by you.
Q: What happens if a Filter blocks a lead?
The lead exits the workflow — it won’t reach the action steps.