A secure workflow automation extension that bridges web-based data directly into the NEXUS CRM, boosting data productivity.
Users
9
+5 in 30 days
Rating
0.0 / 5
unchanged in 30 days
Ratings
0
0 in 30 days
Store rank
#202K
#169K among extensions
Version
2.12.2
updated 14 Oct 2026
Users
monthly, 4 months
Latest, 17 Oct 2026:9 usersMove the mouse over the chart for any month
Ratings count
monthly, 4 months
Latest, 17 Oct 2026:0 ratingsMove the mouse over the chart for any month
The Chrome Web Store rounds user counts down to the leading digit, so the user line moves in steps. The ratings count is exact and is the better signal of real adoption.
About NEXUS Bridge
WHAT'S NEW
# v2.12.2 - No more "signed out" notices while you are signed in, and the daily sync runs when somebody is there
This release answers the office's report from October 10: a notice at the bottom of the NEXUS
screen saying ProConnect is signed out and needs a sign-in, on a PC where ProConnect was open and
signed in, and where the Bridge's own connection test showed everything green.
**NEXUS can open a return for you.** Every row of ProConnect's tax returns list carries the
return's own id, and the Bridge now reads it off the list (no return is opened) whenever that list
is on screen, and once an hour. A client's page in NEXUS then shows "Open 2025 return",
"Dependents" and "W-2s"; the Bridge lands on that screen inside the return, since ProConnect's own
address never says which screen is open.
**E-file status every hour.** The office asked for e-file status "quicker than once a day." While
ProConnect is open and signed in on a PC that runs the sync, the Bridge reads the tax returns list
and the e-file dashboard once an hour (never between 10 PM and 7 AM). NEXUS shows accepted,
rejected or transmitted on the client card and in a new e-file report, the preparer on the return
gets a task when it is accepted or rejected, and a rejection buzzes their phone. Nothing in
ProConnect is changed.
**Why a return was rejected.** When a return is rejected, the reject code and the IRS explanation
come across with it when ProConnect shows them. To read them the Bridge may open that return's
rejection details on the e-file dashboard and close them again; it never changes anything there.
In NEXUS the "Rejected e-file" card then arrives filled in with the code, the explanation, and a
suggested reason, which the preparer can still change.
**The sync window says what it is, and a PC can opt out.** The hidden sync window used to look like
any other ProConnect tab, so people closed it. If it is ever visible now, its title starts
"NEXUS sync - " and an amber bar across the top reads: "NEXUS Sync Window. Do Not Close; It will
close by itself. If an alert asks you to sign in to ProConnect sign in here once after every time
Proconnect logs you out". Close it mid-run anyway and the Bridge's popup says when it was closed and
when it tries again. Settings has a new switch, "This computer runs the daily sync", on by default;
turn it off on a PC that should never open the window on its own. The popup's "Sync this client"
still works there, because a person pressed it.
**ProConnect's own merge tool, with the names labeled.** When Merge & Fix in NEXUS finds a pair
that is two separate ProConnect entries, it now sends you to ProConnect's "Merge duplicate clients"
tool with the two names labeled: which one NEXUS would keep as the main record and which one to
merge into it. On that ProConnect page the Bridge hangs the same two labels after the names. It
never presses anything there; the merge stays yours.
**The "signed out of ProConnect" notice no longer shows while you are signed in.** The Bridge has
two views of ProConnect: your own tab, and the hidden window it uses to sync in the background.
Both reported whether they were signed in, once a minute each, into the same answer. After a night
in which ProConnect had signed the hidden window out, that window kept saying "signed out" while
your tab kept saying "signed in," and NEXUS showed whichever had spoken last. Your own tab is now
the one that counts. The hidden window reports only on itself, and the Bridge tells the two apart
by the window itself, not by what the page claims to be.
**Signing in to ProConnect now lifts a waiting sync by itself.** When the hidden window was signed
out during the overnight run before it had reached any client, it had no page to go back to, so it
sat on the sign-in screen for good. Signing in beside it changed nothing, the sync stayed "waiting
for a ProConnect sign-in," and NEXUS kept showing that notice until Chrome was restarted. Now, the
moment a signed-in ProConnect page is seen on the PC, the Bridge sends the hidden window back to
its page and the sync carries on within the minute. If Chrome had been restarted in between and
that overnight run was lost, it starts over at that same moment.
**An overnight sync that finds ProConnect signed out waits quietly for the morning.** Between 10 PM
and 7 AM n
# v2.12.1 - Links open the new NEXUS address, and a stuck background sync says what it needs once instead of over and over
This release answers the office's reports from October 5: the "Open in NEXUS" links opening the old
address, notification after notification piling up in the Windows sidebar, and the hidden sync
window not appearing when a client is opened.
**Every link to NEXUS now opens the practice's own address.** The "Open in NEXUS" button on
ProConnect pages, the link inside a correction notice, and the NEXUS logo in the Bridge popup all
open nexus.turneroundsolutions.com. The old address still works, so nothing breaks if you have it
bookmarked, but a link there made you sign in a second time on a second copy of the site.
**A sync waiting for a ProConnect sign-in now tells you once.** When ProConnect signs the hidden
sync window out (it does this on its own after a stretch of inactivity, so overnight is typical),
the Bridge pauses and sends one desktop notification that says what to do: sign in to ProConnect and
the sync continues on its own. It used to send a fresh one roughly every twenty seconds for as long
as it waited, because its check for "signed back in" accepted a page that had not finished loading.
A single signed-out night produced hundreds of notifications, which is why they were being ignored.
The same rule now covers every notice that only a person can clear: one per pause, and never a
repeat inside half an hour.
**A client the Bridge could not read is no longer a notification per client.** If the hidden window
cannot read the pages it is sent to, every client you open fails the same way. You now…