bullhorn-email-checker
DeprecatedPricing
$35.00/month + usage
bullhorn-email-checker
DeprecatedBullhorn 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
Maintained by CommunityActor stats
0
Bookmarked
3
Total users
3
Monthly active users
10 months ago
Last modified
Categories
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.usernameCRM_PASSWORD=your.passwordCRM_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 addressexists- Boolean indicating if the email was foundcandidateId- 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:
- Set up Apify integration in Zapier
- Configure actor:
bullhorn-email-checker - Provide email + credentials as input fields
- Use output to trigger conditional workflows