Fountain ↔ Foley Integration (Foley Pre‑Hire Screening)

For: Admin users in Fountain · Estimated time: 15–20 minutes

Overview

The Foley integration lets your team initiate and track pre‑hire screenings (e.g., MVR, BGC, DOT) without leaving Fountain. Admins connect a Foley account once, then recruiters use a Foley stage in job workflows to kick off packages and review outcomes inside Fountain.

Good to know: Only one Foley integration can be configured per Fountain customer. Configure the integration using the highest‑level Foley account in your company hierarchy. Job requisitions may live in any child account underneath that top‑level account.

How the integration works

  1. Connect: A Fountain admin enters the Foley API Key and Account ID in Settings → Integrations → Screening.
  2. Trigger: When an applicant reaches a specific stage in Fountain, Fountain sends applicant details to Foley and can kick off a configured package of background screens.
  3. Update: Foley returns status updates (e.g., Data Collection, Complete Application, Approved), Rejected and errors/statuses for each configured stage in the candidate lifecycle.

Before you start

  • Ask your Foley representative for your API Key and Foley Account ID.
  • Confirm which screens and packages should be run for specific stages of the Candidate lifecycle (packages are configured in Foley and results surfaced to Fountain).
  • Make sure the job posting (requisition) already exists in Foley and that its Requisition ID matches what you’ll use in Fountain. Requisitions can live in any child account under your top‑level Foley account.
Environments: Use Sandbox for testing (api.sandbox.foley.io). Move to Production (api.foley.io) when ready.

Set up Foley in Fountain

  1. In Fountain, go to Settings → Integrations → Screening.
  2. Select Foley for the correct environment (Sandbox or Production).
  3. Enter your Foley API Key and Foley Account ID.
  4. Click Save Changes to connect. You should see confirmation that the integration is active.

Example (Sandbox):

Foley_Fountain_Integration_Settings.png
Important: Because only a single Foley integration is allowed per Fountain customer, configure it using the top‑level Foley account so that all child accounts’ requisitions can be used in workflows.

Add Foley to a job workflow

  1. Open the job in Fountain and edit its workflow.
  2. Add a new stage and choose the Foley Stage Type.
  3. Pick the desired screening package (e.g., BGC, MVR, etc) or action for that stage.
  4. Add a Rule for moving to a new Stage if a certain result is received.
  5. Ensure the Fountain job references the correct Requisition ID that already exists in Foley.
  6. Publish your changes and run a test applicant through the workflow in Sandbox.

Statuses & results in Fountain

  • pending_action: Waiting on candidate data/consents.
  • in_progress: Screening in progress.
  • completed: All screens complete. A Review Screens link may be shown.
  • incomplete or error: One or more screens cancelled/errored; details return via applicant details.

FAQ & tips

Can we connect multiple Foley accounts?
You connect once at the top‑level. Requisitions may exist in any child Foley account under that top‑level account.

Which screenings can be packaged?
Examples include BGC, MVR, DOT Drug/Alcohol, DOT Physical, DFW Drug/Alcohol, and Clearinghouse queries. Your Foley team will expose the right packages for your programs.

Do we need to create candidates in Foley first?
No—when an applicant hits the Foley stage, Fountain sends applicant data; Foley creates or maps the candidate automatically if the requisition exists and IDs match.

Troubleshooting

  • Invalid API key or account: Re‑check the API Key and Account ID you entered.
  • No packages visible in Fountain: Ask Foley to confirm packages are configured for your account and exposed to Fountain.
  • Statuses not updating: Verify you’re using the correct environment and that the job’s requisition exists in Foley with a matching ID.

Need help? Contact your Foley representative or Fountain Support.

Was this article helpful?
0 out of 0 found this helpful

Comments

0 comments

Article is closed for comments.