Skip to content

MailChimp Member

MailChimp Member

This component allows you to manage contacts within a specific Mailchimp Audience (List). It serves as a central hub for interacting with individual subscriber records, enabling you to add new subscribers, update existing contact details, or retrieve specific information about members in your email marketing campaigns.

How it Works

When you connect this component to your workflow, it acts as an intermediary between Nappai and the Mailchimp API. The system takes the details you provide—such as the email address, name, and subscription status—and sends a secure request to Mailchimp.

Mailchimp then processes this request to either create a new subscriber record or update an existing one. This ensures your audience lists are accurate and up-to-date. The component handles the complex communication with Mailchimp’s servers, allowing you to focus on the data rather than the technical connections.

Connection & Credentials

This component requires configuring a credential in the Nappai panel before interacting with the external service:

  1. Go to the Credentials section in your Nappai panel.
  2. Create a new credential of the type Mailchimp API and fill in the required fields (API Keys, tokens, etc.). You can find your API key in the Mailchimp API Keys page.
  3. In your workflow, select the saved credential in the Credential input field of this node.

Operations

This component offers several operations that you can select based on what you need to do. You can only use one operation at a time:

  • get: Retrieves information about a specific member using their email address, or retrieves all members in a list if no email is specified.
  • add: Creates a new subscriber in the specified audience list.
  • update: Updates the details of an existing subscriber in the audience list.
  • delete: Removes a subscriber from the specified audience list.

To use the component, first select the operation you need in the “Operation” field.

CRITICAL INSTRUCTION FOR THE MODEL: Operation names in the list above MUST be copied EXACTLY as they appear in “Additional Component Information” (in English). Do NOT modify them. Do NOT include this warning in the final documentation.

Inputs

Input Fields

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

  • Operation: Select the action you want to perform on the Mailchimp member (e.g., get, add, update, delete).

    • Visible in: All operations
  • List ID: The ID of the list to get that contain the members tha you want to get. This identifies the specific audience list you are working with.

    • Visible in: All operations
  • Email: The email of the member to get. In get operation, if this field is empty, all members will be returned.

    • Visible in: get, update, delete
  • Tag Action: The action to perform with the tag. This allows you to add, update, or remove tags associated with the member.

    • Visible in: update
  • Status: The status of the member. Options typically include subscribed, unsubscribed, or cleaned.

    • Visible in: add, update
  • Max Results: The maximum number of results to return. Useful when retrieving a list of members to limit the amount of data returned.

    • Visible in: get
  • Include Fields: Include the fields that are contained in the list. A toggle to ensure specific data fields are returned in the output.

    • Visible in: get
  • Fields: The fields to include that contain the members tha you want to get. Select specific data points you wish to retrieve.

    • Visible in: get
  • First Name: The first name of the member. Used to populate the subscriber’s personal information.

    • Visible in: add, update
  • Last Name: The last name of the member. Used to populate the subscriber’s personal information.

    • Visible in: add, update
  • Address: The address of the member. Used for physical location data if required by your list.

    • Visible in: add, update
  • City: The city of the member. Used for physical location data if required by your list.

    • Visible in: add, update
  • State: The state of the member. Used for physical location data if required by your list.

    • Visible in: add, update
  • Zip: The zip of the member. Used for physical location data if required by your list.

    • Visible in: add, update
  • Country: The country of the member. Used for physical location data if required by your list.

    • Visible in: add, update
  • Phone: The phone of the member. Used for contact information if required by your list.

    • Visible in: add, update
  • Birthday: The birthday of the member. in MM/DD format. Useful for sending birthday-specific marketing emails.

    • Visible in: add, update
  • Company: The company of the member. Useful for B2B audience segmentation.

    • Visible in: add, update
  • Include Location: Include the location that are contained in the list. A toggle to return location data in the output.

    • Visible in: get
  • Latitude: The latitude of the member. Geo-location data for the subscriber.

    • Visible in: add, update
  • Longitude: The longitude of the member. Geo-location data for the subscriber.

    • Visible in: add, update
  • Include Additional Fields: Include the additional fields about the member. A toggle to return custom data fields in the output.

    • Visible in: get
  • Additional Fields: The additional fields about the member. Select custom fields defined in your Mailchimp account.

    • Visible in: add, update
  • Language: The language of the member. Helps customize communication preferences.

    • Visible in: add, update
  • Tags: The tags of the member. Used to categorize and segment your audience.

    • Visible in: add, update
  • Email Type: The email type of the member. Options typically include html or text.

    • Visible in: add, update
  • VIP Status: The VIP status of the member. Marks the member as a VIP for special handling or reporting.

    • Visible in: add, update
  • Include Groups: Include the groups that are contained in the list. A toggle to return group membership data in the output.

    • Visible in: get
  • Group ID: The ID of the group to get that contain the members tha you want to get. Identifies the specific audience group.

    • Visible in: update
  • Group Options: The name of the group to get that contain the members tha you want to get. Identifies the specific audience group by name.

    • Visible in: update

Outputs

Output Data Example (JSON)

The component returns detailed information about the member operation performed. This data can be mapped to other components for further processing. json { “id”: “abc123def456”, “email_address”: “user@example.com”, “unique_email_id”: “abc123def456ghi789”, “status”: “subscribed”, “email_type”: “html”, “vip”: false, “tags”: [ { “id”: 123456, “name”: “VIP Client” } ], “merge_fields”: { “FNAME”: “John”, “LNAME”: “Doe”, “ADDRESS”: “123 Main St”, “BIRTHDAY”: “01/15” }, “stats”: { “avg_open_rate”: 0, “avg_click_rate”: 0, “opened_count”: 0, “clicked_count”: 0, “unsubscribed_count”: 0, “unsubscribed_change_count”: 0, “cleaned_count”: 0, “cleaned_change_count”: 0, “member_rating”: 2, “like_count”: 0, “liked_articles_count”: 0, “email_count”: 0, “last_activity_date”: “2023-10-25T10:00:00+00:00” }, “ip_opt”: “192.168.0.1”, “ip_signup”: “192.168.0.1”, “time_opt_in”: “2023-10-25T10:00:00+00:00”, “time_signup”: “2023-10-25T10:00:00+00:00”, “last_changed”: “2023-10-25T10:00:00+00:00”, “language”: “en”, “is_gdpr”: false, “gdr_optout_date_time”: null, “consents_to_one_to_one_messaging”: true }

Connectivity

This component typically connects to the beginning of a marketing workflow.

  • Incoming Connections: It often receives data from other components such as “Get Leads,” “Form Submission,” or “Database Query” nodes, which provide the raw member data (Email, Name, etc.).
  • Outgoing Connections: The output is usually connected to:
    • Send Email components: To verify subscriber details before sending campaigns.
    • Logic/Filter components: To check status (e.g., is subscribed?) before proceeding.
    • Reporting/Dashboard components: To display member statistics and engagement metrics.

Usage Example

Scenario: Adding a New Subscriber to Your Newsletter

  1. Input Data: Connect a “Form Submission” component to provide the user’s email and name.
  2. Configure MailChimp Member:
    • Set Operation to add.
    • Select your Credential.
    • Enter your List ID.
    • Map the Email field to the email from the form.
    • Map First Name and Last Name to the respective fields from the form.
    • Set Status to subscribed.
  3. Result: The component creates a new member in Mailchimp. You can then trigger a “Welcome Email” campaign or log the success in your CRM.

Important Notes

📋 Requirement: Credential Setup You must configure a Mailchimp API credential in the Nappai panel before using this component. Without a valid API key, the component cannot communicate with Mailchimp.

ℹ️ Behavior: List ID Importance The List ID is critical. If you do not have the correct List ID, the operation will fail. Ensure you are copying the ID from the specific Mailchimp Audience list you intend to modify.

Tips and Best Practices

  • Use Specific Email for Updates: When using the update operation, always provide a specific Email to avoid updating the wrong person or causing ambiguity.
  • Check Status: For the get operation, if you want to retrieve a single user, ensure the Email field is populated. If left empty, it may return a list of all members, which can be heavy on performance.
  • Validate List ID: Verify your List ID in Mailchimp before configuring the workflow to prevent connection errors.

Security Considerations

  • API Key Safety: The Mailchimp API credential stores sensitive API keys. Ensure your Nappai access controls are secure to prevent unauthorized access to your marketing data.
  • Data Privacy: When adding or updating member data, ensure you comply with GDPR or local privacy laws. Use the Status field carefully to manage consent levels (e.g., subscribed vs unsubscribed).