How to integrate LiveChat Dashboard with Google Dialogflow for agents handoff? - dialogflow-es

When user ask or select option for "agent"/"chat with an agent" on google dialogflow chatbot then it should transfer the chat to LiveChat(https://www.livechat.com/) dashboard so that agent take over from chatbot.

To pass data into LiveChat from a page without LiveChat chat window installed on it,
you can use the following method from LiveChat API:
https://developers.livechat.com/docs/messaging/agent-chat-api#create-customer
to create a customer
afterwards, start a chat as that customer:
https://developers.livechat.com/docs/messaging/customer-chat-api#start-chat
once chat is started - you can submit events using this method:
https://developers.livechat.com/docs/messaging/customer-chat-api#send-event
for all of the above you'll need to provide authorization, please see below:
https://developers.livechat.com/docs/authorization/authorizing-api-calls
for authorization you'll need an account in LiveChat Developer Console:
https://developers.livechat.com/console/
In the Console you can also find contact to LiveChat Developer Community (Discord and email)
EDIT: here's how it looks like more hands on:
First thing we need to do is acquire authentication - in this case we want to act as a customer, there are a few ways to authenticate as customer - below are instructions regarding all the methods:
https://developers.livechat.com/docs/authorization/authorizing-api-calls#case-new-customer
I'll use Agent token grant method and acquire Customer access token by sending following curl:
curl --location --request POST 'https://accounts.livechat.com/customer/token' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer dal:xxxFpzmIHk5c86Zwn3uf2YunhGk' \
--data-raw '{
"grant_type": "agent_token",
"client_id": "3xxx45a50544060cedc26c90644f7677",
"response_type": "token",
"redirect_uri": "https://my.livechatinc.com"
}
'
And here's the response received:
{
"access_token": "dal:xxx-zH-fTOKYJsUolAKzow",
"client_id": "xxx145a50544060cedc26c90644f7677",
"entity_id": "xxx1d260-e284-44c0-53d2-3e958f74488a",
"expires_in": 28800,
"token_type": "Bearer"
}
Once customer access token is acquired we'll be looking to send the "start chat" method
This request requires a parameter called "organization_id" - that's an unique identifier of your account across all LiveChat Inc. products that's static so we'll need to only get it once,
you can get it by sending following curl:
curl --location --request GET 'https://api.livechatinc.com/v3.4/configuration/action/get_organization_id?license_id=1234567'
License ID required for the above can be found inside of your LiveChat tracking code here:
https://my.livechatinc.com/settings/code
Sending the request will provide you with "organization_id" in the response:
{
"organization_id": "xxx29b0e-012c-4384-9f72-614324ec0xxx"
}
Now that we have everything - we can start the chat:
curl --location --request POST 'https://api.livechatinc.com/v3.4/customer/action/start_chat?organization_id=xxx29b0e-012c-4384-9f72-614324ec0741' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer dal:xxx-zH-fTOKYJsUolAKzow' \
--data-raw '{}'
And the response looks like this:
{
"chat_id": "R5MUSNS1I5",
"thread_id": "R5MUSNS1J5"
}
chat_id property from the above response will be useful for sending events and resuming the chat should the visitor want to chat again in the future
To send a message we'll be using the "send_event" method, curl below:
curl --location --request POST 'https://api.livechatinc.com/v3.4/customer/action/send_event?organization_id=xxx29b0e-012c-4384-9f72-614324ec0741' \
--header 'Content-Type: application/json' \
--header 'Authorization: Bearer dal:xxx-zH-fTOKYJsUolAKzow' \
--data-raw '{
"chat_id": "R5MUSNS1I5",
"event": {
"type": "message",
"text": "hello world",
"recipients": "all"
}
}'
And here's the result:
incoming chat
I hope that helps!

Related

OAuth JIRA authentication flow fails

So i've created an app on jira's developers console and recieved a Client ID and a secret.
According to jira-oauth docs Im sending a get request from the browser
https://auth.atlassian.com/authorize?
audience=api.atlassian.com&
client_id=YOUR_CLIENT_ID&
scope=REQUESTED_SCOPE_ONE%20REQUESTED_SCOPE_TWO&
redirect_uri=https://YOUR_APP_CALLBACK_URL&
state=YOUR_USER_BOUND_VALUE&
response_type=code&
prompt=consent
This fire the callback uri with a long string as query param:
https://9bd3-203-114-123-134.ap.ngrok.io/?state=%24%7BYOUR_USER_BOUND_VALUE%7D&code=
Appending it to the access_token post request
curl --request POST \
--url 'https://auth.atlassian.com/oauth/token' \
--header 'Content-Type: application/json' \
--data '{
"grant_type": "authorization_code",
"client_id": "YOUR_CLIENT_ID",
"client_secret": "YOUR_CLIENT_SECRET",
"code": "YOUR_AUTHORIZATION_CODE",
"redirect_uri": "https://YOUR_APP_CALLBACK_URL"}'
This eventually returns a 404 error with title message and description as follows:
{
"error": "invalid_client",
"error_description": "failed to retrieve client"
}
Does anyone know why this is happening? all the credentials I've entered are rechecked 10 times and most of it actually copied so little room for typos.
Thank you for the help

GitlabAPI PUT approval_rules can't update group_ids

I'm trying to update the group_ids of specific approval rule in a project using the PUT API https://gitlab.com/api/v4/projects/:proj/approval_rules/:ruleId
using this call : curl -s --request PUT --header "PRIVATE-TOKEN: xxx" --data 'name=Approval_ALL_GLs_experts' --data 'approvals_required=1' --data "group_ids[]=:groupId" "https://gitlab.com/api/v4/projects/:proj/approval_rules/xxx"
The problem is that i'm getting the following response: {"id":xxx,"name":"Approval_ALL_GLs_experts","rule_type":"regular","eligible_approvers":[],"approvals_required":1,"users":[],"groups":[],"contains_hidden_groups":false,"protected_branches":[]}
My observation is that it's not working when I'm using a token of an owner of the proj but this user is not part of the groupId.
Using a token of an owner which is part of the groupId will do the work and update it correctly.

Paypal integration issue with KillBill in a node app

I am trying to integrate paypal payment gateway in my Node app in which i'm calling KillBill api provided for Paypal gateway in itsw documentation it is described that we will recieve a url in location header.
But on hitting it in postman i'm recieving html of that page instead of its url in Headers with key "location".
How to integrate it in node app so that if i make request to its url i get back the url of page to be redirected and can do anything i want.
KillBill docs link https://github.com/killbill/killbill-paypal-express-plugin
following is the api i'm using of paypal integration provided by kill bill
curl -v \
-X POST \
-u admin:password \
-H 'X-Killbill-ApiKey: bob' \
-H 'X-Killbill-ApiSecret: lazar' \
-H 'X-Killbill-CreatedBy: admin' \
-H 'Content-Type: application/json' \
-d '{
"kb_account_id": "13d26090-b8d7-11e2-9e96-0800200c9a66",
"currency": "USD",
"options": {
"return_url": "http://www.google.com/?q=SUCCESS",
"cancel_return_url": "http://www.google.com/?q=FAILURE",
"billing_agreement": {
"description": "Your subscription"
}
}
}' \
http://127.0.0.1:8080/plugins/killbill-paypal-express/1.0/setup-checkout
I have sort it some way i just converted that response html into a circular Json array and than found the URL of that html page in some index of that array as a key value pair of an object. Don't know that if it is a perfect solution but it works fine and according to my requirements.

How to test QnA knowledge base with fiddler

I just created a qna knowledge base but i'm finding it difficult to consume the endpoint api. I have actually done this before Microsoft changed the endpoint configuration features. please find below my test credentials
POST /knowledgebases/6a523867-3606-480e-9179-bd7e06df4b4d/generateAnswer
Host: https://kb12.azurewebsites.net/qnamaker
Authorization: EndpointKey 604c416d-ef24-402d-b889-cbbb4c16a396
Content-Type: application/json
{"question":"hi"}
i used `Ocp-Apim-Subscription-Key: 604c416d-ef24-402d-b889-cbbb4c16a396 but i keep getting 502 error
.
keep getting 502 error
I do a test using fiddler and can reproduce same issue, to solve the issue, you can go Tools > Options > HTTPS to make tls1.2 allowable.
Test result:
Curl example that works for me -
replace xxxx..., yyyy...., and myazureresourcename with your own values shown on the publish page.
curl \
--header "Content-type: application/json" \
--header "Authorization: EndpointKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" \
--request POST \
--data '{"question":"what is my endpoint?"}' \
https://myazureresourcename.azurewebsites.net/qnamaker/knowledgebases/yyyyyyyy-yyyy-yyyy-yyyy-yyyyyyyyyyyy/generateAnswer

Github API Create Issues return 404 Not found

I am making a request to the below URL-
Post https://api.github.com/repos/kvimal/2048/issues
With my Token as a header for authorization.
The Curl Request
curl -i -X POST https://api.github.com/repos/kvimal/2048/issues -d "{title:'hey'}" -H "Authorization: Bearer xxxxxxxxxxxxxxxxxx" -H "Content-Type: application/json"
And GitHub sends a response 404 Not found. I have reade the Documentation and as far as i have observed i am doing it by the github standards. Can anyone Help with this issues?
As illustrated in this python script, the header should be using 'token' not Bearer'
headers = {
'Content-Type':'application/json',
'Authorization': 'token %s' % token,
}
(That script doesn't use curl, but give an idea of the header)
For curl queries, see this curl POST tutorial:
curl -H "Authorization: token OAUTH-TOKEN"
And the POST message must be complete as well (as in this python script)
issue = {'title': title,
'body': body,
'assignee': assignee,
'milestone': milestone,
'labels': labels}
# Add the issue to our repository
r = session.post(url, json=issue)
(again, not curl, but gives you an example of the body)
Go to "Edit personal access token" page, checkout the "Select scopes" session.
Make sure the token has been granted required access right.
I encountered similar case when trying to create public repo with 'Authorization: token ...' header.

Resources