Skip to content

Instantly share code, notes, and snippets.

Show Gist options
  • Save drewbanin/efd632bb5cd37e5611c1423d5d83f4bc to your computer and use it in GitHub Desktop.
Save drewbanin/efd632bb5cd37e5611c1423d5d83f4bc to your computer and use it in GitHub Desktop.
Stitch Tap Documentation Template

[tap-liveperson]

Connecting [tap-liveperson]

Setup

To set up tap-liveperson in Stitch, you need:

  • A LivePerson Account ID: Find this ID in the URL after authenticating with LivePerson. It should be a 7-digit number.
  • LivePerson API Keys: For information on creating API Keys, consult the LivePerson docs. You will need to record your app_key, app_secret, access_token, and access_token.

tap-liveperson Replication

The following endpoints are replicated incrementally:

  • Engagement History
  • Messaging Interactions
  • Agent Activity
  • Queue Health

The following endpoints do not support incremental querying, and are refreshed completely on every sync

  • Agent Groups
  • Agent Status
  • Skills
  • Users

The incrementally-synced endpoints represent potentially large activity streams. The full-refreshed endpoints are smaller in nature, and map one-to-one with administrative resources created in the LivePerson user interface.

Queue Health

The Queue Health endpoint does not support historical querying and is real-time in nature. The Queue Health endpoint only returns data about queue health in LivePerson for the last 24 hours. In order to build a complete Queue Health dataset, this endpoint must be replicated no less than every 24 hours.


tap-liveperson Table Schemas

Table name: Engagement History

Table name: Messaging Interactions

Table name: Agent Activity

Table name: Queue Health

Table name: Agent Groups

Table name: Agent Status

Table name: Skills

Table name: Users

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment