From Bright Pattern Documentation
< 5.19:Twitter-integration-guide | Configuration
Revision as of 04:04, 29 May 2024 by BpDeeplTranslateMaintenance (talk | contribs) (Updated via BpDeleteTranslateTags script)
• 日本語
Setting the Twitter Webhook Manually
In the unlikely case that you're unable to set the Twitter webhook in the Contact Center Administrator application, section Integration Accounts (i.e., when your Twitter credentials are accepted but you receive an authentication error when setting webhook), please try following these manual steps, and then notify our support:
- Download the twurl application; instruction are found at the following link: https://developer.twitter.com/en/docs/tutorials/using-twurl
- Set the following credentials in the .twurlrc file; note that the tokens should match those entered in the Contact Center Administrator application for your Twitter integration account:
- In Windows, the path should be in Users/<windows username>/.twurlrc
- In Linux, the path should be in ~/.twurlrc
- (Optional) Verify twurl reads the .twurlrc file correctly using the following command: twurl accounts
- Example output:
- C:\Users\Edmund>twurl accounts
- <twitter-user-name>
- SB64DimDrkcE4m85yIfz23g3C (default)
- Example output:
- Set the webhook using the commands change <env_name>, <tenant host name>, and <access token secret> to the correct values. There is no need to URL encode the URL parameter (i.e., twurl does it automatically):
- twurl -X POST "/1.1/account_activity/all/<env_name>/webhooks.json?url=https://<tenant host name>/clientweb/twitter/webhook/<access token secret>"
- Note: If you are successful, you will receive a 2xx HTTP response status code.
- twurl -X POST "/1.1/account_activity/all/<env_name>/webhooks.json?url=https://<tenant host name>/clientweb/twitter/webhook/<access token secret>"
- In the Contact Center Administrator, section Integration Accounts, click your Twitter integration's Set Webhook button again using the same credentials. This time, the "Could not authenticate you" error should be gone (i.e., if this is the same issue that was originally noted).
Example .twurlrc:
--- profiles: edmundwongbp: SB64DimDrkcE4m85yIfz23g3C: username: edmundwongbp consumer_key: SB64DimDrkcE4m85yIfz23g3C consumer_secret: ddss token: dss secret: 7xxx configuration: default_profile: - edmundwongbp
- SB64DimDrkcE4m85yIfz23g3C