Rippling: How to Sync Employee Data to CultureBot

Rippling: How to Sync Employee Data to CultureBot

CultureBot only needs a few key employee details to power recognition, birthdays, anniversaries, and other culture-building features. Depending on your access to advanced workflows within Rippling, you can create a scheduled report export directly from Rippling. This guide walks you through setting up an automated employee data feed that works seamlessly with CultureBot.

What Information to Include

When creating your employee report in Rippling, make sure to include the following fields:

• Employee Name
• Employee Work Email
• Employee Date of Birth (DOB)
• Employee Hire Date (Start Date)
• Manager (Manager's Work Email)
• Employee Location
• Optional: Groups (this will be a custom field)
• Employee Department

These fields ensure CultureBot can match and display information correctly across its features.

*Optional: Add a Custom Field for Group Data

If you track groups (teams, cohorts, ERGs, etc.) and currently manipulate that data manually before sending it to CultureBot, you can save that step by storing group data in a dedicated Rippling custom field instead.

1. Create the field: Go to Data > Catalog > Employee object > Add field, and create your custom field.
2. Add it to employee profiles: Go to HR > People, open any employee, click the three-dot menu, and select Manage tabs and fields to place the new field on the profile.
3. Bulk-populate values: Go to Data > Catalog > Employee > Raw data > Import CSV. Select the custom field(s) you want to update, filter to the employees you want, download the template, fill it in, and re-import.
4. Add it to your report: Open your report, use the field picker on the left, browse to the Employee object/section, and check the custom field to add it as a column.

Once group data lives in its own field, your report pulls it as a clean column — no manual splitting required before it reaches CultureBot.

Step 1 – Create a Custom Employee Report

1. Log into your Rippling dashboard.
2. Navigate to Tools > Reports.
3. Click New Report and select Start from Scratch.
4. Use the search bar to add the following fields to your report:
   • Employee Name
   • Work Email
   • Date of Birth
   • Start Date
   • Manager – Work Email
   • Department
   • Location
   • Any custom fields you've added (see above)
5. Run the report once to preview the data, then Save it with a clear name (e.g., "CultureBot Employee Export").

Step 2 – Optional: Schedule the Report

You can deliver this report to CultureBot automatically using any of the three methods below. All three rely on a scheduled trigger, which requires an advanced workflow in Rippling — basic workflows only support triggers relative to an employee's start date, so a monthly (or weekly) schedule needs the advanced option.

Go to Workflow Studio, create a New Workflow, and choose the trigger On a Set Schedule with your desired frequency. Then add one of the following actions:

Option A: Send a Report via Email

1. Add the action Send a report.
2. Select the custom report you created in Step 1.
3. Click Add recipients and enter CultureBot's inbox address (get this from your CultureBot Customer Success Manager). You can add it as an external recipient — separate multiple addresses with commas if needed.
4. Choose the report view (recommend your access level as the workflow creator, so the report reflects what you see regardless of the recipient's own permissions).
5. Select CSV as the file type.
6. Configure date/time format and time zone as needed.
7. Save and Publish the workflow.

Option B: Call CultureBot's API Endpoint

This method requires your Rippling plan to include the Platform tier that unlocks the "Call a public API or webhook" action — check with your Rippling Account Manager if you're not sure this is included on your plan.

1. Add the action Call a public API.
2. Enter the endpoint URL and authentication details provided by CultureBot's Customer Success team, or found in your Employee Directory.
3. Select the appropriate HTTP method (your CultureBot CSM will confirm which one to use).
4. Add your report data as the payload — either as key-value pairs or by editing the JSON directly.
5. Save and Publish the workflow.

Which should you choose?  Email is simpler to set up and works well for most teams. The API option is worth exploring if you already use API-based integrations elsewhere and have Platform-tier access.

Step 3 – Verify the Delivery

• On the first scheduled run, confirm the data arrived at CultureBot correctly (via SFTP, email, or the API endpoint, depending on your chosen method).
• Confirm the file/payload contains all required fields.
• If anything looks off, return to the report builder to adjust fields or formatting.

Manual Option

If you do not have any available advanced workflows in Rippling, the saved report in Step 1 will still be saved and easily accessible to you in the future. You can access and download it any time to send to support@getculturebot.com, or import directly in your Employee Directory (click Import Users > CSV).

Best Practices

• Cadence: For most teams, a monthly sync is enough to keep employee data fresh; some prefer weekly.
• Confirm Your Rippling Plan: Scheduled delivery (any method) requires an advanced workflow; the API method additionally requires Platform-tier access. Check with your Rippling Account Manager if you're unsure what your plan includes.
• Connect with support: when in doubt, our support team is always happy to assist you and verify that your report is properly delivered. Please reach out to support@getculturebot.com with any questions.