Skip to main content

Mailchimp Destination

Nexla's bi-directional connectors allow data to flow both to and from any location, making it simple to create a FlexFlow, DB-CDC, Spark ETL, or Replication data flow that sends data to a Mailchimp location.
mailchimp_api.png

Mailchimp

Create a Mailchimp Destination​

  1. Click the + icon on the Nexset that will be sent to the Mailchimp destination, and select the Send to Destination option from the menu.

  2. Select the Mailchimp connector from the list of available destination connectors. Then, select the credential that will be used to connect to the Mailchimp organization, and click Next; or, create a new Mailchimp credential for use in this flow.

  3. In Nexla, Mailchimp destinations can be created using pre-built endpoint templates, which expedite destination setup for common Mailchimp endpoints. Each template is designed specifically for the corresponding Mailchimp endpoint, making destination configuration easy and efficient.
    • To configure this destination using a template, follow the instructions in Configure Using a Template.

    Mailchimp destinations can also be configured manually, allowing you to send data to Mailchimp endpoints not included in the pre-built templates or apply further customizations to exactly suit your needs.
    • To configure this destination manually, follow the instructions in Configure Manually.

Configure Using a Template​

Nexla provides pre-built templates that can be used to rapidly configure destinations to send data to common Mailchimp endpoints. Each template is designed specifically for the corresponding Mailchimp endpoint, making destination setup easy and efficient.

  • To configure this destination using a template, select the endpoint to which data will be sent from the Endpoint pulldown menu. Then, click on the template in the list below to expand it, and follow the instructions to configure additional endpoint settings.

    Add List Member

    This endpoint adds new members to a Mailchimp list (audience). Use this template when you need to automatically add subscribers to your email lists based on data from your Nexla flows.

    • Enter the List ID in the List ID field. This is the unique identifier for the Mailchimp list where you want to add members. You can find this ID by using the "Lists" source endpoint or in your Mailchimp account.
    • The endpoint will automatically send member data from your Nexset to add new subscribers to the specified list.
    • Each record in your Nexset will be processed as a separate member, allowing you to bulk-add multiple subscribers at once.

    List IDs are unique identifiers that can be obtained from your Mailchimp account or by using Mailchimp's API to list audiences. Ensure you have the correct List ID before configuring this endpoint. For complete information about member management, see the Mailchimp API Documentation.

    Create Campaign

    This endpoint creates new email campaigns in your Mailchimp account. Use this template when you need to automatically create campaigns based on data from your Nexla flows.

    • The endpoint will automatically send campaign data from your Nexset to create new email campaigns in your Mailchimp account.
    • Each record in your Nexset will be processed as a separate campaign, allowing you to bulk-create multiple campaigns at once.
    • Campaign data should include required fields such as campaign type, subject line, and list information.

    Ensure your campaign data includes all required fields for Mailchimp campaign creation. For complete information about campaign management, see the Mailchimp API Documentation.

Configure Manually​

Mailchimp destinations can be manually configured to send data to any valid Mailchimp API endpoint.

Using manual configuration, you can also configure Nexla to automatically send the response received from the Mailchimp API after each call to a new Nexla webhook data source.

API Method​

  1. To manually configure this destination, select the Advanced tab at the top of the configuration screen.

  2. Select the API method that will be used for calls to the Mailchimp API from the Method pulldown menu. The most common methods for Mailchimp destinations are:

    • POST: For creating new resources (most common for Mailchimp destinations)
    • PUT: For updating existing resources
    • PATCH: For partial updates to existing resources
    • DELETE: For removing resources

Data Format​

  1. Select the format in which the Nexset data will be sent to the Mailchimp API from the Content Format pulldown menu. Nexla will automatically convert the data to the selected format for each API call.

Mailchimp APIs typically expect JSON format for most operations. Choose JSON unless you have specific requirements for other formats like XML or form data.

API Endpoint URL​

  1. Enter the URL of the Mailchimp API endpoint to which you want to send the Nexset data in the URL field. For update/upsert operations, include the ID of the object to be updated at the end of the URL.

Ensure the API endpoint URL is correct and accessible with your current credentials. You can test the endpoint using the Test button after configuring the URL.

Request Headers​

  • If Nexla should include any additional request headers in API calls to this destination, enter the headers & corresponding values as comma-separated pairs in the Request Headers field (e.g., header1:value1,header2:value2).

    You do not need to include any headers already present in the credentials. Common headers like Authorization, Content-Type, and Accept are typically handled automatically by Nexla based on your credential configuration.

Exclude Attributes from the Call​

  • If any record attributes in the Nexset should be omitted when sending data to this Mailchimp destination, select the attributes from the Exclude Attributes pulldown menu.

  • Any number of attributes can be selected for exclusion, and all excluded attributes will be shown in the field. To remove an attribute from the list, click the X icon next to the attribute name.

Record Batching​

  1. If records should be sent to this destination in batched API calls, check the box next to Would you like to batch your records together? to enable record batching.

  2. Enter the maximum number of records that should be batched together in a single API call in the Batch Size field. By default, this value is set to 100.

  3. Select the algorithm that will be used to group records into batches from the Grouping Algorithm pulldown menu. The sample request shown in the panel on the right will be updated to reflect the current batching settings. Some algorithms require additional settings—click on an algorithm listed below to view instructions for configuring these settings.

Record batching is particularly useful for Mailchimp destinations when you need to process large numbers of members or campaigns efficiently. Batching can help reduce API calls and improve performance.

Response Webhook​

Nexla can automatically send the response received from the Mailchimp API after each call to a new Nexla webhook data source. This option allows you to keep track of the status of each API call and any additional information returned after each call.

  • To enable this option, check the box next to Would you like to process the API response as a Nexla Webhook source?.

Response webhooks are particularly useful for Mailchimp destinations to track member addition status, campaign creation confirmations, and any error responses from the Mailchimp API.

Sample Request Payload​

Sample request payloads containing a portion of the Nexset data that will be sent to the Mailchimp API endpoint based on the current settings are shown in the Sample Payload panel on the right. These samples can be referenced to ensure that the destination and request settings are correctly configured.

  • Click on a sample request payload to expand it and view the complete payload content.
  • Sample payloads are automatically updated with each setting change, making it easy to verify that changes achieve the desired effect.

Endpoint Testing (Manual Configuration)​

After all endpoint settings have been configured, Nexla can send a test payload to the Mailchimp API to ensure that the destination is configured correctly.

  1. To send a test payload, select the Test button at the top of the Sample Payload panel, and click on a listed sample payload to expand it.

  2. If any modifications to the sample payload are needed, make the necessary changes directly within the sample window.

  3. Click the Send Test Data button at the top of a sample payload to send the test payload to the Mailchimp API using the current settings.

Save & Activate the Destination​

  • Once all endpoint settings have been configured, click the Done button in the upper right corner of the screen to save and create the destination. To send the data to the configured Mailchimp endpoint, open the destination resource menu, and select Activate.

    The Nexset data will not be sent to the Mailchimp endpoint until the destination is activated. Destinations can be activated immediately or at a later time, providing full control over data movement.