Configure Automated Enrichment Flow

Your org already has an Enrich with Amplify quick action on the Job record that uses AI to generate an external job posting (title, description, responsibilities, and education and experience requirements) from the job's existing details. The work happens in a headless subflow named Enrich Record (AFA), which has no screen and needs only the Job record ID as input.

Because the subflow is already built and packaged, Salesforce admins can automate enrichment by building record-triggered flow that calls the exisitng subflow. You don't rebuild any AI logic or create new fields.

Use this topic to automatically run Amplify Enrich on Job records in Salesforce, so qualifying jobs get an external job posting without anyone having to open the Jon and click Enrich with Amplify. It also covers how to run enrichment as a scheduled bulk process across many jobs at once, with tracking of which jobs succeeded and which failed.

Before You Begin

Confirm your org has the following:

• The BHRC Amplify Actions package, which provides the Enrich with Amplify quick action and its underlying flows.

• The BHRC Agentforce for Professionals package, which provides the AF4PR_Create_Job_Posting prompt template.

• A Salesforce Agentforce license.

• The AFA_Agentforce_Actions permission set (Models API access) and Read/Write access to the Job object (TR1__Job__c) for the users who own the jobs.

Automate Enrichment with a Record-Triggered Flow

Create the Flow

1. Navigate to Setup > Flows.

2. Click New Flow.

3. Select Record-Triggered Flow.

4. Configure the trigger:

   • Object: Job (TR1__Job__c)

   • Trigger the flow when: A record is created or updated

   • Trigger execution: At the start of the transaction

5. Click Done.

Add a Decision for Your Trigger Criteria

1. Click + New Element and select Decision.

2. Name the decision Should_Enrich_Job.

3. Add a rule with the following conditions, combined with AND:

   Condition Field operator Value Record Type Check

   $Record.RecordType.DeveloperName Equals Job

   $Record.TR1__Job_Status__c In Open,Draft,Pending

   $Record.On_Hold__c Equals false

4. Set Outcome Label to Proceed.

5. Click Done.

Adjust the criteria to fit your org. Common variations include:

• Multiple record type: Job, Permanent_Job, Contract_Job

• Different statuses:Open, Posted, In_Review.

• Other exclusions that use your org's own fields.

Call the Enrichment Subflow

1. On the Proceed path, click + New Element and select Subflow.

2. Select the flow named Enrich Record (AFA).

3. Set the input recordId to $Record.Id.

4. Click Done.

The subflow handles the prompt template, field mapping, and output parsing, exactly as it does when a user clicks Enrich with Amplify.

Handle Failures (Recommended)

The subflow returns isSuccess and errorMessage outputs.

1. Add a Decision after the subflow call that checks whether isSuccess equals false.

2. On the failure path, choose how to respond:

   • Log the failure to a tracking object. The Schedule Bulk Enrichment With Tracking process later in this topic describes one.

   • Send an email alert to an admin.

   • Leave the Job as is for manual retry.

Save and Activate the Flow

1. Click Save.

2. Enter a flow name, for example Auto Enrich Job.

3. Enter a description, for example "Automatically runs the existing Enrich with Amplify logic for jobs that match criteria."

4. Click Save, and then click Activate.

Test the Auto-Enrichment Flow

1. Create a test Job record:

   1. Open the Job object and click New.

   2. Enter enough detail for the AI to work with:

      • Job Title: "Senior Software Engineer"

      • Job Status: Open (must match your criteria)

      • Record Type: Job (must match your criteria)

      • On Hold: cleared (must match your exclusion criteria)

      • Client Job Description or Skills: a few sentences. The AI grounds the posting on these fields.

   3. Click Save.

2. Wait 5 to 10 seconds for the flow to run, and then refresh the Job record.

3. Confirm the flow populated these fields:

   • TR1__External_Job_Title__c

   • TR1__Client_Description__c

   • TR1__Responsibilities__c

   • TR1__Education_Requirements__c

   • TR1__Experience_Requirements__c

4. Test your exclusion logic. Create another Job with the status On Hold and confirm enrichment does not run.

Troubleshoot Enrichment That Doesn't Run

If enrichment doesn't happen, check the following:

1. Flow debug logs: Navigate to Setup > Flows, open your flow, and click Show Debug. Create a test Job and confirm the decision logic evaluated correctly and the subflow ran.

2. Manual button: Click Enrich with Amplify directly on a Job. If it fails too, the issue is with the underlying package or configuration, not your new flow.

3. Criteria: Verify the record type, status, and On Hold values on the test record match your decision criteria.

4. API limits: Navigate to Setup > System Overview and check API Usage to confirm you haven't hit prompt template rate limits.

Modify Your Trigger Criteria

To change which jobs qualify for auto-enrichment:

1. Navigate to Setup > Flows and open your flow.

2. Click Edit.

3. Click the Should_Enrich_Job decision and change the conditions.

4. Click Save.

Chain Enrichment into AI Screening (Optional)

After a job posting is enriched, you can hand the job to the existing screening questions pipeline. You don't build anything new to generate questions.

The pipeline works as follows:

• The AI Screening Status field (AFA_AI_Screening_Status__c) on the Job drives the process. Setting it to Questions Requested triggers the packaged automation (Flow:AF4PR_Generate_Screening_Agent_Questions_For_Job), which generates screening questions and creates the underlying Questionnaire__c and Single_Use_Question__c records.

• After questions generate, the status advances automatically. The questions appear in the existing Screening Questions screen flow.

• The Screening Agent Questions (JSON) field (AFA_Screening_Agent_Questions__c) is a machine-readable export that stays in sync automatically for the Bullhorn Automation integration. You don't populate or read it yourself.

To chain your enrichment flow into the pipeline:

1. In your enrichment flow, after the subflow call succeeds (isSuccess equals true), add an Update Records element on the same Job.

2. Set AI Screening Status (AFA_AI_Screening_Status__c) to Questions Requested.

3. Click Save and activate the flow.

This single field update is the entire integration point. The packaged screening automation uses the newly enriched job posting as context.

AFA_Auto_Enrich_Chaining_Flow

Schedule Bulk Enrichment with Tracking

To enrich many jobs at once, such as every open job that's missing a posting, build a scheduled process. The record-triggered flow handles jobs one at a time as they change, so a backlog needs a process that runs on a schedule, stays within per-transaction limits, and records which jobs succeeded or failed.

Build a Scheduled-Triggered Flow

1. Navigate to Setup > Flows and click New Flow.

2. Select Schedule-Triggered Flow.

3. Set your schedule (for example, daily at a low-traffic time).

4. Add a Get Records element that queries the jobs matching your bulk criteria. Use the same logic as your record-triggered decision, for example Status equals Open, posting fields blank, and On Hold equals false.

5. Add a Loop element over the retrieved jobs.

6. Inside the loop, call the Enrich Record (AFA) subflow and pass the current job's Id as recordId.

7. After each subflow call, create a Job Enrichment Log record that captures the isSuccess and errorMessage values.

8. Click Save and activate the flow.