Some platforms are genuinely run more than once by the same person. An agency might run one MailWizz install per client, or a publisher might run separate Sendy installs for each brand. WP Sync lets one card hold several of them.
Which apps support it:
- MailWizz and Sendy: extra installs on the same card.
- AWeber: a Multiple AWeber accounts section on its card, marked beta.
How it works:

The first set of details you enter is the main account and keeps working exactly as before. Under it, a Running more than one section offers Add another install blocks, each with a name, an address and keys. Every list from every install then appears in the bridge builder, so one bridge can write to as many of them as you like.
Adding an install step by step:
- Open the MailWizz or Sendy card and click Edit Settings.
- In an empty Add another install block, type a name, such as Client A.
- Enter that install's API address and keys.
- Click Save Changes.
- Click Edit Settings again for more blank blocks.
How many:
Two blank blocks are offered at a time, and a card holds up to 20 extra installs.
Removing an install:
Clear its API address and save.
Why it is safe to turn on:
Lists on the main account keep exactly the same IDs, so every bridge you already saved keeps running without changes. Nothing needs re-saving when you add a second install.
Naming matters:
The name you give an install is what you will see when picking a list in the builder. Client or brand names read better than server addresses.
AWeber is a related case:
AWeber's two cards are two ways to connect, not two accounts. Use AWeber (Developer OAuth) when you want AWeber as a source or want tag and field actions. To use more than one AWeber login, open the Multiple AWeber accounts (beta) section on the card, add the other account with its own authorisation, and route different bridges to it. Actions such as tags run on your main AWeber account.
For other apps:
Apps without this feature hold one account per card. To feed two accounts of such an app, a Webhook Connect outbound target can pass contacts to a tool that serves the second account.
A real example:
An agency running WP Sync on its own site has a MailWizz install for each of two clients, named Client A and Client B. One bridge sends Client A's webinar sign ups to Client A's list, another sends Client B's to Client B's, both from the same MailWizz card.
Checking an extra install:
After saving, click Refresh Lists on the card. Lists from each install appear with the install's name, so you can see at a glance which client each one belongs to.
Planning lists across installs:
- Name each install after the client or brand.
- In each install, keep list names clear, such as Newsletter and Customers.
- In the builder, the list picker shows the install name with each list, so Client A Newsletter and Client B Newsletter are easy to tell apart.
Bridges per client:
Give each client its own bridges, named with the client, such as Client A webinar sign ups to MailWizz. On the Bridges tab, typing Client A in the search box then shows everything for that client in one view.
Tips:
- Run Test Connection after adding an install.
- Keep names short, since they appear in every list picker.