Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 19 Next »

Overview

This document contains all the information you need to connect MailUp to external systems such as Web sites, ecommerce applications, CRM, ERP and CMS systems, and so on. Use of the MailUp API is free of charge, except for data synchronization via Batch FTP. The FTP space used for the integrations is never included in the MailUp service, and is usually provided by the customer.

In a nutshell, the MailUp API allows you to send a message from an external Web site or other application:

A new /wiki/spaces/mailupapi/pages/36339754 makes it easier to use existing API methods from within an application written in Ruby.

Email & SMS

You can use the SOAP API to send both e-mail and text messages (SMS)

Ready To Go integrations

Many systems can be integrated with MailUp via Web Services or by setting up an automatic file exchange. In some cases, the integration has already been performed and available as a plugin, extension or connector to another application. Among them, you will find "ready to go" integrations with:

  • /wiki/spaces/mailupUserGuide/pages/36503589: it allows to export a list of contacts with specific features from the e-commerce platform to MailUp
  • Microsoft Dynamics CRM: it allows to create a “marketing list” and send it an email message chosen among the available messages in the MailUp console, with the freedom to schedule mailings and receive delivery details directly in the CRM.
  • Wordpress: widget that allows to easily insert a subscription form to a distribution list in MailUp. Plugin can be downloaded from Wordpress site.

Several MailUp partners have developed other integrations, e.g. with VTiger or ProductCart. MailUp is always willing to provide the necessary support to develop integrations with applications that are already widely used in Italy or abroad.

Learn more about existing MailUp integrations.

Typical Workflow

In a typical workflow, the MailUp database is automatically fed with data from the external system, so that manual imports can be avoided. MailUp then returns important information such as unsubscribed users, invalid email addresses and marketing statistics.

In order to understand which solution better suits your needs, let's look at your scenario. Is the database managed inside or outside MailUp? Is the email message composed inside or outside MailUp? Here is the suggested integration method based on database location and message composition:

A section of this documentation provides additional details on the recommended MailUp API methods to execute specific tasks.

Peace of Mind

When you integrate your application with MailUp, you have the peace of mind of knowing that MailUp will always ensure that messages are never sent to:

  1. Duplicate email addresses;
  2. Recipients that unsubscribed;
  3. Recipients that reported SPAM (feedback loop management);
  4. Recipients that used the List-Unsubscribe system to unsubscribe;
  5. Recipients that reported a Hard Bounce 550 5.1.1 (invalid address, mailbox not found).

Let's Get Started

So, let's get started with the MailUp API: first, let's look at a few terms that are used throughout this documentation.

 

  • No labels