Bullhorn Data Replication Automation Data Payloads

This article outlines Bullhorn Automation data payloads accessible via Bullhorn Data Replication. You can import Automation data, both internally and externally, through Bullhorn Data Replication, allowing you to customize your reporting and meet specific requirements.

Understanding Amplify Data in Data Replication

Data Replication includes four key tables. Three of these (EdsSourceSystem, EdsEntityType, and EdsEntityTypeSchemaVersion) are metadata tables that catalog available data sources, entity types, and schema versions.

These metadata tables do not contain the data itself. Instead, they describe what data exists and how it is structured. You’ll find entries for Automation in these metadata tables.

The actual data payloads are stored in the EdsData table. This is the table you’ll query when retrieving Automation data for reporting.

Example Use Cases

  • Measuring communication metrics, such as OptOuts in the last 30 days
  • Identifying new candidates in the last seven days without engagement
  • Evaluating performance across customers based on Net Promoter Score (NPS)
  • Determining at-risk candidates, such as pending starters with no calls within the last 30 days

To have this feature enabled submit a ticket to Support.

Requirements

Data Replication is not supported for Bullhorn Recruitment Cloud clients. As a result, automation data payloads aren't available.

You require the following to use Automation data payloads:

  • Bullhorn Automation Enterprise
  • Bullhorn Data Replication or Bullhorn Analytics Enterprise

Data Structure

To see an example of how payloads are structured, see Automation Data Payload Example.

To see an example of how to create views, see Automation Data View Example.

Data Payloads

Bullhorn Data Replication receives automation data in structured JSON payloads. Each payload contains one entity, and the structure varies by data type.

  • Data is delivered as a single JSON entity field per payload.

  • Each data type has its own structure.

  • Use source IDs to link records to Bullhorn entities.

  • If you're new to JSON, use this Microsoft article for an introduction.
  • Note: This is a third-party resource provided for convenience. Bullhorn does not endorse or manage its content.