n8n Integration

CampaignKit integrates with n8n through a community node, bringing powerful email validation capabilities to your workflow automation. Whether you’re self-hosting n8n or using the cloud version, you can validate emails in real-time or process large batches asynchronously.

How It Works

The CampaignKit n8n community node provides:

• Validate Email - Verify a single email address and get instant results with detailed quality metrics
• Validate Batch - Submit multiple emails for asynchronous batch processing (up to thousands at once)
• Get Job Status - Retrieve the status and results of batch validation jobs
• Job Completed Trigger - Automatically trigger workflows when validation jobs finish via webhook

CampaignKit validates each email using multiple verification techniques including syntax checks, domain validation, MX record verification, and SMTP validation.

What You Can Build

Here are some popular use cases for the CampaignKit n8n integration:

Real-Time Form Validation

Validate email addresses from webhook submissions or HTTP endpoints before storing them in your database. Perfect for API-first applications that need instant validation results.

Scheduled List Cleaning

Set up recurring workflows that validate email lists stored in databases like PostgreSQL, MySQL, or MongoDB. Update records with validation scores and flag risky addresses automatically.

Batch Processing with Notifications

Submit large email lists for batch validation and use webhook triggers to receive notifications when jobs complete. Process results and update your systems automatically.

Multi-Step Validation Pipelines

Build complex workflows that combine email validation with other operations like data enrichment, CRM updates, or notification delivery based on validation results.

Data Quality Enforcement

Integrate validation into your data pipelines to ensure only valid email addresses enter your marketing automation platforms, CRMs, or data warehouses.

Validation Results

When you validate an email through n8n, CampaignKit returns comprehensive results including:

• Score - Quality score from 0-10 indicating deliverability
  • 10: Valid - All checks passed, email is deliverable
  • 9: Valid but unverified - Syntax and MX checks passed
  • 2: Risky - Email exists but may be suspicious
  • 0: Invalid - Email will bounce
• Status Flags - Boolean indicators for email characteristics:
  • is_valid - Email is deliverable (score 9-10)
  • is_invalid - Email will bounce (score 0)
  • is_risky - Email may be a spam trap or temporary
  • is_disposable - Temporary/disposable email service
  • is_role_email - Generic role address (info@, support@)
  • is_catchall - Domain accepts all email addresses
  • is_blacklisted - Email is on CampaignKit’s blacklist
• Classifier - Human-readable classification (valid, invalid, risky)
• Domain Info - MX records, SMTP provider, free email provider detection
• Suggestions - Typo corrections (did_you_mean field for common misspellings)

Use these results in your workflow logic to:

• Filter out invalid emails before saving to your database
• Route risky emails to a separate list for manual review
• Tag or classify contacts based on email quality
• Trigger different actions based on validation status
• Generate reports on email list quality

Setup Process

Step 1: Install the Community Node

Option A: Via n8n UI (Recommended)

1. Open your n8n instance
2. Navigate to Settings > Community Nodes
3. Click Install
4. Enter n8n-nodes-campaignkit in the npm package name field
5. Click Install and wait for installation to complete

Option B: Manual Installation (Self-Hosted)

For self-hosted n8n instances, you can install via npm:

npm install n8n-nodes-campaignkit

For Docker-based installations, add the package to your n8n Docker image or install it in your running container.

Step 2: Get Your API Key

In CampaignKit:

1. Sign up for a CampaignKit account
2. Navigate to Settings > API Keys
3. Create a new API key or copy an existing one
4. Keep your API key secure - you’ll need it in the next step

Step 3: Configure Credentials in n8n

In your n8n workflow:

1. Add a CampaignKit node to your workflow
2. Click on Credentials > Create New
3. Select CampaignKit API
4. Enter your API key from Step 2
5. (Optional) Modify the Base URL if using a custom CampaignKit instance
6. Click Save

The credential will be automatically tested by making a request to /v1/account/me to verify your API key is valid.

Step 4: Choose Your Operation

Select the operation you want to perform:

• Validate Email - For real-time single email validation
• Validate Batch - For processing multiple emails asynchronously
• Get Job Status - To check results of batch validation jobs

Step 5: Set Up Webhook Triggers (Optional)

To receive notifications when batch validation jobs complete:

1. Add a CampaignKit Trigger node to your workflow
2. Select Job Completed as the trigger event
3. Activate the workflow

n8n will automatically register the webhook URL with CampaignKit. You’ll receive events whenever validation jobs finish.

Example Workflows

Example 1: Validate Single Email from Webhook

Trigger: Webhook (receives form submission) Action 1: CampaignKit - Validate Email Filter: Only continue if is_valid = true Action 2: HTTP Request - Save to database Action 3: Send confirmation email

This ensures only valid emails are stored in your database and receive confirmation emails.

Example 2: Scheduled Database List Cleaning

Trigger: Schedule (runs weekly) Action 1: PostgreSQL - Fetch emails needing validation Action 2: CampaignKit - Validate Batch Action 3: Wait for completion (or use webhook trigger in separate workflow) Action 4: CampaignKit - Get Job Status Action 5: PostgreSQL - Update records with validation results

Automatically maintains email list quality by periodically revalidating stored addresses.

Example 3: Batch Validation with Webhook Notification

Workflow A - Submit Batch: Trigger: Manual or Schedule Action 1: HTTP Request - Fetch email list from API Action 2: CampaignKit - Validate Batch (returns job_id) Action 3: Store job_id for tracking

Workflow B - Process Results: Trigger: CampaignKit Trigger - Job Completed Filter: Only continue if deliverable_count > 0 Action 1: HTTP Request - Update database with results Action 2: Slack - Send notification with job statistics

Separate workflows handle submission and result processing, ideal for large batch operations.

Best Practices

Start with Single Email Validation

For real-time use cases (form submissions, API endpoints), use the Validate Email operation to get instant results and provide immediate feedback.

Use Batch Validation for Large Lists

When validating more than 10-20 emails at once, use Validate Batch instead of looping through single validations. Batch operations are optimized for performance and credit usage.

Implement Webhook Triggers for Batches

Don’t poll for batch job status repeatedly. Instead, use the CampaignKit Trigger node to receive automatic notifications when jobs complete, saving execution time and resources.

Handle Risky Emails Appropriately

Don’t automatically discard risky emails - they may be legitimate. Route them to a separate list for manual review or apply additional verification steps.

Store Validation Results

Save the complete validation response (score, status flags, classifier) to your database. This data is valuable for segmentation, analytics, and future decision-making.

Monitor Your Credit Balance

Regularly check your CampaignKit dashboard to monitor validation credit usage, especially if running automated batch validations on schedules.

Use Error Handling

Add error handling nodes to your workflows to gracefully handle API failures, network issues, or insufficient credits without breaking your automation.

Test with Small Batches First

When setting up batch validation workflows, test with small samples (10-50 emails) before processing large lists to ensure your workflow logic is correct.

Privacy & Data

CampaignKit follows strict data protection principles:

• API Authentication - Uses secure API key authentication over HTTPS (TLS 1.2+)
• Minimal Data Storage - Emails are validated in real-time and only stored temporarily for batch job processing
• GDPR Compliant - All processing follows GDPR requirements for data protection
• Webhook Security - All webhook payloads are signed with HMAC-SHA256 for verification
• Self-Hosted Benefits - With self-hosted n8n, your workflow logic and email data never leaves your infrastructure until validation requests are made
• No Third-Party Sharing - Email validation data is never shared with third parties

Troubleshooting

Credential Test Fails

Problem: “Invalid API key” or credential verification fails

Solutions:

• Verify your API key is copied correctly from CampaignKit settings (keys are case-sensitive)
• Check that your CampaignKit account is active and in good standing
• Ensure the Base URL is correct (default: https://api.campaignkit.cc)
• Try regenerating your API key in the CampaignKit dashboard

Webhook Not Receiving Events

Problem: CampaignKit Trigger node doesn’t fire when jobs complete

Solutions:

• Ensure your n8n instance is accessible from the internet (webhooks need public access)
• Verify the workflow containing the trigger is activated (not just saved)
• Check n8n execution logs for incoming webhook requests
• Confirm the webhook was successfully registered in your CampaignKit dashboard
• For self-hosted n8n behind firewalls, ensure port forwarding is configured correctly

Batch Job Stuck in “Pending”

Problem: Get Job Status shows job is still pending after a long time

Solutions:

• Large batches may take time to process (approximately 100-500 emails per minute)
• Use the Get Job Status operation to check the progress field for completion percentage
• Wait at least 5-10 minutes for large batches before troubleshooting
• Check the CampaignKit dashboard to verify the job is processing normally

”Insufficient Credits” Error

Problem: Validation operations fail with “Not enough credits” message

Solutions:

• Check your account credit balance in the CampaignKit dashboard
• Purchase additional validation credits in the Plans section
• Contact support@campaignkit.cc for billing assistance
• Set up low-balance alerts to prevent workflows from failing

Rate Limiting Errors

Problem: “Rate limit exceeded” or 429 status code responses

Solutions:

• Implement delays between sequential single email validations using Wait nodes
• Use Validate Batch instead of looping single validations for better throughput
• Rate limits are based on your account plan - check your plan details in the dashboard
• Contact support if you need higher rate limits for your use case

Need Help?

If you encounter any issues setting up the n8n integration or have questions about building specific workflows:

• CampaignKit Documentation: API Reference
• n8n Community Nodes Guide: Installation & Usage
• Support Portal: Submit a ticket
• Email Support: support@campaignkit.cc
• GitHub Repository: n8n-nodes-campaignkit (for node-specific issues)
• n8n Community Forum: community.n8n.io (for general n8n questions)