Overview
- Google Chat is used by organizations for internal communications. Google Chat data carries important conversations and documents which need to be frequently backed up.
- Using the LegacyFlo Googlechat-S3-ZIP or Googlechat-S3-PST request types, you can now backup Google Chat conversations into emails which are saved on a S3 bucket in your account
Step 1: Getting access to the Google Chat data
This is a one-time process, in which you generate the API access key and register with LegacyFlo.
Follow the steps given here.
Step 2: Register the S3 bucket with LegacyFlo
The S3 bucket has to be registered with LegacyFlo (this is a one time activity). For the steps on registration, refer to this article.
Step 3: Submitting a LegacyFlo request
You can submit requests to back up Google Chat communication data using the LegacyFlo interface.
The request type to be used is Googlechat-S3-ZIP or Googlechat-S3-PST.
The source parameters for the request are as follows:
Source Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| User ID | User id on M365 domain whose data needs to be retrieved (Note: The id should not contain the domain name.) | "john" |
| Domain | Source domain on M365 | "baya.com" |
| Operation Type | There are two options to choose from 1. Direct Message 2. Space If you choose Direct Message, all the Google Chat one on one chats for the user will be retrieved. If you choose Space, all the Google chats for the user in the Spaces will be retrieved. | Space |
| Include JSON Response | By default, all chat communications are converted to email in the HTML format and any documents shared are attached to the mail. The Include JSON Response option should be enabled if you wish to add the RAW JSON returned by the API as an additional attachment. |
Filter Information
| FIELD NAME | DESCRIPTION | SAMPLE VALUE |
|---|---|---|
| Since (DD-MMM-YYYY) | If this field is left blank, all the communications of the user till one day before the date specified in the Before field will be retrieved. If this field has a valid input, then all communications since the date specified will be retrieved. | "31-JAN-2022" |
| Before(DD-MMM-YYYY) | If this field is left blank, all the communications from the date specified in the Since field till the date prior to the date when the execution starts will be retrieved. If the field has a valid input, all communications till a day prior to the date specified will be retrieved. | "31-MAR-2022" |
Destination Information
| FIELD NAME | DESCRIPTION |
|---|---|
| S3 bucket name | The S3 bucket for the destination file. Select the S3 bucket name from the drop-down list. The list will show
|
| S3 folder path | If the file has to be created on the Vaultastic Open Store, then this parameter will have the name of your Vaultastic domain. Example: baya-com.vaultastic.com If the file is to be created on your own bucket, give the folder which will contain the file. Leave this value empty if the destination file has to be created on the root of the S3 bucket. NOTE: S3 folder path should not start or end with a "/" |
| File name | The destination filename. The file that will contain the results of the LegacyFlo command NOTE: Filenames should not start or end with a "/" |
Step 4 (optional): Submitting multiple LegacyFlo requests to backup data for multiple users
To upload multiple jobs using a CSV, create a CSV file with a list of all the users and other details required to upload data.