Skip to content
Nappai Documentation

Mailchimp Webhook

This component serves as a bridge between your Mailchimp account and the Nappai automation system. It is designed to automatically detect when specific actions happen in your Mailchimp account—such as when someone subscribes to your list, unsubscribes, or when a campaign status changes. Instead of you having to constantly check Mailchimp for changes, this component “listens” for these events and passes the information to your workflow so you can automate follow-up tasks.

How it Works

The Mailchimp Webhook component operates in the background, waiting for data from Mailchimp. When an event occurs in your Mailchimp account, Mailchimp sends a secure message (called a “webhook”) to Nappai.

The component then performs the following steps:

  1. Security Check: It verifies that the message is genuinely from Mailchimp using your API credentials to ensure no one else is sending fake data.
  2. Processing: It takes the raw data sent by Mailchimp and formats it into a clear, structured message (often containing details like the subscriber’s email address, the type of event, and campaign details).
  3. Output: This processed message is then passed to the next step in your Nappai workflow, allowing other components to react to the event (e.g., sending a welcome email or updating a database).

Connection & Credentials

To use this component, you must connect it to your Mailchimp account using secure credentials. This ensures that only authorized events are processed.

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type specified for Mailchimp and fill in the required fields (API Keys, Data Center codes, etc.).
  3. In your workflow, select the saved credential in the API Key input field of this node.

Note: Ensure your Mailchimp API key has permissions to read subscriber and campaign data.

Inputs

The following fields are available to configure this component. Each field may be visible in different operations:

  • API Key: A secure string provided by Mailchimp that allows Nappai to authenticate and communicate with your account. You must generate this key in your Mailchimp account settings.
  • Data Center: A short code (like us1 or us2) that identifies which regional server your Mailchimp account uses. This is required to route the webhook request correctly.
  • Webhook Key: A unique identifier for the specific audience or list in Mailchimp that you want to monitor for events.

Outputs

The component produces a structured output that can be connected to other nodes in your workflow to automate actions based on Mailchimp events.

Output Data Example (JSON)json

{ “message”: { “type”: “subscribe”, “email”: “user@example.com”, “fname”: “John”, “lname”: “Doe”, “campaign_id”: “c845b85796”, “fired_at”: “2023-10-27T10:00:00”, “list_id”: “l123456789” } } Use the message output to access details like the subscriber’s email, name, or the specific campaign involved. This data can then be used by other components to trigger actions, such as sending a personalized welcome email or logging the data into a spreadsheet.

Connectivity

This component is typically used as a trigger or source node in your workflow.

  • Connect From: It receives data directly from Mailchimp’s servers. No other Nappai components connect to this component in the traditional sense; rather, it acts as the entry point for external data.
  • Connect To: The message output should typically be connected to components that need to react to the event, such as:
    • Email Senders: To send follow-up emails to new subscribers.
    • Database Nodes: To update records or add new entries when a subscription occurs.
    • Notification Tools: To alert your team when specific campaign events happen (e.g., when a campaign fails or completes).

Usage Example

Scenario: Welcome New Subscribers

  1. Set up the Mailchimp Webhook: Configure the component with your API Key and Data Center, and set it to monitor a specific audience list.
  2. Connect to an Email Node: Drag a line from the message output of the webhook to the input of an “Send Email” component.
  3. Customize the Message: In the Email component, use the subscriber’s email from the message output as the recipient and fill in a personalized subject line.
  4. Result: Whenever someone subscribes to your Mailchimp list, the webhook detects it, and Nappai automatically sends them a welcome email.

Tips and Best Practices

  • Test with Test Subscribers: Before automating real customer data, use a test email address to verify that your webhook is receiving data correctly.
  • Handle Errors Gracefully: If the webhook fails to validate (e.g., due to an incorrect API key), the system will log an error. Always check the connection settings if you do not see events appearing in your workflow.
  • Monitor Data Center Codes: Ensure your Data Center code matches your Mailchimp account region. Using the wrong code (e.g., us1 for a us2 account) will cause connection failures.

Security Considerations

  • Secure API Keys: Never share your Mailchimp API Key publicly. Store it only in the secure Credential section of Nappai.
  • Validation: The component automatically validates the source of incoming webhooks. Do not attempt to bypass this validation, as it protects your system from malicious data injections.
  • Permissions: Ensure your Mailchimp API key has the minimum necessary permissions (read/write for the specific list) to follow security best practices.