Credentials Setup

Configure your Mailpulse API credentials in n8n to connect to your account.

Creating a New Credential

1. In n8n, go to Credentials in the left sidebar
2. Click Add Credential
3. Search for “Mailpulse API”
4. Click to create

Credential Fields

API URL

The base URL for API requests:

• Cloud: https://mailpulse-io.lyten.agency
• Self-hosted: Your custom domain (e.g., https://tracking.yourcompany.com)

API Key

Your organization’s API key from the Mailpulse dashboard:

1. Log in to https://mailpulse-io.lyten.agency (or your instance)
2. Go to Settings
3. Navigate to API Keys
4. Copy an existing key or create a new one

Example Configuration

API URL: NEXT_PUBLIC_BASE_URL
API Key: mp_sk_12345abcdef...

Testing the Connection

To verify your credentials are working:

1. Create a new workflow
2. Add the Mailpulse Email Tracker node
3. Select your credential
4. Try to load campaigns (if you have any)

If there’s a connection problem, n8n will show an error message.

Security Best Practices

Keep Your API Key Secure

• Never share your API key publicly
• Rotate keys periodically in the Mailpulse dashboard
• Use separate keys for development and production

Self-Hosted Instances

If you’re self-hosting Mailpulse:

• Use HTTPS for your API URL
• Consider using internal network URLs if n8n and Mailpulse are on the same network

Multiple Environments

You can create multiple credentials for different environments:

1. Development: Points to a test/staging Mailpulse instance
2. Production: Points to your production Mailpulse instance

Name them clearly (e.g., “Mailpulse - Dev”, “Mailpulse - Prod”) for easy identification.

Troubleshooting

”Unauthorized” Errors

• Verify the API key is correct
• Check if the key has been revoked in the dashboard
• Ensure there are no extra spaces in the key

Connection Timeout

• Verify the API URL is accessible from your n8n server
• Check firewall rules if self-hosted
• Ensure the Mailpulse server is running

Certificate Errors

For self-hosted instances with self-signed certificates:

# Allow self-signed certificates (not recommended for production)
NODE_TLS_REJECT_UNAUTHORIZED=0

Better solution: Use a valid SSL certificate (e.g., Let’s Encrypt).

Next Steps

With credentials configured, learn how to use the Email Tracker Node in your workflows.