BullhornHub Phone Utils icon

BullhornHub Phone Utils

Phone number utilities: parse, format, validate, geocode, carrier, timezone

Actions10

Phone Utils → Normalize

AI-generated

Summary

Normalize phone numbers to Bullhorn's E.164 standard format using various input modes including manual entry, field mapping from input data, or Bullhorn entity presets.

Inputs

  • Authentication — Choose between User Credentials (Email & Password) or Enterprise Credentials (API Key) for BullhornHub authentication.
  • Input Mode (required) — Select how to provide phone numbers: Manual Input (enter directly), Field Mapping (from input data fields), or Bullhorn Entity (preset Bullhorn fields).
  • Phone Number(s) (required) — For Manual Input mode, enter one or more phone numbers separated by commas.
  • Source Field (required) — For Field Mapping mode, specify the field in input data that contains the phone number to normalize.
  • Output Field — For Field Mapping mode, specify the field name for normalized output; leave empty to auto-generate using source field name plus suffix.
  • Entity Type (required) — For Bullhorn Entity mode, select the Bullhorn entity type (Candidate, Client Contact, Client Corporation, Lead).
  • Phone Fields (required) — For Bullhorn Entity mode, choose one or more phone fields to normalize from the entity record.
  • Batch Mode — For Field Mapping or Bullhorn Entity input modes, choose whether to process all input items in a single API call for efficiency.
  • Error Handling (required) — Choose how to handle errors: Fail Fast to stop on first error, Continue to skip errors, or Collect Errors to include error details in output.
  • Default Country (required) — Default country code used for parsing numbers missing country codes, with common countries plus an option for a custom ISO 3166-1 alpha-2 code.
  • Country Code — When Default Country is 'Other', specify the ISO 3166-1 alpha-2 country code for number parsing.

Output shape

A list of items corresponding to each input phone number or input item, each containing normalized phone number data or error details depending on error handling settings.

Output includes normalized phone numbers in E.164 format or related metadata added to each input item under specified or auto-generated output fields. Supports batch processing for multiple input items, with up to 100 phone numbers per API request. Errors are handled according to the chosen Error Handling mode, potentially including error fields in the output.

Examples

Example 1: Manual Input mode: Normalize a list of phone numbers entered directly to E.164 format.

Set Input Mode to Manual Input, enter one or more phone numbers separated by commas, select authentication method, specify default country if needed, and enable error handling as desired.

Example 2: Field Mapping mode: Normalize phone numbers from an input data field.

Set Input Mode to Field Mapping, specify source field containing phone numbers, optionally set output field name for normalized numbers, choose batch mode if processing many items for efficiency.

Example 3: Bullhorn Entity mode: Normalize selected phone fields of entities like Candidates or Leads.

Set Input Mode to Bullhorn Entity, choose the entity type, select one or more phone fields to normalize from the entity records, and set batch mode and error handling accordingly.

Links

Discussion