Before you begin
1. User fields and first steps on Go1
In Go1, turn off portal notifications before setting up the data feed if you do not want setup/testing emails sent to users.
In Go1, start the User Data Feed setup under the Integrations section.
Use the sample CSV provided to progress through the mapping step and retrieve the secret key, access key, and bucket URL.
Note: Secret keys are only visible once for security reasons. Keep the AWS secret access key somewhere secure. You will need it along with the access key and bucket URL when creating the S3 destination in HiBob.
2. Create the Amazon S3 Destination in HiBob
In HiBob, choose Marketplace from the menu.
In Marketplace, select Storage and open Amazon S3.
Marketplace > Storage shows Amazon S3 as the storage option for scheduled
report delivery
Select Connect on the Amazon S3 app page.
Amazon S3 overview page with the Manage button
On S3 destinations, select New S3 destination.
S3 destinations page. Existing destination details are hidden in this reference image
Complete the destination fields using the values retrieved from your Go1 Data Feed setup , then select Save.
HiBob field | What to enter |
Name | Use a clear label, for example, Go1 Data Feed. |
Bucket | Paste in only the bucket sub-domain from the Go1 portal data feed section: s3-go1-user-datafeed-production |
Folder | Paste the folder ID from the bucket URL in the Go1 portal data feed section. This is the 8-digit number at the end of the URL – do not include any trailing slashes. |
AWS access key ID | Paste the access key ID from the Go1 portal data feed section. |
AWS secret access key | Paste the secret access key from the Go1 portal data feed section that was stored securely. |
New S3 destination form. All required fields come from the Go1 data feed setup.
3. Prepare the Bob Report
Create or open the Bob report that will be sent to Go1. Use a clear report name, for example “Go1 Data Feed”. The report should include the user fields Go1 needs for provisioning or user updates.
Go1 requires specific column headers. Edit the Bob report columns with the settings cog to rename them accordingly. By default, the column names are:
First Name (required field)
Last Name (required field)
Email (required field)
Optional standard fields:
Managers (for Manager email)
Locale (for Intelligent Translations, if not already set up through SSO)
Job Title (for Knowledge Checks, if not already set up through SSO)
Industry (for Knowledge Checks, if not already set up through SSO)
Department
Division
Job Level
Start Date (YYYY-MM-DD)
External User ID
City
State
Phone
Country
Gender
Note:
If sending any date fields, select the Date drop-down on the column settings to YYYY-MM-DD.
Save the report and export a version for the final steps on Go1 before creating the schedule.
Saved Go1 Data Feed report with the current HiBob schedule banner.
4. Schedule the Report to S3
6. From the report, open More and choose Schedule.
Use More > Schedule to create a scheduled report from the saved report.
7. Enter a schedule name and confirm the report to be sent.
8. Set File format to csv.
9. In the S3 field, select the S3 destination you created for Go1.
10. Leave email notification off unless you want an email every time HiBob sends the report to S3.
11. Choose the frequency, delivery time, and timezone, then save the schedule.
Schedule settings showing the S3 destination selector and notification toggle.
After saving, the report page will show the planned schedule. You can open it from the View dropdown to confirm the target destination, frequency, time, timezone, and file format.
5. Finish Setup in Go1
Return to Go1 and continue the data feed setup flow. Upload the Bob user report as instructed, then map the Bob fields to the matching Go1 user fields.
If you’d like to use the user's employee ID/UPN as the unique identifier on Go1, an additional configuration step is required by your Go1 point of contact.
If you have existing users on Go1, ensure they have this ID mapped via a bulk CSV upload prior to the data feed sync to avoid duplication of user records.
Fields are case sensitive so ensure everything is mirrored exactly across both your Bob custom report and the fields selected on the Go1 Data Feed mapping table.
Ensure notifications are off and run a test delivery. Confirm through the Go1 Data Feed history page that the sync completed without errors.
Future changes
If additional fields are required in the future, the custom report in Bob can be edited to add the columns. Export the new report to re-upload the new csv on Go1 and then update the mappings. If the field is non-standard, ensure the custom field has been created beforehand by your Go1 point of contact.