#### Configuring Account Linking
1. Login to your [Action Developer Console](https://console.actions.google.com/) and select Rocket Chat project on the list.
2. Go to Settings ⚙ -> Project Setting and Copy **Project ID** and paste it somewere safe as we will need it later.
3. Now click on **Advance Options** on Bottom left of the screen and select **Account Linking** from the list.
4. In Account creation,
+ Select **No, I only want to allow account creation on my website**
+ Click **Next**.
5. In Linking type, Select **OAuth** from the list and Set **Authorisation code** as grant type. Click **Next**.
6. Now we need to fill up the Authorization URI, Access Token URI, Client ID, Client Secret which we will generate on our rocket chat server.
+ **Note** You need to be admin of the server to proceed with the further steps.
7. In a new tab go to your **Server** -> **Three Dot Menu** -> **Administration**.
8. Click on **OAuth Apps**.
9. Click on **New Application** on top right. Now we need to give it an **Application Name** and a **Redirect URI**.
10. For Application Name use "rcgoogleaction". This can be anything else as well.
+ For the Redirect URI, copy `https://oauth-redirect.googleusercontent.com/r/YOUR_PROJECT_ID` and paste it in the Redirect URI field. **(Paste the Project Id we copied earlier here)**
11. You'll see it automatically generating Client ID, Client Secret, Authorization URL, and Access Token URL. Now copy these from the oauth app page and paste it in the **Client ID, Client Secret, Authorization URL** and **Access Token URL** fields in the Client information on Google Action Console Page. Click **Next**.
12. Copy **Client ID** and paste it somewhere safe as we will be using it for setting up Firebase Environent Variables.
13. In Configure your client (optional) section,
+ Tick mark(✔) **Google to transmit clientID and secret via HTTP basic auth header**
+ Click **Next**.
14. In Testing instructions,
+ Provide an Email Id and Password as per instructions
+ Click on **Save**.
15. We are done on setting our OAuth App which will give us the access token to use for logging in. But for that we need to also enable custom oauth login for our server which we will do in the next steps.
16. Go to your **Server -> Three Dot Menu -> Administration**. Scroll down on your left and select **OAuth** and on top right click on **Add custom OAuth**.
17. Give a unique name in lower case for the custom oauth. For example enter "googleaction". Click on **Send**. Copy and paste this name somewhere safe as we will be using it for setting up Firebase Environent Variables.
18. You will now be provided a few fields some of which will be prefilled. We only need to change a few.
+ Change the **Enable** to **true**.
+ In the URL field enter `https://yourserverurl/api/v1`
19. Finally at the bottom switch **Merge users** to **true**. We don't need to make any other changes here.
20. Click on **Save Changes** on top.
21. Go to your console add your **Server URL,OAuth Service Name** and **Client ID** to the following command and run,
```
firebase functions:config:set envariables.server_url="https://YOUR.SERVER.chat" envariables.oauth_service_name="YOUR_CUSTOM_OAUTH_NAME" envariables.clientid="YOUR_CLIENT_ID"
````
Then run,
firebase deploy --only functions
22. Finally We Are Done !
#### AWS Lambda Deployment
The fulfillment code can also be deployed in AWS as a lambda function as an alternative to using Firebase.
1. Navigate to the AWS Lambda console.
2. Create a new function with the following settings.
+ Author From Scratch
+ Runtime: Node.js 12.x
+ Permissions: Create a new role with basic Lambda Permissions
3. Add the following Environment Variables
```
OAUTH_SERVICE_NAME => Name of the Custom OAuth service created in Rocket Chat OAuth Settings
SERVER_URL => Rocket Chat server url (https://YOUR.SERVER.chat)
```
4. Add an API Gateway trigger with the following settings.
+ Create an API
+ API Type: HTTP API
+ Security: Open
5. Copy the following value somewhere.
+ Click on API Gateway > Details > API endpoint
6. Navigate to Dialogflow > Fulfillment section: https://dialogflow.cloud.google.com/#/agent/project_id/fulfillment
+ Paste the API endpoint in the Webhook URL field.
7. To upload the backend code in Lambda function
+ Navigate to `./functions` directory in the project repository
+ Select all files and compress into a zip file.
+ In the **Functions Code** section of AWS Lambda Function
+ Actions > Upload a .zip file
+ Select the compressed zip file
+ Click **Save**.
---
## Running this Action
+ You can test your Action on any Google Assistant-enabled device on which the Assistant is signed into the same account used to create this project. Just say or type, “OK Google, talk to my test app”.
+ You can also use the Actions on Google Console simulator to test most features and preview on-device behavior.
---
## Development
#### Local Development Setup
The project can be run on local development for debugging. The steps are listed below.
1. Create an environment file inside the functions folder.
+ `./functions/.env`
2. Add the following variables
```
SERVER_URL=
and select **Your Locale** from the list.
4. You will need to add **Training phrases** one by one to every intent. Select **Intents** > select one intent from the list > **Training phrases**. Add some training phrases that include every **Parameter** required as headers data to send a `POST` request to the server, in the utterance and make sure it is native speaker friendly.
5. While creating Training Phrases, make sure that you give composite entities parameters to the utterances. E.g. If your creating an utterance with `username` and `channelname`, select `@sys.any` as their entity type. Refer to `EN` locale training phrases for more depth understanding.
6. For Backend setup, go to `./functions/index.js` and add your locale name to `i18n.configure` > `locales` array.
```
i18n.configure({
locales: ['en-US', 'en-GB', 'en-AU', 'en-CA', 'en-IN', 'pt-BR', 'hi-IN'],
directory: __dirname + '/locales',
defaultLocale: 'en-US',
objectNotation : true
});
```
**NOTE:** It is same name as in locales folder.
7. Locale File: `./functions/locales/*.json` ,It is highly likely that your locale may be behind because of new function additions, so we highly suggest to make sure that every object in your locale is up-to-date with our English locale file. If not make sure to add those JSON blocks to your locale before deployment. To do that simply copy and paste missing blocks from **English** locale file and simply translate the response strings into your own language.
We have developed those base locales using a translation software and translations of response may not be always accurate so feel free to update those response strings correctly as per your native language.
For more details on i18n please check out [Fulfillment Localization](https://developers.google.com/actions/localization/fulfillment) and [I18n-node](https://github.com/mashpie/i18n-node)
---
## References & Issues
+ Rocket Chat API [Documentation](https://rocket.chat/docs/developer-guides/rest-api/)
+ Axios [Documentation](https://github.com/axios/axios)
+ i18n [Documentation](https://developers.google.com/actions/localization/fulfillment)
+ Questions? Go to [StackOverflow](https://stackoverflow.com/questions/tagged/actions-on-google), [Assistant Developer Community on Reddit](https://www.reddit.com/r/GoogleAssistantDev/) or [Support](https://developers.google.com/actions/support/).
+ For bugs, please report an issue on Github.
+ Actions on Google [Documentation](https://developers.google.com/actions/extending-the-assistant)
+ Actions on Google [Codelabs](https://codelabs.developers.google.com/?cat=Assistant)
+ [Webhook Boilerplate Template](https://github.com/actions-on-google/dialogflow-webhook-boilerplate-nodejs) for Actions on Google
---
## Our Alexa Skill
Are you an Alexa Developer, We also have an [Alexa Repository](https://github.com/RocketChat/alexa-rocketchat) for you to contribute on. Any form of help is appreciated.