bullhorn-email-checker avatar

bullhorn-email-checker

Deprecated

Pricing

$35.00/month + usage

Go to Apify Store
bullhorn-email-checker

bullhorn-email-checker

Deprecated

Bullhorn Email Checker stops duplicate candidates in seconds. It logs into Bullhorn, searches by email, and returns JSON with `exists` and `candidateId`. Plug it into Zapier, n8n or API flows to skip β€œCreate Candidate” when a match is foundβ€”no coding required.

Pricing

$35.00/month + usage

Rating

0.0

(0)

Developer

{t}riggernode

{t}riggernode

Maintained by Community

Actor stats

0

Bookmarked

3

Total users

3

Monthly active users

10 months ago

Last modified

Share

Bullhorn Email Checker

This Apify actor checks if an email address exists in the Bullhorn CRM candidate database. Version 2.0 introduces multi-user support with flexible credential management.

πŸš€ Features

  • βœ… Reliable Email Detection: Advanced matching algorithms with multiple fallback strategies
  • πŸ” Flexible Credentials: Supports both environment variables and input-based credentials
  • 🌐 Multi-User Ready: Perfect for Zapier integrations and shared environments
  • ⚑ High Performance: Optimized for speed and reliability
  • πŸ“Š Detailed Results: Returns email status, candidate ID, and timestamp

πŸ“ Usage

Input Parameters

Required

  • email - The email address to search for

Optional (Multi-User Mode)

  • username - Bullhorn CRM username (secure field)
  • password - Bullhorn CRM password (secure field)
  • crmUrl - Bullhorn CRM login URL

Credential Methods

Method 1: Environment Variables (Legacy)

Set these environment variables (e.g., in .env file):

CRM_USERNAME=your.username
CRM_PASSWORD=your.password
CRM_URL=https://universal.bullhornstaffing.com/universal-login/login

Method 2: Input Parameters (Multi-User)

Provide credentials directly in the actor input:

{
"email": "john.doe@example.com",
"username": "your.username",
"password": "your.password",
"crmUrl": "https://universal.bullhornstaffing.com/universal-login/login"
}

πŸ“€ Output

The actor returns a JSON object with:

  • email - The searched email address
  • exists - Boolean indicating if the email was found
  • candidateId - The candidate ID if found (null if not found)
  • matchType - How the match was found (exact, partial, text_contains, username)
  • timestamp - When the search was performed

πŸ“‹ Examples

Example Input (Environment Method)

{
"email": "john.doe@example.com"
}

Example Input (Multi-User Method)

{
"email": "john.doe@example.com",
"username": "api.user",
"password": "secure.password",
"crmUrl": "https://universal.bullhornstaffing.com/universal-login/login"
}

Example Output

{
"email": "john.doe@example.com",
"exists": true,
"candidateId": "12345",
"matchType": "exact",
"timestamp": "2025-07-15T20:30:00.000Z"
}

πŸ” Security

  • Credentials are never logged in plain text
  • Input-based credentials are marked as secure fields in Apify
  • Supports encrypted credential storage in Zapier integrations
  • Automatic credential source detection and logging

πŸ”§ Configuration

  • Memory: 4096 MB recommended
  • Timeout: 300 seconds (5 minutes)
  • Build: Use "latest" for most recent optimizations

🌐 Zapier Integration

Perfect for Zapier workflows:

  1. Set up Apify integration in Zapier
  2. Configure actor: bullhorn-email-checker
  3. Provide email + credentials as input fields
  4. Use output to trigger conditional workflows