Work through the checks below in order. Each one is quick, and together they cover nearly every case.
Nothing is syncing at all:
- On the Bridges tab, check the bridge is enabled. A paused bridge is faded and shows Enable.
- Check the heartbeat at the top of the Bridges tab. Green Watching means the five minute check runs. A red Sweep overdue means it does not, see below.
- Check the source can be a source. Open its card on the Connections tab and look for Source under its name.
- For a polled source, add a new contact after the bridge was created. A bridge relays new arrivals only. Use Backfill for people already on the list.
- Click Run Sync Now, then open History on the bridge row.
The heartbeat says Sweep overdue:
WordPress runs its scheduled tasks when the site has visitors. On a quiet site, ask your host to add a server cron job that calls your site's wp-cron.php every five minutes. Diagnostics, Cron Status, then shows the next run.
A push source is not firing:
Push sources need their URL pasted into the other app. Open the app's card, click Edit Settings, copy the URL exactly, and paste it into that app's webhook or notification settings. Then trigger a real event and watch History. For Stripe, add the signing secret too so events can be checked.
A push email app is not firing:
- Brevo, Drip, Flodesk, SendX and Sendiio create their webhook when you connect. Open Edit Settings and click Save Changes to create it again.
- Loops, Sender.net, Acumbamail, Moosend, Sendy, Encharge and Ortto are set up by hand. Follow the numbered steps in the Use as a source box on the card.
- Sender.net needs a paid plan, Acumbamail any paid plan, and Sendy version 6.1 or newer for webhooks.
- For Mautic, check the webhook in Mautic points at the URL on the Mautic card, has Contact identified and Contact updated ticked, and that the secret matches.
A run shows Partial:
Open Details on the row in the Activity Log, or History on the bridge. The destination that did not accept the contact is named with its message.
- A message about connecting or reconnecting: open the app's card and click Test Connection, then Edit Settings to paste a fresh key.
- A message about a list: edit the bridge and pick the list again.
- A message about a name or a field: add a Fallback if empty in that destination's field mapping.
- A message about a temporary error or rate limit: the next contact usually goes through. Send the person again with Send live test if needed.
A run shows Failed:
- Poll error with a timeout: the source app was slow to answer. The next check tries again.
- No email in payload: a form posted without an email field. Check the field is named email.
Contacts are waiting but not arriving:
Look for a queued count on the bridge row. A delay holds contacts until their time, and a drip releases them at your pace, so a big batch takes a while by design. A paused bridge holds its queue. To send them now, click Deliver now.
Backfill or Migrate is not offered:
Both appear on bridges whose source is a built in email app. Backfill also appears for a few pack sources, such as Referly. They do not appear for No source bridges or one off events like refunds.
A list is missing in the builder:
Click Refresh Lists on the app's card, or Refresh lists in the builder, after creating a new list in the other app. Long lists get a Type to filter box.
A Google Sheet connects but no rows move:
Share the sheet with the service account email shown on the Google Sheets Connect card, with Editor access.
WooCommerce, EDD or Forms is not offered:
Those are detected on the same site, so the plugin must be active there. Activate it and reload the Connections tab.
Chat destinations are quiet:
Slack needs an incoming webhook URL, Discord a channel webhook URL, and Telegram a bot token plus the chat ID. Click Test Connection on the card.
Still stuck:
Open Diagnostics, click Copy Report for Support, and paste it into your ticket. It holds everything support needs, with keys and passwords removed.
A contact arrived twice:
Two bridges may both send to the same list. Check the Bridges tab for bridges with the same destination. Email apps ignore people they already have, but sheets add a row each time.
A new list or field is missing in the builder:
Click Refresh lists in the builder, or Refresh fields in the field mapping panel. Lists and fields are kept for a day for speed, and these links fetch them again now.
Contacts arrive without names:
Open the destination's field mapping and add a Fallback if empty, or set First name to Derive from email.
A destination says a contact unsubscribed earlier:
Email apps keep their own unsubscribe records and will not add somebody who left. That is the app protecting its sender reputation, and the Activity Log shows its message. If the person asks to rejoin, they can sign up again through that app's own form.
Tokens arrive as typed, such as {amount}:
The source did not send a field with that name for this contact. Open the token chips under the tags box to see the exact names the source sends, and check the spelling. A dry run always shows tokens as typed, because its sample has no real data.
The builder will not open:
It needs at least one connected source and one connected destination. Open the Connections tab and check both have a green Connected badge.
A bridge was copied but nothing happens:
A clone starts paused. Click Enable on its row.