Getting HighLevel contacts into a Kixie PowerList

This is the step most teams miss when they first connect the two tools. Below: the ways numbers get into a PowerList, the workflow that loads one from HighLevel, which phone number the action sends, how to read Queued and Deferred, and how to take numbers back out.

Why tagging didn't fill the list

A PowerList is a list of phone numbers that lives in Kixie. In our builds it doesn't filter on a HighLevel tag or smart list, and we haven't found a Kixie setting that makes it. A tag is a signal for a workflow, and the workflow does the pushing.

Numbers reach a PowerList three ways: a CSV upload, a push through Kixie's API, or a HighLevel workflow action. For contacts that already live in HighLevel, the workflow action is the one that keeps loading without anyone exporting a file.

The same goes in reverse. Because the list doesn't follow your tags, taking a tag off a contact in HighLevel leaves the number sitting in Kixie. Removal is its own workflow step.

Load the list from a HighLevel workflow

Set this up once per PowerList you want HighLevel to feed.

1. Open a HighLevel workflow and look for the Add to PowerList action. If it isn't there, the Kixie integration isn't active for this HighLevel account; fix that before anything else.
2. In Kixie, go to Manage > PowerLists and copy the ID of the list you want to fill.
3. Build the trigger. We use a tag that marks one group of contacts, added on purpose, so each contact enters the list once and only when it should.
4. Add the Add to PowerList action and paste in the list ID.
5. Check the phone number. The action sends the contact's primary HighLevel phone field by default; override it only if the number to dial is kept somewhere else.
6. Map any extra contact properties you want sent with the number through the tag icon in the action.
7. Before a batch goes through, remove duplicate phone numbers, then let the workflow run.

One number, one entry

Kixie builds PowerList entries around the phone number, not the contact. A contact with two numbers can become two entries. And when two HighLevel contacts share a number, Kixie matches by phone and picks the newest contact, which may not be the one you meant.

Kixie's setup page says the CRM User ID and CRM Contact ID fields on a PowerList don't affect the integration. Sources disagree on whether those IDs link records, so don't rely on them to sort out matching. Clean the phone numbers instead.

Kixie matches on the phone number. Clean the numbers before you push them.

Queued or Deferred

After a push, open the PowerList's View Contacts page. Queued numbers are waiting their turn to be dialed. A Deferred number is being held back by one of the list's rules, such as calling hours, the attempt limit or the spacing between retries, and the page shows the reason.

A Deferred number isn't a failed push. It arrived; the list's settings are holding it until a rule allows the call.

Taking numbers back out

HighLevel has two removal actions for Kixie, and they do very different things.

• Remove from PowerList takes the number off the one list you name in the action.
• Remove from All PowerLists takes it off every PowerList in Kixie. Keep it for a contact who should never be dialed again, not for moving someone from one list to the next.