SENDY n8n INTEGRATION: AUTOMATE SENDY WITH N8N

This action is the foundation of most Sendy automation workflows. It allows you to programmatically add new subscribers to any of your Sendy mailing lists, complete with custom fields and preferences.

Key parameters:

• Email: The subscriber's email address you want to add to your list. This is a required text field that accepts any valid email format.
• List ID: The unique identifier of the Sendy mailing list where the subscriber will be added. You can find this ID in your Sendy list settings. This field is required.
• Additional Fields: Optional custom properties you can attach to the subscriber, such as name, company, or any custom fields you've configured in Sendy.

Use cases:

• Automatically subscribe new customers from Stripe, PayPal, or any payment processor
• Add form submissions from Typeform, Gravity Forms, or custom web forms to targeted lists
• Sync new CRM contacts from HubSpot or Pipedrive to your newsletter
• Subscribe users who complete specific actions in your application

Need to verify if someone is subscribed before taking action? This action retrieves the current subscription status of any email address on a specific list. It's essential for building conditional workflows that behave differently based on subscription state.

Key parameters:

• Credential to connect with: A required dropdown to select your Sendy account credentials for authentication.
• Resource: Set to "Subscriber" to indicate you're working with subscriber data.
• Operation: Set to "Status" to retrieve the subscription state.
• Email: The email address you want to check. This is a required text field.
• List ID: The unique identifier of the mailing list to check against. Required for the status lookup.

Use cases:

• Check if a user is subscribed before sending them a promotional offer via another channel
• Build conditional logic that adds users only if they're not already subscribed
• Verify subscription status before processing refunds or cancellations
• Create re-engagement workflows targeting users who have unsubscribed

When to use it: Use this action at the beginning of workflows where the next steps depend on whether someone is actively subscribed, unsubscribed, or has never been on your list.

This action removes a subscriber from a specific mailing list without permanently deleting their data. The subscriber won't receive emails from that list but can be re-added later. Perfect for honoring unsubscribe requests or managing list segmentation.

Key parameters:

• Email: The email address of the subscriber to remove from the list. Required text input.
• List ID: The unique identifier of the mailing list from which to remove the subscriber. Required field.

Use cases:

• Process unsubscribe requests from your custom preference center or webhook
• Remove subscribers who downgrade from a paid plan and shouldn't receive premium content
• Clean lists by removing bounced emails detected by external validation services
• Implement cooling-off periods where users are temporarily removed then re-added

Unlike the "Remove" action, Delete Subscriber permanently removes all data associated with an email address. Use this for GDPR compliance, data cleanup, or when a subscriber requests complete data deletion.

Key parameters:

• Email: The email address of the subscriber to permanently delete. Required field.
• List ID: Optional field to specify a particular list. If left blank, the subscriber is deleted from ALL lists they belong to—use with caution.

Use cases:

• Honor GDPR "right to be forgotten" requests automatically
• Permanently remove fake or spam email addresses from your entire database
• Clean up test subscribers after development or QA processes
• Implement complete data deletion when users close their accounts

💡 TIP: Before using Delete Subscriber without a List ID, always confirm the action with the user or implement a confirmation step in your workflow. Deleting from all lists is irreversible and affects every mailing list in your Sendy installation.

This action returns the total number of active subscribers on a specific mailing list. It's invaluable for monitoring list growth, triggering milestone-based workflows, and generating reports.

Key parameters:

• Credential to connect with: Required dropdown to select your Sendy authentication credentials.
• Resource: Set to "Subscriber" for subscriber-related operations.
• Operation: Set to "Count" to retrieve the subscriber total.
• List ID: The unique identifier of the list you want to count. This field is required.

Use cases:

• Schedule daily or weekly subscriber count snapshots to Google Sheets or Airtable for growth tracking
• Trigger celebration notifications when you hit subscriber milestones (1,000, 10,000, etc.)
• Monitor list health by comparing counts over time and alerting on unusual drops
• Feed subscriber metrics into dashboards built with tools like Geckoboard or Databox

The most powerful action in the Sendy n8n integration. Create Campaign lets you programmatically generate email campaigns complete with sender details, subject lines, and full HTML content. Combined with n8n's other nodes, you can automate your entire content distribution workflow.

Key parameters:

• From Name: The sender name recipients will see. Required text field.
• From Email: The email address the campaign is sent from. Must be a verified sender in your Sendy/SES setup. Required.
• Reply To: Optional email address for replies if different from the sender address.
• Title: Internal campaign name for your Sendy dashboard. Required for organization.
• Subject: The email subject line your recipients see. Required and crucial for open rates.
• HTML Text: The full HTML content of your email. Required. Can include dynamic data from previous n8n nodes.
• Send Campaign: Optional toggle. When enabled, the campaign sends immediately upon creation. Leave disabled to save as draft.
• Brand ID: Optional field for multi-brand Sendy installations to specify which brand the campaign belongs to.

Use cases:

• Automatically create and send digest emails when new blog posts are published via WordPress
• Generate personalized campaign drafts from CRM data for sales teams to review
• Create product announcement emails triggered by inventory or pricing changes
• Build automated drip campaigns where each email is dynamically generated based on user behavior