Amplify Enriching FAQ

Got questions about Amplify Enriching? You're in the right place! This guide contains answers to common questions about Amplify Enriching.

See Amplify Enriching Troubleshooting for help solving common issues with the Enrich step.

How does Amplify Enriching work?

Here's the basic flow:

  1. Add the Enrich step to a candidate-, submission-, or job-based automation.

  2. Pick your prompt - choose from our default prompts or create your own custom ones

  3. Choose where to save the AI-generated content:

    • Directly to an ATS field, or

    • As a note on the candidate or job record.

Once a record passes through the Enrich step, your prompt runs automatically and the content gets saved exactly where you specified.

Which automations can I use the Enrich Step in?

You can use the Enrich step is Candidate and Job based automations, as well as submission-based automations with a Type of ‘Candidate’. The Enrich step is available for both standard and date-based automations.

How do I create my own prompts for the Enrich step?

Admins can use the Prompt Studio in Bullhorn ATS to build custom prompts. Once they’re created, they'll automatically show up as options in the Enrich step for the relevant entity.

How can I tell when a record has been enriched?

Just check the Activity Feed on the record in Automation! Here's what the statuses mean:

  • "Waiting": The record has been processed and is waiting for Amplify to complete the request.

  • "Completed": Amplify has finished and the content has been generated.

Why aren't all the default prompts in Bullhorn ATS available for use in Automation?

Bullhorn Automation currently supports prompts that are:

  • Entity-specific (designed for candidates, jobs, etc.)

  • Scalable across multiple records rather than tailored to individual records

This approach keeps your automated actions relevant, efficient, and effective at scale. Prompts that work best for one-off, individual record scenarios in the ATS aren't quite the right fit for Automation workflows.

What fields can the Enrich step write to?

You can choose any text field in the ATS. The AI-generated content comes back as a text string, so it needs to fit within the character limits and format requirements of your selected field.

 

  • Existing data will be overwritten - If your selected field already has content, the AI-generated text will replace it

  • Format matters - Content won't save if the field format is incompatible (for example, you can't save a job title to a date field)

Why can't the Enrich step write back a list of skills or categories to the standard ATS fields?

This comes down to how Bullhorn handles structured data. The standard skills and categories fields require each item to have a specific ID for validation—they're not simple text fields.

Right now, Automation delivers AI-generated content as plain text (like "JavaScript, Python, Project Management"), which doesn't match the structured format the ATS needs. We're working with plain text output, but those fields need specially formatted data with unique IDs.