Documentation

Reading time: 15 min
Last updated: March 15, 2024

PihuPulse ATS Integration Guide

This guide provides comprehensive instructions for integrating PihuPulse with your Applicant Tracking System (ATS). Learn how to set up bidirectional data flow, automate candidate screening, and streamline your recruitment workflow.

Overview of ATS Integration

Integrating PihuPulse with your Applicant Tracking System creates a seamless recruitment workflow that eliminates manual data entry, reduces administrative tasks, and ensures consistent candidate information across all your platforms.

PihuPulse ATS Integration Workflow

PihuPulse ATS Integration Workflow

Key Benefits

Bidirectional Data Sync

Candidate information flows seamlessly between PihuPulse and your ATS, ensuring all systems have the most up-to-date data.

Centralized Candidate Profiles

View complete candidate profiles, including screening results, directly within your ATS interface.

Automated Workflows

Trigger automated actions in your ATS based on PihuPulse screening results, such as advancing qualified candidates or scheduling interviews.

Consolidated Reporting

Generate comprehensive reports that combine data from both PihuPulse and your ATS for deeper insights into your recruitment process.

Integration Approach

PihuPulse offers both native integrations with popular ATS platforms and a flexible API for custom integrations. This guide covers both approaches, allowing you to choose the best option for your specific needs.

Supported ATS Platforms

PihuPulse offers native integrations with the following Applicant Tracking Systems. Each integration is designed to provide seamless data flow and functionality while respecting the unique features of each platform.

GH

Greenhouse

Full bidirectional integration with customizable field mapping and automated stage progression.

View setup guide
WD

Workday

Enterprise-grade integration with Workday Recruiting, including custom security controls and advanced reporting.

View setup guide
LV

Lever

Seamless integration with Lever's candidate pipeline, including custom feedback forms and stage automation.

View setup guide
SF

Salesforce

Integration with Salesforce Talent Management, including custom objects and Lightning components.

View setup guide
BH

BambooHR

Complete integration with BambooHR's applicant tracking features, including custom hiring workflows.

View setup guide
WB

Workable

Comprehensive integration with Workable, including automated candidate sourcing and evaluation.

View setup guide

Custom ATS Integration

If your ATS is not listed above, PihuPulse offers several options for custom integration:

API Integration

Use our comprehensive REST API to build a custom integration between PihuPulse and your ATS. Our API documentation provides detailed endpoints and examples to facilitate development.

View API Documentation

Webhook Integration

Configure webhooks to send real-time notifications from PihuPulse to your ATS when specific events occur, such as when a candidate completes a screening or receives a particular score.

Configure Webhooks

Custom Integration Services

Our professional services team can build a custom integration tailored to your specific ATS and workflow requirements. Contact us to discuss your needs and get a quote.

Integration Setup Process

Setting up an ATS integration with PihuPulse involves several key steps. While the specific details may vary depending on your ATS, the general process remains consistent.

PihuPulse ATS Integration Setup

PihuPulse ATS Integration Setup Interface

  1. 1Generate API Credentials

    In your ATS, create API credentials that PihuPulse will use to access your data. This typically involves:

    • Generating an API key or OAuth credentials
    • Setting appropriate permission scopes
    • Configuring webhook endpoints (if applicable)

    Refer to your specific ATS documentation for detailed instructions on generating API credentials.

  2. 2Configure Integration in PihuPulse

    In PihuPulse, navigate to Settings > Integrations > ATS Integration and follow these steps:

    • Select your ATS from the dropdown menu
    • Enter the API credentials generated in step 1
    • Specify your ATS instance URL (if applicable)
    • Test the connection to ensure proper authentication
  3. 3Map Data Fields

    Configure how data fields in PihuPulse correspond to fields in your ATS:

    • Map standard fields like name, email, and phone number
    • Configure custom field mappings specific to your organization
    • Set up screening result field mappings

    Field mapping ensures that data flows correctly between systems and appears in the expected locations.

  4. 4Configure Workflow Automation

    Set up automated workflows that trigger actions based on screening results:

    • Define candidate stage progression rules
    • Configure automatic tagging based on screening results
    • Set up notification rules for hiring managers

    Workflow automation reduces manual tasks and ensures consistent candidate processing.

  5. 5Test the Integration

    Thoroughly test the integration to ensure data flows correctly in both directions:

    • Create a test candidate in your ATS and verify it appears in PihuPulse
    • Run a test screening and confirm the results appear in your ATS
    • Test workflow automations to ensure they trigger as expected
  6. 6Deploy to Production

    Once testing is complete, deploy the integration to your production environment:

    • Update API credentials if different from testing environment
    • Verify production connectivity
    • Train your team on the integrated workflow

Implementation Support

Our integration specialists are available to assist with your ATS integration. For complex setups or custom requirements, schedule a consultation with our team to ensure a smooth implementation.

Data Field Mapping

Proper data field mapping is crucial for a successful ATS integration. This section explains how to map fields between PihuPulse and your ATS to ensure accurate data synchronization.

PihuPulse Data Field Mapping Interface

PihuPulse Data Field Mapping Interface

Standard Fields

PihuPulse automatically maps these standard fields to their equivalents in most ATS platforms:

PihuPulse FieldCommon ATS FieldDescription
First Namefirst_name, firstNameCandidate's first name
Last Namelast_name, lastNameCandidate's last name
Emailemail, email_addressPrimary contact email
Phonephone, phone_numberContact phone number
Positionjob_title, positionApplied position or job title

Screening Result Fields

Configure how screening results from PihuPulse are mapped to your ATS:

Overall Score

Map the candidate's overall screening score to a field in your ATS. This is typically mapped to a custom field or a scoring field.

Example mapping: PihuPulse "Overall Score" → ATS "candidate_score" or "assessment_result"

Category Scores

Map individual category scores (e.g., Technical Skills, Communication) to separate fields in your ATS for detailed reporting.

Example mapping: PihuPulse "Technical Score" → ATS "technical_assessment" or "tech_skills_rating"

Screening Summary

Map the AI-generated screening summary to a notes or comments field in your ATS to provide recruiters with a quick overview.

Example mapping: PihuPulse "AI Summary" → ATS "candidate_notes" or "assessment_summary"

Recommendation

Map the PihuPulse recommendation (Advance, Consider, Decline) to a status or recommendation field in your ATS.

Example mapping: PihuPulse "Recommendation" → ATS "screening_result" or "candidate_status"

Custom Field Mapping

For organization-specific data, you can create custom field mappings:

  1. 1. Identify Custom Fields

    Identify the custom fields in your ATS that you want to sync with PihuPulse. These might include fields like "Source," "Salary Expectations," or industry-specific qualifications.

  2. 2. Create Matching Fields

    In PihuPulse, create corresponding custom fields under Settings > Custom Fields to match your ATS fields.

  3. 3. Configure Field Mapping

    In the integration settings, map your custom PihuPulse fields to the corresponding ATS fields. Ensure that field types match (e.g., text to text, number to number).

  4. 4. Test Custom Field Sync

    Create a test candidate with custom field data and verify that the information syncs correctly between systems.

Field Mapping Best Practices

When mapping fields, consider these best practices:

  • • Ensure field types match to prevent data conversion issues
  • • Map only the fields you need to avoid cluttering your ATS
  • • Use descriptive field names for clarity
  • • Document your field mappings for future reference

Workflow Automation

PihuPulse's ATS integration enables powerful workflow automations that can streamline your recruitment process. These automations trigger actions in your ATS based on screening results and other criteria.

PihuPulse Workflow Automation Interface

PihuPulse Workflow Automation Interface

Common Workflow Automations

Stage Progression

Automatically move candidates to the next stage in your ATS based on their screening scores.

Example: Move candidates with scores above 85% from "Screening" to "Interview" stage

Candidate Tagging

Apply tags to candidates in your ATS based on skills or qualifications detected during screening.

Example: Add "JavaScript Expert" tag when candidate scores highly on JavaScript questions

Interview Scheduling

Trigger interview scheduling workflows for qualified candidates.

Example: Send interview scheduling email to candidates who pass screening

Rejection Automation

Automatically send rejection notifications to candidates who don't meet minimum requirements.

Example: Send rejection email to candidates with scores below 40%

Setting Up Workflow Automations

  1. 1Access Automation Settings

    Navigate to Settings > Integrations > ATS Integration > Workflow Automation to access the automation configuration interface.

  2. 2Create a New Automation

    Click "Create Automation" and provide a name and description for your automation rule.

  3. 3Define Trigger Conditions

    Specify the conditions that will trigger the automation:

    • Score thresholds (e.g., Overall Score > 80%)
    • Specific answers to key questions
    • AI recommendation (Advance, Consider, Decline)
    • Screening completion status
  4. 4Configure Actions

    Define the actions that will occur when the trigger conditions are met:

    • Update candidate stage in ATS
    • Add tags or labels to the candidate
    • Send notifications to hiring managers
    • Trigger email templates in your ATS
  5. 5Set Scope and Limitations

    Define when and where the automation should apply:

    • Specific job requisitions or departments
    • Time-based limitations (e.g., only during business hours)
    • Volume limitations (e.g., maximum number of automated actions per day)
  6. 6Test and Activate

    Run a test with sample data to ensure the automation works as expected, then activate it for your live recruitment process.

Automation Best Practices

Start with simple automations and gradually add complexity as you become comfortable with the system. Always maintain human oversight for critical decisions, and regularly review automation performance to ensure it's achieving your recruitment goals.

Candidate Experience

A seamless ATS integration enhances the candidate experience by creating a cohesive recruitment journey. This section explains how to optimize the candidate experience when using PihuPulse with your ATS.

PihuPulse Candidate Experience Flow

PihuPulse Candidate Experience Flow

Unified Application Process

Create a seamless transition between your ATS application and PihuPulse screening:

Single Sign-On

Implement single sign-on (SSO) between your ATS and PihuPulse so candidates don't need to create multiple accounts or remember different credentials. This creates a smoother transition between systems.

Consistent Branding

Ensure your company branding is consistent across both your ATS career portal and PihuPulse screening interface. This includes logos, colors, fonts, and messaging to create a cohesive experience.

Pre-filled Information

Configure the integration to pre-fill candidate information from your ATS into PihuPulse, eliminating the need for candidates to enter the same information multiple times.

Communication Flow

Coordinate communications between your ATS and PihuPulse to provide clear guidance to candidates:

Email Templates

Create consistent email templates that clearly explain the screening process. Configure your ATS to automatically send screening invitations with clear instructions on how to access PihuPulse.

Status Updates

Ensure candidates receive appropriate status updates as they move through the screening process. Configure your ATS to send automated updates when screening is completed and results are reviewed.

Next Steps Guidance

Provide clear information about what happens after screening. Configure PihuPulse to display a customized message at the end of screening that explains the next steps in your recruitment process.

Feedback Loop

Implement a feedback mechanism to continuously improve the candidate experience:

Candidate Surveys

Configure your ATS to automatically send satisfaction surveys after candidates complete the PihuPulse screening. Use this feedback to identify pain points and improve the process.

Experience Metrics

Track key metrics like completion rates, time spent in screening, and dropout points to identify areas for improvement in your integrated recruitment process.

Candidate Experience Best Practice

Always test your integrated recruitment process from the candidate's perspective. Go through the entire journey from application to screening to identify any friction points or confusing transitions. This hands-on testing is invaluable for creating a truly seamless experience.

Troubleshooting

If you encounter issues with your ATS integration, use this troubleshooting guide to identify and resolve common problems.

Connection Issues

If PihuPulse cannot connect to your ATS:

  • Verify that your API credentials are correct and have not expired
  • Check that your ATS API is accessible and not experiencing downtime
  • Ensure that your firewall settings allow connections between PihuPulse and your ATS
  • Verify that the API permissions include all necessary scopes for the integration

Data Sync Issues

If data is not syncing correctly between systems:

  • Check your field mappings to ensure they are correctly configured
  • Verify that field types match between systems (e.g., text to text, number to number)
  • Check for any validation rules in your ATS that might be preventing data updates
  • Review the sync logs in PihuPulse for specific error messages

Workflow Automation Issues

If your automated workflows are not triggering as expected:

  • Verify that the automation is activated and not in draft or paused state
  • Check that the trigger conditions are being met exactly as configured
  • Ensure that the actions you're trying to automate are supported by your ATS's API
  • Review the automation logs to identify specific failure points

Performance Issues

If your integration is running slowly or causing performance problems:

  • Reduce the frequency of data syncs to minimize API calls
  • Limit the number of fields being synced to only those that are necessary
  • Check if your ATS has rate limits that you might be exceeding
  • Consider implementing incremental syncs instead of full data syncs

Integration Logs

PihuPulse maintains detailed logs of all integration activities, which can be invaluable for troubleshooting:

Accessing Integration Logs

To access integration logs:

  1. 1Navigate to Settings > Integrations > ATS Integration > Logs
  2. 2Use the filters to narrow down logs by date, event type, or status
  3. 3Click on any log entry to view detailed information, including request and response data
  4. 4Export logs for further analysis or to share with support

Need Additional Help?

If you're still experiencing issues with your ATS integration, please contact our support team at support@pihupulse.com or through the in-app chat support. Our integration specialists are available to help you resolve any issues and optimize your integration.

Was this article helpful?