I clone master branch in my local and load Rocket.Chat and everything works good but I have problem with Livechat.
I want to START CHAT with Livechat.
First step: Enable Livechat
Next Step: Register a new account
Last Step: In Livechat Users section add the user to LIVECHAT AGENTS list.
Now by using Installation code I expect that I can chat with another user. But when I fill name and email and press START CHAT button I face an internal server error.
What is the problem? Any help will be appreciated
Related
I have followed the below steps to create a custom workflow action:
Created a Hubspot developer account and created an App with proper scope, redirect URL and etc.. in it.
I was able to create the action definitions through post man using this App id and H API key.
The definitions were also listed when I use the GET Call
https://api.hubspot.com/automation/v4/actions/121**?hapikey=5af26**-***-***-***-*********
I wanted to use this action in my workflow tool in my test account and sandbox account. So installed it using the install URL in the App section.
Chose the App, accepted permission and received the code also generated the access token with it, during the installation process. (oath process done)
The App was showing up in the "Connected Apps" section in the Integration tab.
So in order to test my App I went to worflowtool but I couldn't find the actions which I custom-defined to appear here. Can someone help me, what I'm missing here...
Is there some other way I can view the UI of the defined action definition?? Why the custom action is not serachable or not listed in the workflow?
PS: Though the name is Twilio, I'm not integrating it with Twilio, I know there is integration plugins existing already.
Thanks in advance!!
Could be a few possible things that I personally encountered:
published field in your action is set to false. By default the action is created in this way. You need to pass published: true in the creation POST request for it to be enabled on creation. Alternatively you could make a PATCH request and update it after creation.
objectTypes field in your action isn't correct. I has created my action with objectTypes: ['DEALS'] but was checking for the action in a Contact workflow.
I have an application which sends notification to its subscribers through telegram.
For someone to subscribe, he needs to add his request in my website and after that, to identify his self, he needs to start a conversation with my bot using a secret code generated by the server.
For example, whenever he completes his request he should click a button which leads him out of my website and to telegram's chat (using ), in the background, the website is making long-pool requests to the server to check whether the server received a notification from telegram with this secret code abcd and to get the chat id assosiated with the request so it could store the request with this specific chat id.
The process seems to work just fine for many users, but for minor amount of users it's not working, they are starting a conversation with my bot but not getting any feedback about a success. It seems as whenever they leave the website (or the browser) and follow the path of the link (https://t.me/mybot?start=abcd) straight to telegram app, the long-pool is being stopped.does that happen sometimes when long-polling?
New Matillion user, and my first project is to read in Google Analytics data by using a google account authorized to access GA data from several clients.
I follow the steps from this Matillion documentation: Google Query Authentication Guide
I have setup the needed client ID and client secret, and I've pasted the redirect URL into the credentials page in the Google console.
From Matillion, I enter the client ID and secret in the OAuth Configuration dialog, and I configure the proxyserver and proxyport under "advanced connection options" as specified in the Matillion documentation.
When I click the Authorization link in the OAuth it opens a new tab to the Google page where I login and allow the access. Once I do this, the redirect seems(?) to kick in and I presented with a browser page with the message "Authorisation complete Please close this tab". I am not taken back to the tab where Matillion OAuth configuration is still waiting for a response of some type.
Any ideas with this? Additional information: I setup Matillion via the Snowflake Partner Connect console and am still in the free 14-day trial for Matillion.
I was able to get the OAuth workflow to finish. Any issues from this point forward will be a battle for another day. Here are my findings:
First note that I initiated my Matillion install from the Snowflake Partner Connect, which was very straight forward. I was up and running with Matillion in less than a minute.
The Matillion version that launched was 1.50.6, which is behind the most current version 1.58.4. I had no idea this would not be the most current version, as I assume the cloud platform might provide new installs with the latest version. I can see reasons why this might not be the case.
After several hours ensuring my GCP project, client id, client key, and other settings were correct everywhere, the workflow still would not complete. I opened a support case with Matillion and it was responded to within 2 hours. That is excellent. The first recommendation was to update Matillion to the latest version as it will address an OAuth issue resembling the one I reported. I saw the new version was very recent, and didn't realize I was nowhere near having the latest version.
After the update completed, I tried repeating all of the same steps. The only difference now was that the "Authorisation complete" tab closed on its own returning me to the Matillion tab which still sat "Waiting for response from service...". The version update seemed to show promise but not a solution.
A comment Schepo above cleared the final hurdle: I removed the proxyserver and proxyport "Advanced Connection options" from the OAuth configuration, and then tried getting a new authorization link. Matillion froze up and the session was dead. I had to close the browser, open a new incognito window and repeat the steps - without the proxyserver/proxyport connection settings. This time the workflow completed!
The Matillion documentation for Google Query: https://documentation.matillion.com/docs/2339840 should be updated if the Proxy Settings are not required for all OAuth configurations. The OAuth issue I reported should also be documented somewhere as a known issue addressable by the latest version (if not already).
OAuth being one of the many ways you can set up connectivity with Snowflake; it appears you're attempting to set up External OAuth, that is Google is the authorizing server. My understanding is that there are two paths to setting up OAuth,
This link has the Azure AD setup with the two options, https://community.snowflake.com/s/article/Create-External-OAuth-Token-Using-Azure-AD-For-The-OAuth-Client-Itself
Googling to setup Google AD returns https://support.google.com/cloud/answer/6158849?hl=en
You may have to follow a similar process, follow this content here: https://docs.snowflake.com/en/user-guide/oauth-ext-custom.html
I am creating an app where Admin will login form his normally account and he/she can send and receive message to any skype user which is already connected to his/her skype.
for ex.
I will send an link to user to join me on skype. It can be through any way like whatsapp, fb or any other platform. Once user will join me I can send/receiver her/his message in my admin web portal which I have created.
Can any help me about it. I am using skype for buisness online and using ucwa but still stuck on authentication part of Azure AD.
If anyone has created this type of functionality plz let me know I want a demo or a docs which I can follow bcz Microsoft Docs sucks. It really sucks.
https://learn.microsoft.com/en-us/skype-sdk/ucwa/authenticationusingazuread
I passed all the steps for authentication but stuck on last step where I have to send resend auto discovery. Through this I will get the my app's end point and I will call the api using that end point.
HTTP/1.1 200 OK
{
"_links":{
"self":{"href":"https://webdirX.online.lync.com/Autodiscover/AutodiscoverService.svc/root/user"},
"applications":{"href":"https://webpoolXY.infra.lync.com/ucwa/oauth/v1/applications"}
}
}
I am following these steps but still unable to follow properly. If anyone has done it already please let me know.
We running a wordpress website use google oauth for third-party social login. (via WP Social Login plugin.) Former engineer is leave, and we cannot have past google account credential.
We face a problem shows:
Error 401
Error: deleted_client
The OAuth client was deleted.
but we can only see old client id and secret from website admin panel.
I wanna to know,
if we set up a new google oauth application id/secret, will it make user crash from login website?
Or, is it possible for us to restore/retrieve former application ownership and make it live again?
This happened to me when I was working on an Add-On (maybe not completely related to this question but similar). I mistakenly deleted a Client ID that I thought we weren't using.
How I solved it:
Created a new project in Google Cloud
Associated the Apps Script project (Add-on) to this new Google Cloud project
Then I re-associated the App Script project with my previous Google Cloud project
The previous step will re-compile, create and associate the Client ID to the App Script project. It will contain all settings from the Client ID manually created and associated with your project in the code.
Maybe this will give some light to anyone having a similar problem.
Here use this link:
https://support.google.com/cloud/answer/6251787?hl=en
You have to reach google and they will help you out, this is the only solution you can do.
In my case, the simplest/only path (though certainly not ideal) ended up being to create a new Firebase project and start using that.
This of course can be problematic if you have a lot of data to move and/or a nontrivial data schema - say, with nested collections. For me, it was worth the effort to get unblocked from Sign-In suddenly failing to work.
... ah, OAuth fun
=======
If you are trying to make the new Client ID work .. though it's not a total solution, but after searching for a while, found this config option in Firebase console - where you enable Google Sign In.
So if you generate a new OAuth Client ID, update the ID & secret there.
After I did this, it went from a 401 error to a 400 mis_direct , which I think was step in the right direction.