LEMLIST n8n INTEGRATION: AUTOMATE LEMLIST WITH N8N

This trigger activates the moment your Lemwarm email warming sequence gets paused. It's essential for maintaining email deliverability—when warming stops unexpectedly, you need to know immediately to prevent your sender reputation from degrading.

Configuration: The trigger requires selecting your Lemlist account credential for authentication, setting the event to "Lemwarm Paused," and optionally adding custom fields for filtering behavior.

Use cases: Send urgent Slack alerts when Lemwarm pauses unexpectedly, automatically create a high-priority task in Asana to investigate, log warming interruptions to a Google Sheet for deliverability tracking, or trigger a backup warming sequence on a secondary domain.

When to use it: Essential for any team relying on Lemwarm to maintain inbox placement. Pair with monitoring dashboards to catch deliverability issues before they impact campaign performance.

This trigger fires when your Lemlist account hits its daily sending limit, preventing any further outreach until the limit resets. It's crucial for high-volume senders who need to manage multiple campaigns across sending limits.

Configuration: Select your Lemlist credential, set the event to "Send Limit Reached," and optionally add custom fields for extended configuration.

Use cases: Notify your team via email when limits are reached, automatically pause dependent workflows that feed leads to Lemlist, switch sending to a secondary Lemlist account, or log limit events to analyze sending patterns over time.

When to use it: Critical for agencies managing multiple client accounts or teams running aggressive outreach campaigns who need to maximize daily sending without overshooting limits.

This trigger activates when Lemlist encounters a connection problem—whether with your email provider, LinkedIn account, or other integrated services. It's your early warning system for technical issues that could silently kill your campaigns.

Configuration: Requires selecting Lemlist credentials and setting the event to "Connection Issue" with optional fields for advanced filtering.

Use cases: Send PagerDuty alerts for critical connection failures, automatically pause campaigns to prevent send failures from hurting deliverability, create IT tickets in Jira when connection issues arise, or log connection problems for post-mortem analysis.

When to use it: Must-have for any team where email deliverability directly impacts revenue. Connection issues left unaddressed can tank your sender reputation overnight.

This trigger fires when a paused Lemlist campaign or sequence resumes sending. It's useful for coordinating activities that should only happen when outreach is actively running.

Configuration: Requires Lemlist credential selection, event set to "Resumed," and optional fields for custom trigger behavior.

Use cases: Notify sales reps that outreach has restarted, re-enable related workflows that were paused, update campaign status dashboards, or log resume events for campaign lifecycle tracking.

When to use it: Ideal for teams with complex, multi-stage outreach where pausing and resuming campaigns requires coordination across multiple systems.

This trigger activates when a Lemlist campaign or sequence gets paused, whether manually or automatically. It's the counterpart to "Resumed" and essential for maintaining workflow consistency.

Configuration: Select Lemlist credentials, set event to "Paused," and add custom fields for filtering as needed.

Use cases: Automatically pause downstream workflows feeding leads to the paused campaign, notify campaign managers via Slack, update CRM fields to reflect paused outreach status, or create tasks to review why the campaign was paused.

When to use it: Critical for teams running multiple concurrent campaigns where pausing one impacts lead routing and sales follow-up timing.

This trigger fires when you manually mark a lead as "not interested" in Lemlist. It's perfect for syncing manual sales decisions across your entire tech stack.

Configuration: Requires selecting Lemlist credentials and setting event to "Manual Not Interested" with optional customization fields.

Use cases: Update lead status in Salesforce or HubSpot, add email to suppression lists across all outreach tools, trigger re-engagement sequences in 6 months, or update lead scoring models with negative signals.

When to use it: Essential for sales teams who manually qualify leads and need those decisions reflected everywhere.

This trigger activates when you manually mark a lead as "interested" in Lemlist—a strong buying signal that warrants immediate action.

Configuration: Select Lemlist credentials, set event to "Manual Interested," and add optional fields for customization.

Use cases: Instantly create a deal in your CRM with high priority, send real-time Slack notifications to account executives, trigger personalized video creation via Loom or Vidyard, or schedule calendar events for follow-up calls.

When to use it: Perfect for teams where manual lead qualification triggers immediate sales action.

This trigger fires when a LinkedIn message fails to send through Lemlist's LinkedIn automation. Failed sends can indicate blocked accounts, rate limits, or technical issues requiring immediate attention.

Configuration: Requires Lemlist credential, event set to "LinkedIn Send Failed," and optional configuration fields.

Use cases: Alert your team to potential LinkedIn account restrictions, automatically pause LinkedIn sequences to prevent further failures, create tasks to manually send the failed message, or log failures for LinkedIn health monitoring.

When to use it: Critical for any team using Lemlist's LinkedIn automation features where failed sends could indicate account health issues.

This trigger activates when a LinkedIn prospect indicates they're not interested. It helps you maintain list hygiene and respect prospect preferences across channels.

Configuration: Select Lemlist credentials, set event to "LinkedIn Not Interested," and add optional fields for extended customization.

Use cases: Remove from email sequences as well, update CRM with LinkedIn-specific disposition, add to "do not contact on LinkedIn" suppression list, or analyze rejection patterns by industry or title.

When to use it: Essential for multi-channel outreach where LinkedIn engagement signals should influence email cadence.

This trigger fires when a LinkedIn prospect shows interest through Lemlist's LinkedIn integration—a high-intent signal that often converts better than email engagement.

Configuration: Requires Lemlist authentication, event set to "LinkedIn Interested," and optional fields available.

Use cases: Fast-track to sales team with high priority flag, send personalized email follow-up referencing LinkedIn conversation, create opportunity in CRM with LinkedIn as source, or trigger account-based marketing for prospect's company.

When to use it: Perfect for B2B teams where LinkedIn interest correlates strongly with purchase intent.

This trigger monitors for failures when sending LinkedIn voice notes through Lemlist. Voice notes have high engagement rates, so failures need quick attention.

Configuration: Select Lemlist credential, set event to "LinkedIn Voice Note Failed," and add optional fields as needed.

Use cases: Create tasks to manually send voice notes, alert team members responsible for LinkedIn outreach, log voice note failures for troubleshooting, or switch to alternative contact methods automatically.

When to use it: Important for teams leveraging voice notes as a differentiation strategy in LinkedIn outreach.

This trigger fires when a LinkedIn voice note successfully sends, allowing you to track engagement with this high-touch outreach method.

Configuration: Requires Lemlist credential, event set to "LinkedIn Voice Note Done," and optional configuration fields.

Use cases: Log successful voice notes for engagement tracking, trigger follow-up sequences timed to voice note delivery, update activity logs in CRM, or notify sales reps that voice note was delivered.

When to use it: Useful for teams tracking voice note performance and timing follow-ups accordingly.

This trigger activates whenever a LinkedIn message successfully sends through Lemlist, helping you track LinkedIn outreach activity.

Configuration: Requires credential dropdown for authentication, event set to "LinkedIn Sent," and optional parameters for customization.

Use cases: Update activity feeds in your CRM, track LinkedIn send volumes over time, trigger delayed follow-up actions, or sync LinkedIn touchpoints with email sequences.

When to use it: Essential for teams tracking multi-channel touchpoint density and timing.

This trigger fires when a prospect replies to your LinkedIn message—one of the highest-intent signals in B2B outreach.

Configuration: Requires Lemlist credential selection, event set to "LinkedIn Replied," and optional trigger refinement fields.

Use cases: Instantly notify sales reps via Slack or SMS, create high-priority tasks for immediate follow-up, update lead status and scoring in CRM, or pause email sequences to avoid over-communication.

When to use it: Critical trigger for any team doing LinkedIn outreach. LinkedIn replies often signal higher intent than email opens.

This trigger activates when a prospect accepts your LinkedIn connection request, expanding your network and opening direct messaging.

Configuration: Requires authentication credential, event set to "LinkedIn Invite Accepted," and optional fields for extended configuration.

Use cases: Trigger personalized welcome messages, add to specific LinkedIn nurture sequences, update CRM with network expansion data, or notify sales reps of new connections in their territory.

When to use it: Perfect for teams using connection requests as a top-of-funnel strategy before direct outreach.

This trigger monitors for failed LinkedIn connection requests, which can indicate profile restrictions, rate limits, or targeting issues.

Configuration: Requires Lemlist credential, event set to "LinkedIn Invite Failed," and optional customization fields.

Use cases: Alert team to potential LinkedIn account issues, automatically reduce daily invite volume, create tasks to review targeting criteria, or log failures for account health monitoring.

When to use it: Important for maintaining LinkedIn account health during aggressive connection campaigns.

This trigger fires when a LinkedIn connection request is successfully sent, allowing you to track invite activity.

Configuration: Requires credential selection, event set to "LinkedIn Invite Done," and optional configuration fields.

Use cases: Track daily invite volumes, update prospect records with touchpoint data, trigger follow-up actions based on invite timing, or sync invite activity to CRM.

When to use it: Useful for teams monitoring LinkedIn outreach volume and pacing.

This trigger activates when a LinkedIn profile visit fails, which can indicate technical issues or account restrictions.

Configuration: Requires Lemlist credential dropdown, event set to "LinkedIn Visit Failed," and optional fields as needed.

Use cases: Alert team to investigate LinkedIn account status, log failures for pattern analysis, trigger alternative engagement strategies, or pause campaigns to protect account health.

When to use it: Important for teams using profile visits as a warming strategy before connection requests.

This trigger fires when a LinkedIn profile visit successfully completes, letting you track this soft-touch engagement tactic.

Configuration: Requires authentication credential, event set to "LinkedIn Visit Done," and optional configuration available.

Use cases: Log profile visits for engagement tracking, trigger timed follow-up actions, update multi-touch attribution data, or sync visit activity with CRM records.

When to use it: Useful for teams implementing multi-touch LinkedIn strategies with profile visits as an initial touchpoint.

This trigger fires when a lead receives their first outreach touchpoint, marking the beginning of the engagement sequence.

Configuration: Requires credential dropdown, event set to "Contacted," and optional fields as needed.

Use cases: Log initial contact in CRM, update lead status from "new" to "contacted", start engagement timing clocks, or trigger parallel awareness campaigns.

When to use it: Essential for accurate pipeline reporting and touchpoint tracking.