The Chorus connector is in beta. If you have any feedback or experience any issues, please contact support@withampersand.com
What’s supported
Supported actions
This connector supports:- Read Actions, including full historic backfill. Please note that incremental read is supported for
emailsandscorecardsonly. For all other objects, a full read of the Chorus instance will be done for each scheduled read. - Write Actions.
- Proxy Actions, using the base URL
https://chorus.ai/api.
Supported Objects
The Chorus connector supports reading from the following objects: The Chorus connector supports writing from the following objects:- filters
- playlists
- moments
- smart_playlists
- playlists/moments
- scorecards:export
- video_conferences
- conversations:validate
- conversations:export
- join
Example integration
For an example manifest file of a Chorus integration, visit our samples repo on Github.Using the connector
This connector uses Basic auth, which means that you do not need to set up a Provider App before getting started. (Provider apps are only required for providers that use OAuth2 Authorization Code grant type.) To start integrating with Chorus:- Create a manifest file using the example.
- Deploy it using the amp CLI.
- Embed the InstallIntegration UI component. The UI component will prompt the customer for their username, password.
- Start using the connector!
- If your integration has Read Actions, you’ll start getting webhook messages.
- If your integration has Write Actions, you can start making API calls to our Write API.
- If your integration has Proxy Actions, you can start making Proxy API calls.