ActionKit integration

Account admins can now connect ActionKit from Settings > Integrations to import ActionKit users as people in Daisychain, with updates synced hourly after the first import. Imported people keep their ActionKit user ID, and you can choose whether people with a mobile number and no SMS subscription history are subscribed to SMS.

Account admins can now connect ActionKit from Settings > Integrations > ActionKit using your instance's hostname and an ActionKit staff user's username and password. We check the credentials when you connect.

Connecting starts an import of every ActionKit user, and a progress page shows how far it has gotten. Once the first import finishes, changes to ActionKit users are synced hourly, and you can start a sync any time with Sync Now. The import doesn't trigger automations.

ActionKit users are matched to existing people by their ActionKit user ID, then by email or phone. Each person shows their ActionKit user ID as an identifier, and CSV imports can match people by it too. All phone numbers are imported, with a mobile number kept as the primary phone when there is one.

Because ActionKit doesn't track SMS opt-ins, an optional setting subscribes imported people to SMS on their mobile number if they have no SMS subscription history in Daisychain. Numbers on your account's SMS opt-out list are skipped. Only turn this on if your list was collected with consent to text. For developers, these subscriptions have the source kind actionkit in the API.

If ActionKit stops accepting the credentials, the integration is disabled and you can re-enable it from the integration page with a new password.