Skip to main content
The Moosend integration adds contacts from ChatbotX to a mailing list directly from a Flow. The action uses the email address to create a subscriber or update an existing subscriber in the selected list. For example, after a customer submits an email address to receive product updates, ChatbotX adds it to the appropriate mailing list for future email marketing campaigns in Moosend.

Prepare your API Key

Get your API Key from Moosend before connecting the integration. This key allows ChatbotX to access your mailing lists and send subscriber data to your account.
1

Sign in to Moosend

Sign in to the Moosend account that you want to connect to ChatbotX.
2

Open Settings

From the top navigation bar, select More > Settings.
3

Select API key

From the settings menu on the left, select API key to view the key for your account.
4

Copy the API Key

Select Copy to copy the current key. To replace it, select Generate new API Key and store the new key securely.See the official Get the API key guide.
Moosend API Key Settings
The API Key provides full API access to your Moosend account. Do not share it in emails, messages, public screenshots, or customer-facing documents.

Connect Moosend to ChatbotX

1

Open Settings

In your ChatbotX workspace, select Settings from the left menu.
2

Select Integrations

Select the Integrations tab, then open Moosend.
3

Open the connection window

Select Connect to open the Connect Moosend window.
4

Enter the API Key

Paste your Moosend key into the API Key field, then select Confirm.
Connect Moosend in ChatbotX Integrations
After the key is verified, ChatbotX saves the connection and loads the mailing lists from your Moosend account for use in Flows.

Add Moosend to a Flow

Place the Moosend action after the step that collects the customer’s email address. The action requires a valid email address before it can add a subscriber to a mailing list.
1

Open the Flow

Select Flows, then open the Flow that you want to use to collect subscribers.
2

Add Actions

In the Send Message node, select + Create, then select Actions.
3

Select Email Actions

Open Email Actions and select Add Contact to Moosend.
Select Add Contact to Moosend Action
4

Open the configuration

Select Edit on the action to choose a mailing list and email field.

Configure Add Contact to Moosend

Configure both fields in the Add Contact to Moosend window, then select Save.
Configure Add Contact to Moosend
The action provides two outcomes that you can connect to the next nodes in the Flow:
  • Success: Moosend processed the request to add or update the subscriber.
  • Error: The request failed because the email address, API Key, mailing list, or connection is invalid.
Connect each outcome to a different node to send a confirmation or handle the error.

Example: Collect subscribers for product updates

A fashion retailer wants to send new collection updates to customers who subscribe through the chatbot.
1

Collect the email address

Use Get User Data to ask for the customer’s email address and save the response in the Email field.
2

Add the subscriber to Moosend

Run Add Contact to Moosend, then select the destination mailing list and the Email field.
3

Handle the result

Connect Success to a subscription confirmation message. Connect Error to a branch that asks the customer to check the email address or transfers the conversation to a support agent.

Test the integration

Before you Publish the Flow, test it with an email address that you can access.
  • Open the selected mailing list in Moosend and confirm that the subscriber appears.
  • Confirm that the Flow follows the Success branch for a valid email address.
  • Enter an invalid email address to test the Error branch.
  • If the mailing list does not appear, check the connection and reopen the action.
  • If the API Key is no longer valid, generate a new key and reconnect Moosend in ChatbotX.
The Moosend API may add a previously unsubscribed subscriber again when the action runs. Use this action only after the customer agrees to receive marketing emails. Do not use it to override an unsubscribe request.