Skip to main content

User Data Feed - Setup Guide

Need to know how to setup data feed? Find out here.

Updated yesterday

Step-by-step instructions to set up a user data feed

Customer Pre-work

  1. Read through our Data Feed FAQs and determine with your Go1 Customer Success Manager if a user data feed is the right solution. SCIM is an alternative technical solution for user management depending on your requirements - which can replace or work in parallel to existing SSO connections.

  2. Meet with your Implementation Project Manager and confirm report fields.

  3. Prepare report in HR system

    1. Download a user report from your HR system.

    2. Downloading a user data template from your Go1 Platform

      1. Login to Go1 as an Admin and navigate to your People page. Select a user and "Export Users" to receive an email with a CSV download link.

      2. From the email, a .csv file will download to your computer by clicking the “Download user export”.

    3. Open the file in a spreadsheet application such as Microsoft Excel, and input test data from your HR report.

      1. The records can be dummy data, but the layout of the file needs to be accurate. It also needs to be in an excel CSV UTF-8 file format.

      2. If the column headers do not match your HR report, inform your Go1 point of contact to rectify this. These must match, and Email, First Name and Last Name are required fields.

  4. Prepare delivery tool (command line or similar)

Data feed setup

  1. Log into your portal as an administrator and navigate to Integrations > User data feed.

  2. Upload a CSV with the fields you will be sending Go1 in preparation for data mapping (only column headers are necessary; any data in CSV will not be processed). See FAQs page here for more.

    1. It is recommended that your very first data feed file uploaded to the service is a snapshot of your portal at present (including inactive users who may become active again in the future).

  3. Data Mapping - map the Go1 fields to the fields in the CSV file you have uploaded. Once you complete the mapping click done.

  4. You are prompted to authorise the Go1 data feed with your log in details to approve. If you do not know your password, your Go1 point of contact can generate and provide one.

  5. Your AWS credentials will now appear on the screen. Copy your S3 bucket path and key pair from the portal to save somewhere safe to use or pass to your IT team. You will not be able to access the Secret Key once you navigate away from this page

  6. Your new data feed service is all set up! You are ready to send us your data feed files from your HRIS by following the steps below.

Send my data feed file to Go1

Sending data from my HRIS

You can send data from several popular HRIS to the Go1 data feed. Please speak to your implementation manager if you have any queries about compatible HRIS.

When sending data from an HRIS you will need the same credentials as listed below: Access Key, Secret key and bucket path/url. Depending on the HRIS you may need to include a shortened version of the url listed below such as: s3-go1-user-datafeed-production/{{portal_id}}

Sending data via AWS CLI

Note: please replace the portal_id in 3 places below {{portal_id}} with the portal_id you’re working with.

It's recommended by the team to use AWS CLI.

2. Run aws configure to setup the connection

  • For the preferred zone, it does not matter when we use S3, but you can choose ap-southeast-2 for Sydney.

3. Write your CLI Command, using AWS documentation here. Change the below example file name and path accordingly.

  1. For example this command could be used to upload the .csv file to your folder in S3:

    1. aws s3 cp C:\Example\list.csv s3://s3-go1-user-datafeed-production/{{portal_id}}/

  2. And this command to download your list in S3 bucket to local:

    1. aws s3 cp s3://s3-go1-user-datafeed-production/{{portal_id}}/list.csv C:\Example

  3. Note: Your access key doesn't have permission to list the S3 bucket content, hence this command won’t work:

    1. aws s3 ls s3:// s3-go1-user-datafeed-production/{{portal_id}}

As soon as a file appears in your dedicated bucket, our system will import the data it contains, based on the mapping rules you have dictated. Therefore, you need to control who has access to the access and secret keys for your bucket to prevent unwanted data from being added to your Go1 Platform.

Check the data feed Upload History page after the scheduled sync to confirm the changes are as desired.

For FAQs on any of these setup steps please see the Setup FAQ help guide.

Did this answer your question?