Skip to main content
The Act! integration connects Continuum to your Act! account so you can import contacts and push meeting notes and tasks back to Act! from any meeting page. Act! is set up differently from most other CRM integrations: instead of an OAuth popup, you sign in through an in‑app form where you select your region and enter your Act! username, password, and database name. For the universal connect/manage/disconnect mechanics, see the Integrations overview.

​
Before you start

Your Act! master database must be hosted in the cloud (on ActAdvantage). The integration connects to your hosted master database, not a local or remote copy.Having ActAdvantage on its own isn’t enough — some advisors have ActAdvantage but are still running their master database on their own server and haven’t moved it to the cloud. If your master database isn’t on the cloud server, the integration won’t connect. If you’re not sure, ask your Act! consultant to confirm your master database is hosted on the cloud.
Have these ready before you connect:
  • Your Act! username and password.
  • Your region — the same region you sign into the Act! web app from.
  • Your hosted (cloud) database name — see the callout in the next section, because this is the field advisors most often get wrong.
  • The account you use needs permission to read contacts and create notes and tasks in Act!.

​
Connecting Act!

1

Open Settings > Integrations and click Connect on the Act! tile

An in‑app connection form appears (no popup window).
2

Select your region

Choose the region that matches your Act! tenant. Picking the wrong region will cause sign‑in to fail — if you’re not sure which to pick, look at the URL you use to sign into Act! on the web.
3

Enter your username and password

Use the same username and password you sign into Act! with.
4

Enter your database name

Enter the name of your hosted (cloud) database — not the database name shown in your desktop Act! app.
Most common setup issue: Enter the name of your hosted (cloud) database, not the name shown in your desktop Act! app. They are often different, even though your username and password are the same for both. If your username and password are right but the connection fails, this is almost always why.Not sure what your hosted database name is? See Find your hosted database name below.
5

Connect and confirm

Click Connect. The tile updates to Connected and the Manage dialog opens with sync status. You’re done.
Continuum doesn’t store your Act! password — your sign‑in is used once to establish the connection and then discarded.

​
What gets pushed to Act!

From a meeting in Continuum, click Push to CRM to send the meeting back to Act!. The push includes:
  • The meeting summary, organized by your meeting template
  • Notes you added before and during the meeting
  • Tasks (with due dates and assignees) generated from the meeting
  • Meeting metadata — date, time, attendees

​
Where your pushed notes and tasks appear

Pushed notes and tasks show up in the Act! web version immediately. They then flow down to your desktop Act! app on the next Act! sync. The default Act! sync interval is 30 minutes (some setups are configured for 15 minutes or 1 hour), and you can trigger a sync manually in Act! to pull everything down right away.
Just pushed from Continuum but don’t see the note in your desktop Act! app yet? Check the Act! web version — it appears there first — or run a manual sync in Act! to bring it down to your desktop.

​
Importing contacts from Act!

Contacts don’t sync automatically the first time. To bring contacts in:
  1. Go to People in the left sidebar
  2. Click + New Contact > Import from CRM
  3. Pick the Act! contacts you want to bring in

​
Disconnecting

Open Manage and click Disconnect. Contacts you’ve already imported stay in Continuum.

​
Troubleshooting

The database name is almost certainly the cause. Your username and password are the same for both your desktop and your hosted databases, so the database name is the only field that differs between them — which makes it the easiest one to get wrong.Make sure you’ve entered the name of your hosted (cloud) database, not the name shown in your desktop Act! app. To find the correct name, follow Find your hosted database name below.If the database name is correct and the connection still fails, check that you selected the right region (see below) and that your master database is actually hosted on the cloud.
Your hosted database name can be different from the name shown in your desktop Act! app. Here’s how to find the one Continuum needs:
1

Log into the Act! web (cloud) version

Use the web version of Act!, not the desktop app.
2

Look at the top‑left corner

Your database is shown there as Act-[DatabaseName].
3

Take the part after the hyphen

That’s your database name. For example, Act-Entrust means your database name is Entrust.
4

Enter it in Continuum and reconnect

Enter that exact name in the Database name field in Continuum and connect again.
The region you picked doesn’t match where your Act! tenant lives. Double‑check by signing into the Act! web app and comparing the URL, then reconnect with the correct region.
The integration only connects to a master database that’s hosted in the cloud (on ActAdvantage). If your master database is still running on your own server, the integration can’t connect — even if you have ActAdvantage. Ask your Act! consultant to confirm your master database is on the cloud server.
Pushed notes and tasks appear in the Act! web version immediately, then flow down to the Act! desktop app on its next sync — so if you’re working in the desktop app, give it a moment or pull it down yourself.
  • Check the Act! web version first — your push is already there.
  • In the Act! desktop app, click Sync Now to bring it down right away, or wait for the app’s scheduled sync (the default interval is 30 minutes).
  • To see when the next automatic sync will run, look at the left sidebar of the Act! desktop app — it shows the next scheduled sync time.
Open Manage on the Act! tile and click Reconnect. Enter your new credentials to refresh the connection.