Actions87
- Appointment Actions
- Candidate Actions
- Company Actions
- Contact Actions
- File Actions
- Job Actions
- Job Submission Actions
- Lead Actions
- Note Actions
- Opportunity Actions
- Placement Actions
- Sendout Actions
- Task Actions
- Tearsheet Actions
Job → Get Many
AI-generatedSummary
Retrieve multiple Job records from Bullhorn using a JPQL WHERE clause with configurable field selection and paging options.
Inputs
- authentication (required) — Choose authentication method: User Credentials (Email & Password) or Enterprise Credentials (API Key).
- fields — Specify Bullhorn fields to return for each Job. You may rename output fields by setting an Output Name. Defaults to returning the 'id' field.
- limit — Maximum number of Job records to return. The value must be between 1 and 500, defaulting to 20.
- where (required) — JPQL WHERE clause to filter Jobs, e.g., "id > 0" or "status = 'Open'". All queries require this clause.
- hideDeleted — Optionally exclude deleted or archived Job records by automatically appending filters such as 'isDeleted=false'. Defaults to true.
- enableOperationsLog — Enables a second output with audit log entries for each write operation. This parameter is present but irrelevant for 'Get Many' as it is a read operation.
- outputFields — Additional fields to merge into every output item, allowing inclusion of fixed values or input expressions.
Output shape
a list of Job records conforming to the specified field mappings and query filters
The operation returns up to the specified 'limit' number of Job entities matching the 'where' clause. The 'hideDeleted' parameter automatically filters out deleted or archived records when applicable. Selected Bullhorn fields are returned with optional renames applied. The second output for operations log will not be emitted on this read operation.