> For the complete documentation index, see [llms.txt](https://atlas.anywhere.now/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atlas.anywhere.now/channels-integrations/cti-plugins/bullhorn.md).

# Embed WebAgent in Bullhorn

Configure the WebAgent CTI plugin for Bullhorn.

Configure the Bullhorn CTI plugin when WebAgent must be available inside Bullhorn.

## Prerequisites

For Dialogue Cloud Neo, you need a valid WebAgent license and either **PUL20, WebAgent add-on: CRM Embedded**, or **AW310 / AW310N, Salesforce and Bullhorn Premium Embedded Agent**. Your subscription may already include these licenses. Confirm them and plugin enablement with your AnywhereNow representative; see [shared CTI prerequisites](/channels-integrations/cti-plugins.md#licensing-prerequisites) for on-premises licensing guidance.

* Shared WebAgent sign-in is configured.
* Shared WebAgent service settings are configured.
* WebAgent and the Bullhorn CTI plugin are enabled for the environment.
* A Bullhorn administrator can configure the CRM integration settings.
* The WebAgent URL for the environment is available.

## Configure the Bullhorn integration

1. Confirm the Bullhorn environment where WebAgent must be available.
2. Sign in with a Bullhorn administrator account.
3. Confirm with the Bullhorn owner that at least one company record exists for validation.
4. In the current Bullhorn administration area, open the layout or action configuration for company records.
5. Create or update the custom action or menu entry that opens WebAgent.
6. Enter an action name that identifies WebAgent.
7. Enable the action for the intended company-record location.
8. Enter the WebAgent URL supplied for the environment.
9. Add only provider URL parameters that product, support, or the Bullhorn owner confirms are safe for the customer-facing WebAgent URL.
10. Assign the action to the Bullhorn user types that need embedded WebAgent access.
11. Save the action.
12. Confirm with the Bullhorn owner or Bullhorn support whether the WebAgent redirect URL must be registered or updated for the Bullhorn REST API integration.

{% hint style="warning" %}
Bullhorn administration labels can differ by environment. The Bullhorn owner may use labels such as company layout, custom menu actions, or add-new action, but use the labels that are current for the customer environment.
{% endhint %}

## Bullhorn configuration reference

Use Bullhorn-specific configuration only when the environment owner confirms that the setting is required.

| Configuration area        | Detail                                                                                                                                             | Use                                                                                    |
| ------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------- |
| Redirect URL registration | Bullhorn may need the WebAgent URL registered as a redirect URL for the Bullhorn REST API integration.                                             | Confirms that Bullhorn can redirect authentication back to WebAgent.                   |
| Provider URL parameters   | Bullhorn URL parameters can include non-secret provider values confirmed for the environment, such as the Bullhorn subdomain or client identifier. | Allows WebAgent to load the Bullhorn integration context for the environment.          |
| Secret handling           | Any Bullhorn secret or credential value must be handled through the approved configuration or support process for the environment.                 | Keeps secrets out of customer-facing URLs and page content.                            |
| `format-correlationid`    | Optional URL parameter. Append with `&` when another query parameter is already present.                                                           | Controls how correlation identifiers are written for Bullhorn activity context.        |
| `phoneformat`             | Optional URL parameter. Append with `&` when another query parameter is already present.                                                           | Controls how CRM phone-number links are formatted before WebAgent uses them.           |
| `disable-cti-settings`    | Optional URL parameter, usually set to `true` only for environments where Bullhorn CTI settings must not load.                                     | Disables Bullhorn CTI behavior without changing shared WebAgent sign-in configuration. |
| `enabled-entities`        | Optional URL parameter with a comma-separated entity list.                                                                                         | Limits the Bullhorn entity types available to the embedded integration.                |

## Configure URL parameters

1. Start with the WebAgent URL supplied for the environment.
2. Confirm each Bullhorn parameter with product, support, or the Bullhorn owner.
3. Add the first parameter with `?`.
4. Add each additional parameter with `&`.
5. Do not add secrets or credential values to the URL.
6. Save the updated URL in the Bullhorn integration configuration.

## Additional configuration

Keep CRM data lookup settings in [Bullhorn CRM Service](/channels-integrations/crm-service/bullhorn.md). Use this page only for the embedded WebAgent CTI plugin.

## Technical behavior reference

The Bullhorn CTI plugin implementation supports these record types:

| WebAgent record type | Bullhorn entity | Search fields                                               |
| -------------------- | --------------- | ----------------------------------------------------------- |
| Contact              | `ClientContact` | `phone`, `phone2`, `mobile`, `email`, `email2`              |
| Candidate            | `Candidate`     | `phone`, `phone2`, `mobile`, `workPhone`, `email`, `email2` |
| Lead                 | `Lead`          | `phone`, `email`                                            |

Activity behavior is note-based. For phone interactions, the plugin opens a Bullhorn Note with action **Inbound Call** or **Outbound Call**. For email interactions, it uses action **Email**. Other message-style interactions use **Left Message**. When a matched record is available, the note is linked to that record.

The plugin can also open a matched Bullhorn record, open the record's Notes view, and open a new Contact, Candidate, or Lead form with phone or email values prefilled.

## Validate the plugin

1. Sign in to Bullhorn as a test user with access to the integration.
2. Open the Bullhorn area where WebAgent should load.
3. Confirm that WebAgent opens and prompts for sign-in only when expected.
4. Place a test call or open a test interaction.
5. Confirm that configured URL parameters, correlation, and phone-number behavior match the intended Bullhorn workflow.

## Related topics

* [Configure WebAgent sign-in](/channels-integrations/webagent/configure-webagent-sign-in.md)
* [Configure WebAgent service settings](/channels-integrations/webagent/configure-webagent-service-settings.md)
* [Use WebAgent in a CRM system](/use/handle-conversations/webagent/use-webagent-in-crm.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://atlas.anywhere.now/channels-integrations/cti-plugins/bullhorn.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.